Understanding the InstallShield Product Code If you’ve ever managed a Windows deployment or wrestled with a tricky uninstallation, you’ve likely encountered the InstallShield Product Code. It is one of the most critical identifiers in the Windows Installer (MSI) framework, serving as the unique "fingerprint" for a specific release of your software.
Here is everything you need to know about what it is, why it matters, and how to manage it effectively. What is an InstallShield Product Code?
The ProductCode is a GUID (Globally Unique Identifier) used by the Windows Installer engine to identify a particular product or application version. While the human eye sees "MyApplication v1.0," the operating system sees 12345678-ABCD-1234-ABCD-1234567890AB.
In InstallShield, this code is set at the project level. It ensures that the system can distinguish your app from every other piece of software installed on the machine. Product Code vs. Upgrade Code
It is common to confuse these two, but they serve very different roles:
Product Code: Unique to a specific "edition" or version of the program.
Upgrade Code: Remains the same across all versions of a product. It acts as the "family name" that allows a new installer to find and replace an older version. Why the Product Code Matters 1. Handling Maintenance and Uninstalls
When you run a command like msiexec /x ProductCode, Windows looks up that specific GUID in its registry to find the cached .msi file and execute the removal. Without the correct code, you cannot programmatically uninstall or repair a specific build. 2. Preventing "Double Installations"
If you change the Product Code but keep the same installation path, Windows may treat the new version as a completely separate product. This results in two entries in "Add/Remove Programs," leading to file conflicts and registry bloat. 3. Patching and Updates
For "Small Updates" or "Minor Upgrades," the Product Code must remain the same. For a "Major Upgrade" (where the old version is completely uninstalled first), the Product Code must change. How to Find Your Product Code in InstallShield
If you are the developer or packaging engineer, you can find (or change) the code easily within the InstallShield interface: Open your InstallShield project (.ism file).
Navigate to the Installation Information section in the left-hand pane. Click on General Information.
Locate the Product Code property in the main window. It will be listed under the "Product Properties" group. How to Find the Product Code of an Installed App installshield product code
If you are a system administrator trying to automate a deployment, you can find the Product Code of an already installed app using PowerShell: powershell
get-wmiobject Win32_Product | Format-Table Name, IdentifyingNumber Use code with caution. The IdentifyingNumber column is your Product Code. Best Practices for Managing Product Codes
Automation is Key: In InstallShield, you can set the Product Code to * or use the "Generate New GUID" button. For Major Upgrades, always ensure a new GUID is generated.
Keep Records: Maintain a "Build Map" that logs which Product Code corresponds to which version number. This is invaluable for troubleshooting customer logs.
Consistency: Never change a Product Code mid-release. Once a version is "in the wild," that GUID is locked to that version forever.
The InstallShield Product Code is the backbone of your installer’s identity. By understanding when to keep it and when to change it, you ensure a seamless experience for your users—from the first click of "Install" to the final "Uninstall."
The InstallShield Product Code is a unique identifier, formatted as a GUID (Globally Unique Identifier), that acts as the primary "fingerprint" for a specific version of a software product on a Windows machine. Core Functionality
The Product Code is central to how Windows Installer (MSI) manages software. It allows the operating system to differentiate between various software packages, ensuring that updates, repairs, and uninstalls target the correct application.
Version Differentiation: If two versions of a product have the same Product Code, Windows treats them as the same entity. Changes to the Product Code are typically required for "Major Upgrades" to allow the installer to recognize the new version as a replacement for the old one.
Maintenance Operations: When you trigger an "Uninstall" or "Repair" from the Control Panel, Windows uses this code to locate the correct installation database. How to Find a Product Code
If you are an administrator or a user looking for the code of an already-installed program, you can find it through several methods:
Registry Editor: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Search the subkeys (which are themselves GUIDs) for the DisplayName of your software; the subkey name is often the Product Code. Blog Title: Demystifying the InstallShield Product Code: A
PowerShell: Run a command like Get-WmiObject -Class Win32_Product to list all installed MSI-based products and their identifying codes.
InstallShield Designer: Developers can find or generate this code in the General Information view of the InstallShield project. Key Identification Codes
It is often confused with the Upgrade Code, but they serve different purposes: Change Frequency Product Code Identifies a specific release of a product. Changes with every major version. Upgrade Code Identifies a family of products across all versions. Stays the same throughout the product's life. Package Code Identifies a specific MSI file. Changes every time the installer is built. Administrative Usage
For IT professionals, the Product Code is essential for "silent" or automated tasks. You can use it with the standard Windows Installer command-line tool, msiexec.exe, to manage software remotely without needing the original installer file: Uninstalling: msiexec /x YOUR-PRODUCT-CODE-HERE /qn. Repairing: msiexec /f YOUR-PRODUCT-CODE-HERE. Add a Custom Merge Module to an InstallShield Project
An InstallShield Product Code is a unique identifier (a GUID) used by the Windows Installer to distinguish a specific version of a software application. Key Characteristics
Unique Identity: Every version of your product should have its own unique Product Code. If you change the code, Windows Installer treats it as a completely different product.
Format: It is typically formatted as a Registry Summary Property, appearing as a string of hexadecimal characters inside curly braces (e.g., 12345678-1234-1234-1234-1234567890AB). Product vs. Upgrade Code: The Product Code changes with each version.
The Upgrade Code stays the same across all versions of the same software family, allowing newer versions to find and replace older ones. Where to Find or Set the Product Code
Installation Designer: In the InstallShield interface, go to the Installation Information section and select General Information.
Product Properties: You will see a "Product Code" field where you can manually enter a GUID or click the "Generate" button to create a new one.
Automation: If you are using an automated build process, you can use the InstallShield Automation Interface (COM) to set the ProductCode property via script. Why It Matters
Uninstallation: Windows uses this code to identify which application to remove when you trigger an uninstall from the Control Panel. If you’ve ever built an MSI using InstallShield,
Updates: When performing a "Major Upgrade," the installer uses the new Product Code to signal that it is a distinct, newer release that should replace the existing one.
Command Line: You can use the Product Code with msiexec.exe to perform silent uninstalls or repairs (e.g., msiexec /x YOUR-GUID-HERE). InstallShield Major Upgrade - SliQ Invoice Software
Blog Title: Demystifying the InstallShield Product Code: A Guide to Upgrades and Identification
Meta Description: Confused by the curly braces in your ISM file? Learn what the Product Code does, how it differs from the Upgrade Code, and the golden rule for major upgrades.
If you’ve ever built an MSI using InstallShield, you have definitely stared at those long strings of text wrapped in curly braces: A1B2C3D4-E5F6-....
Most developers ignore them—until something breaks. Why does Windows say the software is already installed? Why did your "upgrade" install a second copy instead of replacing the old one?
The answer almost always comes back to the Product Code.
Let’s cut through the confusion.
Definition: A minor update is a reinstall of the same product with some files changed, but the core identity remains the same.
When to do it:
How to implement: Keep the same Product Code. Increment the product version (e.g., 1.0.1 to 1.0.2). Use InstallShield's "Patch Design" view to create a .MSP file.
The Windows Installer engine uses the Product Code to determine whether a product is already installed on a computer.
.msi or setup.exe, the installer checks the registry to see if a product with that specific GUID exists.
A new Product Code means a new product identity. Windows Installer will treat it as a completely separate application.
If you want the new version to stand alongside the old version (side-by-side installation), you need a new Product Code AND a new Upgrade Code. If you want the new version to replace the old version, change the Product Code but keep the Upgrade Code identical.