Download Vcredist 2015 64 Bit

0 views
Skip to first unread message

Jodee Bouman

unread,
Aug 5, 2024, 1:57:14 AM8/5/24
to soulfacoxi
Ihave a c++ application developed using Visual Studio 2015, along with a Wix installer and a Burn bootstrapper. Previous versions of the application were able to use the Visual Studio merge module to install the necessary prerequisites, but it appears that this isn't an option when using Visual Studio 2015 (see Redistributables for deploying C++ exe developed with Visual Studio 2015 on Windows 7).

Following the advice in that link, we have started installing vcredist with Burn using an ExePackage with vital="yes". This mostly works great - we've had several customers who have the installation fail because of various issues with vcredist. Until recently, these were errors that should cause the installation to fail.


In the past couple of days we've received several reports of our installer failing due to a newer version of the redistributable being installed: vcredist fails with error code 0x80070666, which causes our bootstrapper to fail.


You can use the FileSearch Element (Util Extension) to search for one of the vcredist files and retrieve its version. However this approach is complicated by the fact the burn built in variables SystemFolder and System64Folder are reversed with respect the similar variables in Windows Installer. Example of searches for VC14:


Edit 2: In the installers that I author I generally don't try to detect the presence of VC Redist. Instead I let the VC Redist installer run and let itself figure out whether to install, upgrade or do nothing.


I ran into a similar problem recently where a product installer I was working on halted with error 0x80070666. The problem was a newer version of vcredist already installed. The solution I ended up using was: a) include the latest version of vcredist (14.0.23918), and b) add the directive to tell burn not to throw an error if a future newer version of vcredist is already installed.


When I however then run an interactive Powershell with the container and install the vcredist like above, the right dlls get registered. I can stop and commit the container as new image:tag.


ERROR: ERROR: Installation of VCRedist Version 2017 failed with error . This could be due to insufficient OS patch level. Install Microsoft patch KB2999226 and try installing again. If the problem is not resolved after installing the Microsoft Patch, please contact your Windows administrator.


This is version 14.16.27027 - which other versions of Microsoft Visual C 2017 Redistributable (x64) are installed? Obvs a later one and I guess this is the problem. You can find this out in add/remove software.


Problem was solved.

Indeed it was a corrupt installation on machine where some version of VCredist 2017 (universal vcredist) was visible in appwiz.cpl and some other version was visible via registry.

3a8082e126
Reply all
Reply to author
Forward
0 new messages