[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Alex_Farber
Level 3

Prerequisite condition for VC++ x86 runtime

Jump to solution

I added VC++ 64 bit runtime prerequisite to my InstallShild project. File VC_redist.x64 is downloaded from Microsoft page 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:

Prerequisite ConditionPrerequisite Condition

Everything is OK for x64. Now I want to add VC++ x86 runtime to the same project. File VC_redist.x86, 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.

 

 

 

Labels (1)
0 Kudos
1 Solution
shunt
Revenera Moderator Revenera Moderator
Revenera Moderator

Take a look at the following Microsoft article which suggests using an alternative registry entry in:

HKEY_LOCAL_MACHINE\SOFTWARE[\Wow6432Node]\Microsoft\VisualStudio\14.0\VC\Runtimes\x86

https://learn.microsoft.com/en-us/cpp/windows/redistributing-visual-cpp-files?view=msvc-170

View solution in original post

0 Kudos
1 Reply
shunt
Revenera Moderator Revenera Moderator
Revenera Moderator

Take a look at the following Microsoft article which suggests using an alternative registry entry in:

HKEY_LOCAL_MACHINE\SOFTWARE[\Wow6432Node]\Microsoft\VisualStudio\14.0\VC\Runtimes\x86

https://learn.microsoft.com/en-us/cpp/windows/redistributing-visual-cpp-files?view=msvc-170

0 Kudos