how to find out which products are installed – newer product are already installed MSI windows

by

ProductCode identifies a particular product. It changes every time you ship a new replacement product.
UpgradeCode defines a series of products by using the same UpgradeCode in a updated products whose versions are expected to continually increase. By default, new product versions replace older product versions with a major upgrade. Because upgradecode defines a product series, Windows will look for products with the same UpgradeCode because identical UpgradeCodes means mutually exclusiv products, using them to replace an older product with a new one. In WiX, major upgrade is done with the majorupgrade element which it appears you may be using because you get that “a newer version is installed” message. There is an AllowDowngrade option there if you want to “upgrade” to a lower version.

Product versions (like file versions) are not just useful information – they are used by the system with the understanding that new replaces old and generally it is a bad thing to go back to lower versions, that’s why the default behavior disallows downgrades.

This script might help. It uses the Windows Installer scripting API to enumerate all the installed products, showing version, user sid, ProductCode etc:

Option Explicit
Public installer, fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache, pvers

Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("prodex.txt", True)

' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on error resume next
For Each prod In installer.ProductsEx("", "", 7)
   pid = prod.ProductCode
   contxt = prod.Context
   sid=prod.usersid
   pname = prod.InstallProperty("ProductName")
   psorce = prod.InstallProperty("InstallSource")
   ploc =prod.InstallProperty("InstallLocation")  
   pcache = prod.InstallProperty("LocalPackage") 
   pvers=prod.InstallProperty("VersionString")
   a.writeline (pid & " " & pname & " " & pvers & " installed at <" & ploc & "> from " & psorce & " Context " & contxt & " Local " & pcache)
Next

More Related Contents:

  1. How can I compare the content of two (or more) MSI files?
  2. Change my component GUID in wix?
  3. How to make better use of MSI files
  4. What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc [closed]
  5. Why is it a good idea to limit the use of custom actions in my WiX / MSI setups?
  6. Changing text color to Wix dialogs
  7. WIX does not uninstall older version
  8. Adding entries to MSI UpgradeTable to remove related products
  9. Removing files when uninstalling WiX
  10. How to pass CustomActionData to a CustomAction using WiX?
  11. How to add a WiX custom action that happens only on uninstall (via MSI)?
  12. Wix Installer : Setting component condition property when doing a MSIEXEC admin install at command line
  13. What do I do when launching an application triggers repeating, endless Windows Installer self-repair?
  14. Silent installation of a MSI package
  15. Uninstall from Control Panel is different from Remove from .msi
  16. wix – custom action dialogbox on silent uninstall of application
  17. Interrupt installation when custom action returns error
  18. How to Explicitly Remove dll During Majorupgrade Using Wix Toolset
  19. I screwed up, how can I uninstall my program?
  20. WIX merge c++ runtime
  21. Failing condition wix
  22. In WiX files, what does Name=”SourceDir” refer to?
  23. Why is it a good idea to limit deployment of files to the user-profile or HKCU when using MSI?
  24. Unselected Feature Being Installed
  25. How do I avoid distributing sensitive information in my MSI by accident?
  26. VersionNT MSI property on Windows 10
  27. WIX Installer: Prevent installation on Windows Server 2012 R2
  28. Failed to get MSI property in UPGRADINGPRODUCTCODE, WIX_UPGRADE_DETECTED
  29. How to display a non-blocking warning for the operating system in Wix?
  30. WiX – Doing a major upgrade on a multi instance install

Leave a Comment