![msi product lookup by serial number msi product lookup by serial number](https://landing.coolermaster.com/faq/files/others/kA090000000MSdy_2.jpg)
You can find the Product Code in the Property table of any MSI file (and any other property as well). HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall The following registry keys are the common locations in which search and find the GUIDs of MSI packages: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall If it's a 32-bit installer on a 64-bit machine, it might be under the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall.
![msi product lookup by serial number msi product lookup by serial number](https://drivesolutions.com/media/wysiwyg/pages/acer_aspire_v5-571_combined.jpg)
Press F3 key and search for your product name. You can also find the product code by perusing the registry from this base key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Output.writeline (productcode & ", " & name & ", " & version) Version=product.InstallProperty("VersionString") Name = product.InstallProperty("ProductName") On Error Resume Next ' we ignore all errorsįor Each product In installer.ProductsEx("", "", 7) Set installer = CreateObject("WindowsInstaller.Installer") Set output = fso.CreateTextFile("msiinfo.csv", True, True) Set fso = CreateObject("Scripting.FileSystemObject") '# Retrieve all ProductCodes (with ProductName and ProductVersion)
#Msi product lookup by serial number windows
You can try a VBScript to access information via the MSI automation interface (core feature of Windows - it is unrelated to WMI). However, it is more involved than the Powershell option (several lines of code). In essence it is (much) faster and not capable of triggering MSI self-repair since it does not go through WMI (it accesses the MSI COM API directly - at blistering speed). This option may be safer than Powershell for reasons explained in detail below. Quick start of Powershell: hold Windows key, tap R, type in " powershell" and press Enter. get-wmiobject Win32_Product | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize Take not that IdentifyingNumber is the ProductCode (WMI peculiarity). The package integrity checks triggered does add some event log "noise" though. The following four approaches can give us several methods to find and retrieve (also remotely) the GUID of installed MSI packages: Use the Powershell "one-liner"Īny self-repair triggered by this option should generally be possible to cancel. For example, installer API " MsiQueryFeatureStateEx()" and " MsiQueryProductState()", etc. The product code is the unique GUID of identifying an application or product release In other words, different versions and languages of Product must have different product codes.Īlso, ProductCode can be used to query feature state, and product state.