Is there an alternative to GUID when using msiexec to uninstall an application?

by

First of all: it is normal that the product GUID changes for new versions of the application, though it is also possible to upgrade some applications without changing the product GUID (referred to as minor upgrades – as opposed to major upgrades that change the product GUID). What tends to remain stable between different releases of the same product is the UpgradeCode (it defines a family of related products). ProductCode uniquely identifies a product (in a specific version).

There are some options for uninstall listed here: Uninstalling an MSI file from the command line without using msiexec.

I suppose you could use the MSI file name as illustrated in section 3, or if the product name remains stable you could use it along with automation to look up the correct product GUID to uninstall the product in question. I will test this in a moment and update the answer.

UPDATE: A sample VBScript to uninstall product by “product name” (assuming it remains constant across releases, which it normally does, but there is no guarantee – it depends on the product).

Find the product name in Add/Remove Programs – or use the tiny VBScript linked to at the bottom of this answer to export a little text file with info for all installed packages.

' On Error Resume Next ' Used to suppress errors

Const msiUILevelNone = 2
Const msiUILevelFull = 5
Const msiInstallStateAbsent = 2

Set installer = CreateObject("WindowsInstaller.Installer")
Set products = installer.ProductsEx("", "", 7)
installer.UILevel = msiUILevelFull  ' Running with full GUI (if available in MSI)
' installer.UILevel = msiUILevelNone ' Will run uninstall silently, run script with admin rights

' Get the product name from the user
productname = InputBox("Please enter the product name for the MSI package you wish to uninstall:")
If productname = vbCancel Or Trim(productname) = "" Then
   WScript.Quit(0)
End If    

' Iterate over all MSI packages on the box
For Each product In products

   currentproduct = product.InstallProperty("ProductName")

   If LCase(currentproduct) = LCase(productname) Then

      installer.ConfigureProduct product.productcode, 0, 2 ' msiInstallStateAbsent
      MsgBox "Ran uninstall for: " & currentproduct
      Exit For ' End product iteration, assuming only one product needed uninstall

   End If 

Next

Set installer = Nothing

MsgBox "Finished."

UPDATE: You can create yourself a quick list of product codes and product names using VBScript as described towards the bottom of this answer: How can I find the product GUID of an installed MSI setup? . This particular VBScript is as simple as it can possibly get I think.

More Related Contents:

  1. How can I find the product GUID of an installed MSI setup?
  2. Powershell: Uninstall application by UpgradeCode
  3. How can I find the Upgrade Code for an installed MSI file?
  4. How can I use powershell to run through an installer?
  5. How to create windows installer [closed]
  6. How can I uninstall an application using PowerShell?
  7. Why does MSI require the original .msi file to proceed with an uninstall?
  8. Silent run installer (.exe) with parameters on Windows
  9. How to run an installation in /silent mode with adjusted settings
  10. Uninstall and Install App on my Computer silently
  11. How do I pass a local variable to a remote `Invoke-Command`? [duplicate]
  12. The ‘
  13. Watch file for changes and run command with powershell
  14. What is the wix ‘KeyPath’ attribute?
  15. PowerShell – Decode System.Security.SecureString to readable password
  16. Convert a string to datetime in PowerShell
  17. How to quickly change shell folder to match the currently open file
  18. What does $_ mean in PowerShell?
  19. How to get Powershell Invoke-Restmethod to return body of http 500 code response
  20. How to normalize a path in PowerShell?
  21. How to create a shortcut using PowerShell
  22. How to Reinstall Broken npm
  23. Get target of shortcut (.lnk) file with powershell
  24. How can I create an MSI setup?
  25. Can’t install nuget package because of “Failed to initialize the PowerShell host”
  26. What security setting is preventing Remote PowerShell 2.0 from accessing UNC paths
  27. start remote process within the context
  28. How can I elevate Powershell while keeping the current working directory AND maintain all parameters passed to the script?
  29. Are you able to use PtrToStringAuto to decrypt a secure string in Powershell 7 on macOS?
  30. Prevent trailing newline in PowerShell Out-File command

Leave a Comment