Uninstall via msiexec

The good thing is, this one is really easily and deterministically to analyze: Either, the msi package is really not installed on the system or you're doing something wrong. Of course the correct call is:. Admin rights needed of course- With curly braces without any quotes here- quotes are only needed, if paths or values with blank are specified in the commandline. If the message is: "This action is only valid for products that are currently installed", then this is true.

Either the package with this ProductCode is not installed or there is a typo. First try to right click on the probably installed.

You will see besides "Install" and "Repair" an Uninstall entry. Click on that. Just google for them. Look there in the table with the name "Property" and search for the string "ProductCode" in the first column. In the second column there is the correct value. You are sure that the product is actually installed!

The original install is in fact visible in the current context. It looks as if it might have been a per-user install, and if you are logged in as somebody else now then it won't know about it - you'd need to log in under the same account as the original install.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How to uninstall with msiexec using product id guid without. Windows Installer 2. Patches applied using a version of Windows Installer that is earlier than Windows Installer 3.

When you invoke an uninstallation of a patch by any of the following methods, the installer attempts to remove the patch from the first product visible to the application or user requesting the uninstallation. The installer searches for patched products in the following order: per-user managed, per-user unmanaged, per-machine. You can uninstall patches from a command by using msiexec.

The following sample command line removes an uninstallable patch , example. Beginning with Windows Installer version 3. The patch can be referenced by the full path to the patch or by the patch code GUID.

To install a package named example. You can configure what a user sees during the installation process, based on your target environment. For example, if you're distributing a package to all clients for manual installation, there should be a full UI. However, if you're deploying a package using Group Policy, which requires no user interaction, there should be no UI involved. If your installation package overwrites files or attempts to change files that are in use, a reboot might be required before the installation completes.

If you need to debug your installation package, you can set the parameters to create a log file with specific information. You can set public properties through this command. The Overflow Blog. Podcast Making Agile work for data science.

Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions. Question feed. Super User works best with JavaScript enabled. Accept all cookies Customize settings.