This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Knowledge Base
- :
- Microsoft Visual C++ 2017 Redistributable Prerequisites
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
Microsoft Visual C++ 2017 Redistributable Prerequisites
Microsoft Visual C++ 2017 Redistributable Prerequisites
Summary
Issue in Microsoft file causes prerequisite installation issues.Synopsis
Based on an issue in Microsoft's file causing Registry data deletion we encourage you to update to the most recent version of Visual Studio 2017 so that you always get the latest features, fixes, and improvements.Use Microsoft Visual C++ Redistributable for Visual Studio 2017 with file version 14.10.5017.0 or later to avoid potential installation issues.
32-bit (x86) URL to file:
https://download.microsoft.com/download/1/f/e/1febbdb2-aded-4e14-9063-39fb17e88444/vc_redist.x86.exe
64-bit (x64) URL to file:
https://download.microsoft.com/download/3/b/f/3bf6e759-c555-4595-8973-86b7b4312927/vc_redist.x64.exe
Discussion
Reference Microsoft release notes:Visual Studio 2017 version 15.9 Release Notes
https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
VC Runtime Redistributable Update for VS 15.9 deletes Registry Key
https://developercommunity.visualstudio.com/content/problem/383873/vc-runtime-redistributable-update-for-vs-159-delet.html
Prerequisites are provided as a convenience. Based on circumstances outside of our control the way conditions are applied need to change. Therefore, if you are experiencing an issue with the conditions of prerequisite modify the condition using the Prerequisite Editor.
Workaround
In this particular matter you may determine the condition for "Microsoft Visual C ++ 2017 Redistributable Package (x86)" does not meet your needs. Consider implementing one of the following approaches:Registry uninstall data approach:
<condition Type="1" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{582EA838-9199-3518-A05C-DB09462F68EC}" FileName="" ReturnValue=""/>
File version approach:
<condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x86\" FileName="Version" ReturnValue="v14.10.25017.00"/>
No ratings