Prerequisite condition for VC++ x86 runtime
I added VC++ 64 bit runtime prerequisite to my InstallShild project. File is downloaded from Microsoft page: https://aka.ms/vs/17/release/vc_redist.x64.exe and has the following description: Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.34.31931.
When this file is executed, it creates/updates the following Registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\vc\Servicing\14.0\RuntimeMinimum, Version, 14.34.31931. Accordingly, I added the following Prerequisite Condition to InstallShield:
Everything is OK for x64. Now I want to add VC++ x86 runtime to the same project. File https://aka.ms/vs/17/release/vc_redist.x86.exe, description: Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.34.31931.
When this file is executed, it creates/updates the following Registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\DevDiv\vc\Servicing\14.0\RuntimeMinimum, Version, 14.34.31931. I would like to make Prerequisite Condition by the same way, as for x64. But this doesn't work, because x64 installer actually creates two registry entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\vc\Servicing\14.0\RuntimeMinimum and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\DevDiv\vc\Servicing\14.0\RuntimeMinimum, filling them by the same way. So, if x64 VC++ Runtime is already installed, x86 WOW6432Node condition doesn't work.
How can I solve this problem? The project has InstallScript type, so I can override installation events, if necessary. InstallShield version is 2018.
Try with the following registry keys:
For 64-bit setup,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\X64
Value: Version
For 32-bit setup,
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86
Value: Version
Condition type should be:
- InstallShield 2023 Basic MSI: How to change the value of INSTALLDIR at runtime?
- MS Access DB Engine (32-bit) with Office 64-bit
- InstallShield InstallScript-MSI vs. InstallScript-non-MSI
- Installshield major upgrade doesn't uninstall old version
- Accessing command line arguments Installshield Installation Designer UI
- Updating InstallShield .ism (MSI) file with beatifulsoup and maintaining its formatting
- Copyright details doesn't show Organization name
- Managed Code custom action in .Net Core 6 or later
- How to set Required Execution Level to Administrator for Basic MSI project type with MSI file
- WIX Toolset - Custom Action command doesn't correctly detect Windows 10 version
- Using Inno Setup to patch an Install Shield Application
- Signing in Inno Setup fails with "Sign Tool failed with exit code 0x1"
- Is there a good alternative to Install Shield?
- The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception
- How to create a custom installshield dialog skin?
- How to pre-set MSI SecureCustomProperties that are not defined in Properties to allow silent installation?
- How to prevent restart dialog caused by MSI 1610 error
- How do I avoid triggering MSI self-repair with my WiX / MSI package?
- Windows Installer can't find registry entry
- How to add a prerequisite check for .NET framework 4.5.2 in InstallShield Basic MSI project
- Prerequisite condition for VC++ x86 runtime
- Exact setup behavior description, when prerequisite needs a reboot
- Environment variables and other features are missing in InstallShield project
- Installshield Silent Uninstall not working at Command Line
- ISRegSpy error on Image Build that contains a VFP / COM / OlePublic DLL
- Installshield Installer MSI Error : Could not load assembly by name "abcd", Version : 6.0.0.0
- ISEXP : fatal error -6017: Internal build error
- InstallShield Dynamic File Linking can't overwrite
- Registry changes in patch moved to WOW6432Node key for 64-bit msi in Installshield QuickPatch project
- Command line arguments for msiexec break on PowerShell if they contain space