cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jasonaunrein
Level 2

InstallShield extracted MSI is left behind in c:\programdata

We're having InstallShield create a standard setup.exe and upgrade.exe that extracts the msi into c:\programdata. This is then used like normal for any uninstall/repairs. The problem is that during our testing, we might have a 100+ upgrades that get installed on test machines. Each upgrade msi is stored in c:\programdata\\ and never gets removed unless done manually.

Is anyone aware of a setting that prevents the old upgrade installers from being removed or a way to remove them other than a custom action to remove everything except N-1.

I'm assuming since these are upgrades, the old versions are so you can revert back to previous versions (Ie uninstall N, then N-1, then N-2...). If that isn't the case, I don't see why these versions stick around. Either way, I haven't had any luck finding information about this problem.

Any thoughts. Let me know if there is any specific info you need.
Labels (1)
0 Kudos
2 Replies
PlinyElder
Level 7

Is this in an Advanced UI/Suite Project?

If so you can set the release Setup.exe to NOT cache packages locally
0 Kudos
jasonaunrein
Level 2

Nope, this is a basic msi project in IS Pro 2014.
0 Kudos