What are WMIC uninstall commands and syntax to be used for products for which "product get name" returns names with extended characters or already including parentheses?

[TransgressorOfTheUnspeakableWord]

...or, should I use a more comprehensive/different call in place of the basic

product get name

?

Upon briefly attempting to look up answers to this, I've seen people specify actual program paths and use all manner of different ways (like probing registry entries themselves) in order to poll and specify the correct parameters for applications they wish to deal with using WMIC.

Whereas, I've simply been trying to uninstall leftovers/undesirables using

product where (name="INSERT RETURNED NAME HERE") call uninstall

after highlighting and c&p'ing the full title returned by the simple manner already stated, while being careful not to include addtional spaces at the end when initially copying.

BE AWARE!
I know nothing of SQL - or any other modern scripting/language, for that matter.
However, I am very logical and hopefully shouldn't need 100% "hand-holding".

TIA for any help.

[TransgressorOfTheUnspeakableWord]

Well, I've got somewhere with it.

Here's one example:-
The prompt remains after one has called WMIC from a (root drive) C:\ prompt, so need not be entered again.

wmic:root\cli>product where (name like"Far Cry%") call uninstall

This entry found two instances of installed "Far Cry___" components, asking me to interactively confirm each uninstall.
I don't think it'd be wise to disable interactive mode while using wildcards to discover titles.

Now I'm off to to try it out on more amiguous/awkwardly titled entries.

[TransgressorOfTheUnspeakableWord]

Why has this been moved to "Off Topic", when it's related to an important - seemingly essential - tool with regards troubleshooting self-destructive MS Windows OSes? and was, thusly, posted in the named "Hardware and OS" thread.
Considering unseen fragments of troublesome driver software that can be, and have been, removed using this method, even "hardware" is applicable, considering drivers are the required OS environment code interface.

Explanation required.
NOW.

Or was it simply moved by a migrated "console kiddie", who has somehow sucked their way up to moderator status without so much of a clue?

[HellHoundWarrior]

umm...what?
EDIT:steam thinks its a link -_-

[TransgressorOfTheUnspeakableWord]

Steam thinks what is a link? Your "umm...what?"?
If you truly mean "umm...what?" I cannot see how you don't comprehend how my post is related to both "OS" and "hardware". Though the latter, only through driver package detritous.
I've been using this a lot today and a lot of issues with Win10 are disappearing.
It seems this is good for clearing up leftovers during an upgrade; the sort of stuff that causes issues that "Bad Motha" always claims can only be resolved via a "clean install".

edit: Yeah, mine did it too. So, I guess you meant it. Why can you not figure what I'm saying here? I made it pretty clear.

[HellHoundWarrior]

When I said "umm...what?" I was trying to point out that I didn't understand what this post's intentions were, but now that I think about it I probably shouldn't have posted. I apologize for taking your time.

[TransgressorOfTheUnspeakableWord]

Originally posted by DGCAST HellHoundWarrior:

When I said "umm...what?" I was trying to point out that I didn't understand what this post's intentions were, but now that I think about it I probably shouldn't have posted. I apologize for taking your time.

No problem.
It's fine you posted.
Though, you probably shouldn't have posted so "previous" when faced with an angry man after Steam's blood.
But then, you don't know my staunch "Aries" character, so it's forgiven.
My Win feature highlight could have been helpful to others, even though I was asking for correct syntax to use it.
No hard feelings.
Censorship, as a mere bullying attempt, seems to be getting out of hand in here.