

Result: The second install will fail with a message that the product is already installed, or it will trigger a self-repair. Fix: If you need multiple builds (e.g., Developer vs. Production), you must either use different Product Codes or use instance transforms (MSI).
When a user runs the new MSI, Windows Installer sees: "Upgrade Code matches an existing product, but Product Code is different." It then uninstalls the old product (using its old Product Code) and installs the new product. installshield product code
At its core, the InstallShield Product Code is a GUID (e.g., AC76BA86-7AD7-1033-7B44-A94000000001) that uniquely identifies an application suite or product. Result: The second install will fail with a
However, there is a critical nuance that causes endless confusion: InstallShield supports two major project types—InstallScript and MSI (Windows Installer). At its core, the InstallShield Product Code is a GUID (e
InstallShield provides several methods to manage this GUID.
| Your change | Change Product Code? | Upgrade type | |------------|---------------------|---------------| | New major version (v2.0) | ✅ Yes | Major upgrade | | New minor version (v1.1) | ❌ No | Minor upgrade / patch | | Hotfix (same version) | ❌ No | Patch (.msp) | | Product rename | ✅ Yes | Major upgrade | | Add/remove features | ❌ No (reinstall) | Not an upgrade | | Different edition (Pro vs Enterprise) | ✅ Yes | Side-by-side possible |