Visual C 2012 Redist Download For Update

Its best to check for all components you need though (msvcr110.dll, msvcp110.dll, mfc,.). And for update 3 the version is 11.0.60610.1.

I wish there was a magic bullet, but if there is, I havent found it yet.

Ive got an answer down below for some specific redists that seem to work 100 of the time to help with currently most of them.

I have spent ages looking for a reliable method and this seems to be the one, I think with all the other unreliable answers it will help a lot of people to find the right information.

Visual C 2012 Redist Download For Update

These two 2012 keys have worked well for me with their corresponding versions to download for Update 4.

Please be aware that some of these reg locations may be OS-dependent.

Im just going to go ahead and dump all of these redist versions and the reg keys I search for to detect installation.

Version: 9.0.30729.6161 (Actual Version data in registry: 0x9007809 DWORD).

There also doesnt appear to be a standalone installer for Visual C 2019, only this bundle installer that is Visual C 2015 through 2019.

August 19th, 2019 -- Added a new version of 2015-2019 bundle version June 13th, 2019 -- Added a new section for the 2015-2019 bundle version 14.21.27702 and added small notes to the 2015 and 2017 sections about considering the usage of the new bundle as an alternative.

December 14th, 2018 -- Updated MSVC2008 for Service Pack 1s 9.0.30729.6161 update per Jim Wolffs findings November 27th, 2018 -- Updated info for MSVC2017 v.

September 12th, 2018 -- Added version caveat to 2012 Update 4 per Wai Ha Lees findings August 24th, 2018 -- Updated 2017s version for 14.15.26706, the updated Visual C dependencies packaged with VS 2017 15.8.1 May 16th, 2018 -- Updated 2017s version for 14.14.26405.0 as the new C 2017 entry.

September 8th, 2017 -- Updated 2017s version for 14.11.25325.0 as the new Visual C 2017 entry.

April 7th, 2017 -- Updated 2017s version of 14.10.25008.0 as the new Visual C 2017 entry October 24th, 2016 -- Updated 2015s version info for 14.0.24215.1 August 18th, 2016 -- Updated 2015s version info for 14.0.24212 May 27th, 2016 -- Updated info for MSVC2015 Update 2.

For every future update Launching the pre Update 1 VCRedist with Update 1 installed gave me an error - so Im going to use the VC installer reg key - which seems to be fine if you use VCRedist.

I just noticed that they seemed to actually follow something resembling a scheme this time around for 2017, instead of just throwing another GUID somewhere without a meaningful parent key name.

I will be using this as a check for installing the VC 11 (VS 2012) runtime.

I do have the key in Daves answer HKLMSOFTWAREMicrosoftDevDivVCServicing11.0.

Guess Microsoft wants to always install if you set it as a prerequisite.

Also, if you have a 64 bit EXE, you will have to check for both, the 32 AND 64 bit runtimes.

Just run (which means the runtimes are installed) or fail to run (when not installed).

The executables will be around 4KB in size - a small price to pay for a sure result.

Registry keys are all fine and such, but if the user messed with the system and deleted msvcr110.dll the registry check is useless.

Its best to check for all components you need though (msvcr110.dll, msvcp110.dll, mfc,.).