WIX (remove all previous versions)

by

Ignoring Digits: Extract from the MSI SDK documentation for the ProductVersion property:

“Note that Windows Installer uses only the first three fields of the product version. If you include a fourth field in your product version, the installer ignores the fourth field...At least one of the three fields of ProductVersion must change for an upgrade using the Upgrade table.“

In order to get rid of installations in the wild, there are a few approaches.

Uninstall By Product Code: I would just get a list of product codes and uninstall corporate-wide if you are delivering an in-house application: How can I find the product GUID of an installed MSI setup? The list of product codes you assemble can then be passed to msiexec.exe /x {productcode} as explained in section 3 here. Just a simple batch file. Or you can try WMI, or one of the other approaches.

Uninstall By Upgrade Code: You can check if all your setup versions share the same upgrade code by using the code from here: How can I find the Upgrade Code for an installed MSI file? (they probably do). There is even a VBScript version here. Throwing in a link to an answer where I link to several other ways to uninstall, such as by uninstalling all setups that share the same upgrade code. And a direct link to actual code to do so (uninstall by upgrade code).

Uninstall By Product Name: You can uninstall by product name matching as well. Some samples here (VBScript): Is there an alternative to GUID when using msiexec to uninstall an application?. And here is a .NET DTF uninstall function: Uninstalling program (distinctively simplistic, needs tweaking for real-world use).

Some Links:

More Related Contents:

  1. Adding entries to MSI UpgradeTable to remove related products
  2. Reboot on install, Don’t reboot on uninstall
  3. Run Wix Custom action only during uninstall and not during Major upgrade
  4. Doing Major Upgrade in Wix creates 2 entries in Add/Remove Programs
  5. How do I avoid common design flaws in my WiX / MSI deployment solution?
  6. Windows Installer and the creation of WiX
  7. Wix to Install multiple Applications
  8. What do I do when launching an application triggers repeating, endless Windows Installer self-repair?
  9. Is there any possible way to perform upgrade when Product codes for old and new versions are same?
  10. How do I avoid triggering MSI self-repair with my WiX / MSI package?
  11. Uninstall from Control Panel is different from Remove from .msi
  12. Microsoft Installer command line string parameter not working?
  13. How to execute conditional custom action on install and modify only?
  14. How can I programmatically read the properties inside an MSI file?
  15. How to Explicitly Remove dll During Majorupgrade Using Wix Toolset
  16. File of a new component isn’t installed because there was an old component with the same file
  17. Windows installer deletes versioned file during product upgrade, instead of downgrading it
  18. I screwed up, how can I uninstall my program?
  19. WIX merge c++ runtime
  20. In WiX files, what does Name=”SourceDir” refer to?
  21. Wix Custom Action – session empty and error on deferred action
  22. One file per component or several files per component?
  23. Unselected Feature Being Installed
  24. Wix burn doesn’t allow to remove file
  25. Adventures in Installing a C#/WPF Application (WiX)
  26. Create a .config folder in the user folder
  27. Passing command line args to MSI from WiX bundle
  28. VersionNT MSI property on Windows 10
  29. How to assign path value to Directory in WIX?
  30. Wix per user installer to detect the Visual C++ 2015 Redistributable

Leave a Comment