You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.
I wrote a set of tools, RemoveByName and RemoveByGUID that lets you specify a list of applications to remove, and it will remove them for you. It uses WMI, but it does it intelligently - only running the commands it needs to - So your not running removals on software that isn't installed. You interested?
The text was updated successfully, but these errors were encountered:
Definitely. I want to use WMI as much as possible. It's insanely useful. Someone mentioned that if WMI is broken it would stop the script from running, but if that's the case, there's more of a reason to start over with a new install of Windows.
So in the interest of not being too long winded, please feel free to rewrite Stage 2. Thank you.
If WMI is broken, that actually indicates an issue with the PATH variable. In any case, I am not sure if my application be affected, because I am using direct calls to the system to do the work, not the WMI binary.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I wrote a set of tools, RemoveByName and RemoveByGUID that lets you specify a list of applications to remove, and it will remove them for you. It uses WMI, but it does it intelligently - only running the commands it needs to - So your not running removals on software that isn't installed. You interested?
The text was updated successfully, but these errors were encountered: