Major upgrade does not cleanup Add/Remove entry

[usr9876]

With Installshield 2009 SP2, I created a setup with Project Assistant to install a single text file. I created a major upgrade item, taking care to bump the product code with another build. When I run the version 2.0 setup, it completes successfully, but there are now two entries in Add/Remove programs. The item for the previous version is broken. It seems like under the Uninstall registry key, there is an entry left:

InstallShield_{40CD94F8-5B90-4F5B-BADF-5112210B8806}

Normally, for each install, two entries would be created:
{40CD94F8-5B90-4F5B-BADF-5112210B8806}
InstallShield_{40CD94F8-5B90-4F5B-BADF-5112210B8806}

but the one with InstallShield_ prefix is not removed during the major upgrade - so now there are 3 entries - 2 new and 1 old. I confirmed in the msi log file that indeed the upgrade ran:

InstallShield 23:39:50: Begin SetAllUsers()
InstallShield 23:39:50: Getting records from Upgrade table
InstallShield 23:39:50: UpgradeCode: {3C40A277-30FB-468A-BAD7-0C6F80CC443C} MinVersion: 1.00.0000 MaxVersion: 99.00.0000 Language: Attributes: 769
InstallShield 23:39:50: Checking related product {A0003B85-9E69-4B69-95C1-021DD41B5894}
InstallShield 23:39:50: trial2 {A0003B85-9E69-4B69-95C1-021DD41B5894} 1033 1.00.0000 ***Related***
MSI (c) (E4!98) [23:39:50:703]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'.
InstallShield 23:39:50: ALLUSERS of related product {A0003B85-9E69-4B69-95C1-021DD41B5894} is = 1
MSI (c) (E4!98) [23:39:50:703]: PROPERTY CHANGE: Adding ALLUSERS property. Its value is '1'.
InstallShield 23:39:50: End SetAllUsers()
Action ended 23:39:50: ISSetAllUsers. Return value 1.

The windows installer cleanup tool does not see this item, so it seems like InstallShield doesn't cleanup.

Thanks for any insight.

[DLee65]

I could swear there were a couple of posts in here about this. ...

You may have to create a custom action to delete the key unfortunately. 😞

[tommex]

DLee65 wrote:
I could swear there were a couple of posts in here about this. ...

You may have to create a custom action to delete the key unfortunately. 😞

exactly...but if you have a different solution, just let us know;)

the link to the other thread:
http://community.installshield.com/showthread.php?t=183491

[usr9876]

This is a toy/test installation, Installscript MSI. I'm trying to do the minimum number of steps to get a fully functional major upgrade.

I ran the setup on windows XP on my home PC XP SP3 and inside of a VM, XP SP 2. What causes the problem? Is it: misconfiguration of setup, target machine OS, windows installer or Installshield? Is there a sample (bare bones) ISM project file that works everywhere?

[DLee65]

I can only speculate that the registry entry InstallShield_{MY-VERY-GREAT-GUID} is not added to the MSI tables that Setup.exe is writing the registry entry, or something like that.

I am fairly certain that this is an InstallShield problem, although perhaps some of the forum monitors can chime in on this issue.