Message about failed x86-prerequisite on x64 OS after upgrade from AI 13.0 to 13.7

[othulke]

Hi everyone,

we just upgraded our build environment from AI 13.0 to 13.7 and everything worked smoothly until we tried the first installation.
The setup (EXE bootstrapped with both x86 and x64 MSIs) executes flawlessly until prerequisite installation (MSVC 2010 SP1 runtimes for x86 and x64).

On a x64 test system (Windows 7 SP1 x64) the setup installs both x64 and x86 versions of the runtime DLLs (they show up in "Programs and Features") and then complains about the x86 runtime installation having failed:
"Visual C++ 2010 SP1 Redistributable x86 mandatory prerequisite was not correctly installed."
This even happens when the x86 runtimes are already present on the system!

On a x86 test system (Windows Server 2008 SP2 x86) the setup attempts installation of both x86 and x64 versions of the runtime DLLs and complains about the x64 runtime installation having failed:
"Visual C++ 2010 SP1 Redistributable x64 mandatory prerequisite was not correctly installed."

Previous setups (all created with AI 13.0 or before) have never attempted to install the x86 runtimes on x64 OSes or vice versa.

The prerequisite configuration has not been changed during upgrade:
The x86 runtimes are enabled for "32-bit Windows Versions" only ("Install Conditions->Supported Windows Versions").
The x64 runtimes are enabled for "64-bit" OSes only.

Has there been a change in the underlying installer engine regarding handling of x86/x64 prerequisites that we are unaware of or is this a bug in AI 13.7?

Any help would be greatly appreciated!

[Eusebiu]

Hi,

I tested the scenarios you described in the same environments as your and everything worked as expected for me. The problems that you described may appear if the install conditions of the prerequisites are not correct. Can you send me your AIP file to support at advancedinstaller dot com, so I can investigate it?

Best regards,
Eusebiu

[othulke]

Hi Eusebiu,

I just sent you the AIP file we're using with AI13.0. Maybe it's just a misconfiguration on our side that doesn't have any effect up to AI13.0?
Hope to hear from you soon.

Best regards,
Oliver

[Eusebiu]

Hi Oliver,

Indeed, this seems to be an Advanced Installer issue. The problem is that the "Disabled if" conditions are removed during the build of the package. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention.

Unfortunately, we do not have any workaround for this. The only solution is to continue using the 13.0 version of Advanced Installer that works. Sorry for the inconvenience.

Best regards,
Eusebiu

[othulke]

Hi Eusebiu,

thanks for the quick answer. We've downgraded to AI13.0 again.
I would like to point out that other projects using the same "Disabled if" settings on features (NOT used for prerequisite installation) continue to work as expected after upgrading to AI13.7.
Maybe this helps in tracking down the bug.

Can you share any information regarding the time frame for a bugfix?

Best regards,
Oliver

[Eusebiu]

Hi Oliver,

Indeed, I forgot to mention that the problem appears only for the features related to the prerequisites. The latest version of Advanced Installer has just been released, so unfortunately I cannot give you an ETA for now. We will try to add a fix for this problem in the next version which may be available on the next month.

Another thing that I should have mentioned is that, since you have selected the appropriate Windows Versions in the "Install Conditions" tab of your prerequisites, you do not need to set the "VersionNT64" condition for their related features in the "Organization" page. The conditions from the "Install Conditions" tab should be enough in this case.

Best regards,
Eusebiu

[othulke]

Hi Eusebiu,

I can confirm, that just deleting the "Disabled if" entries of the mentioned features fixes the problem.
It appears we're ready to give AI13.8 a try now.

Thanks for your help.

Best regards,
Oliver

[Eusebiu]

You're welcome Oliver. I'm glad it worked.

Just let me know anytime you need help.

Best regards,
Eusebiu

[Dan]

Hello,

This was fixed in version 14.0 of Advanced Installer released on May 7th, 2017.

Best regards,
Dan

[othulke]

Hi Dan,
thanks for the update!

Best regards,
Oliver