Installshield Product Code |best| Jun 2026

In an automated build environment, use InstallShield's automation interface to generate a new Product Code and Package Code for every new major release.

The Product Code must adhere to the standard GUID format: a string of 32 hexadecimal digits, typically displayed in five groups separated by hyphens, and enclosed in curly braces. An example is 5D607F6A-AF48-4003-AFA8-69E019A4496F . All letters in the GUID must be uppercase. If you ever need to generate a GUID programmatically, for example, from a PowerShell script during a build process, you can use a command like (New-Guid).ToString("B").ToUpper() to ensure it is in the correct format.

Once a product has been shipped with a specific Product Code, that GUID is "burned" into the Windows Installer database on all your customers' machines for that version. If you were to release an update (marketing it as a minor patch) but change the Product Code, the installer would treat itself as a brand new product. The result would be a disastrous duplication where two products are installed side-by-side, both reporting themselves as the same software, while the original version remains present and un-updated on the system. installshield product code

Once a Product Code is used, it should never be reused for any other version or product. Recycling GUIDs can cause the Windows Installer to incorrectly cache or recognize packages, leading to unpredictable installation behavior. The entire point of a GUID is its uniqueness; if you need a new identifier, generate a new one.

: When releasing patches, ensuring the correct product code is targeted is crucial for successful patch application. All letters in the GUID must be uppercase

Which do you use? (MSBuild, Jenkins, Azure DevOps, etc.) Do your users require silent installations ?

: The product code ensures that each software product is uniquely identified, which is vital for managing multiple products or versions on the same system. If you were to release an update (marketing

Windows stores installation metadata within the system registry. You can browse to these keys to find your specific application details.

For minor changes where you want to patch or update an existing installation without a full reinstall, you typically keep the existing Product Code.