installing 32-bit MSI over mixed 32/64-bit EXE

[trashy]

To date, we have supplied our app via two installers; a mixed 32/64-bit EXE and a 32-bit MSI.

To simplify things we will supply our new app via just a 32-bit MSI.

The only problem scenario found so far seems to be as follows:

• Installing on Windows 7 SP1 64-bit (Windows 8.1 64-bit is ok, all 32-bit OS ok)
• App originally installed using old mixed 32/64-bit EXE (old 32-bit MSI ok)
• App upgraded using either new 32-bit MSI
• C:\Program Files\<app> untouched (although add/remove programs entry and start menu entry have both correctly gone for old app)

Questions:

1) Any idea why the C:\Program Files\<app> remains (even after a reboot)?
2) Why we get different behaviour on Windows 7 compared with Windows 8?

Any help appreciated!

Advanced Installer 11.7.1
Install files built on Windows 8.1 64-bit OS

[Eusebiu]

Hi,

Looking over your log file, I found the following line: Skipping RemoveExistingProducts action: current configuration is maintenance mode or an uninstall. This may appear if the version of your old and new packages are the same. Did you increase the version of your new package when you created it?

The problem may also appear because of multiple tests of the package on the same machine. Can you reproduce the problem on multiple "Windows 7 64-bit" machines?

Best regards,
Eusebiu

[trashy]

Thanks for taking a look.

In answer to your questions regarding the new installation MSI:

* Updated Product Version from 3.9.4.0 to 4.2.2.0
* Generated new Product Code
* Kept Upgrade Code same

Just tried on another Windows 7 64-bit PC - same result - C:\Program Files\<app> untouched

[Eusebiu]

Hi,

Can you please send us your AIP file and a link to download your packages to support at advancedinstaller dot com, so we can investigate them and try to find the problem?

Best regards,
Eusebiu

[trashy]

Thanks Eusebiu - emails sent.

[Eusebiu]

You're welcome.

Please give us some time to investigate this and we'll get back to you as soon as we have a conclusive answer.

Best regards,
Eusebiu

[trashy]

Thanks Eusebiu - this is the last issue we need to resolve before we can roll out our new application

[Eusebiu]

Hi,

We investigated the problem and it seem to be a Windows Installer limitation. Upgrading a 64-bit package to a 32-bit one does not remove the files of the old version if they were installed in a 64-bit location (i.e. Program Files), because the 32-bit package cannot access the 64-bit location.

Indeed, this behavior is present only on Operating Systems older that Windows 8. The Windows Installer version installed on Windows 8 and above, is newer and it seems that it includes an improvement for this.

As a workaround, you can add the "Uninstall previous versions" predefined custom action in the 32-bit package, which will completely remove the 64-bit package and its files, however this custom action cannot be executed on the "Install Execution Stage" section.

Best regards,
Eusebiu

[trashy]

Thanks Eusebiu.

Just a couple of quick questions:

1) Why can't it go in the "Install Execution Stage"?
2) Can it go in the "Finish Dialogs Stage"?

I don't really want to put it in the "Wizard Dialogs Stage" as this before our "DetectProcess" and "StopProcess" actions in the "Install Execution Stage". I need these actions as the app is a sys tray that doesn't respond to WM_CLOSE messages when the main window isn't open.

[Eusebiu]

Hi,

1) Why can't it go in the "Install Execution Stage"?

The uninstall custom action cannot be placed on the "Install Execution Stage" because two MSI packages cannot run at the same time (in this case the new version that is installed and the old one that is uninstalled). This is the Windows Installer normal behavior.

It works on the "Install Execution Stage" section, only if you place it the last in sequence (after the "Finish Execution" action group) and uncheck the "Wait for custom action to finish before proceeding" and "Wait for return code at the end of the sequence" options for it.

2) Can it go in the "Finish Dialogs Stage"?

Yes, it works on that stage.

Best regards,
Eusebiu