It doesn't help adding the .cab package with dism will simply just make the package installed setrstor.exe will not be processed or executed what i mean is, having the update installed is not a big deal the update is ment for one specific issue, if you are not affected or the update (setrstor) is failing, adding dism package is not useful or required at all and no need to move anything, .cab can be installed from anywhere
I did this and works!...Thanks! o dism /online /add-package /packagepath:C:\Windows\SoftwareDistribution\Download\c4a1b8896ce9fbfea96c1ee6890d52a5\windows10.0-kb3122947-x64.cab
Burf these “real” 12.0.30501.0 files are not what you think… you took them from Office 2016 beta, right? They are not meant to go in system32 and may not work with actual VS12 apps… these betas were compiled with a unreleased internal alpha of VS14, and the version number is a leftover
This isn't perfectly fine, this is horrible. This is worse than using Comic Sans. For any supported release of the VC++ compiler there is a supported set of redistributable runtimes, and that's all that matters. You don't use whatever has the highest version number, you use the runtimes matching the compiler. And you especially don't mix and match DLLs from different releases into one set of runtimes.
@burfadel i can't run Installer.cmd as admin and i dont know why. Window pops out for milisecond an thats it. It's ok now ,i unpack first and tray run Installer.cmd but this must be run with installer without unpackind.
Wow, what tact you have. You would make a great negotiator lol. The runtimes are for the most part cumulative. Meaning that in Visual Studio 2013, you can have a later redist installed and it is fine. You don't need a separate redist for each version of Visual Studio 2013 (and all the others) runtimes for each program that uses these versions. The key points would be not to mix up App based CRT's with desktop based ones, nor .NET Framework versions with standard versions. If I did the latter, I would be using 12.0.52512.0. Using the 30501 files in the redist in this case is fine. The runtimes are made of 'core' files (msvcr120.dll and msvcp120.dll), the remaining minimum files, and the additional files. On any system at any time, there is probably a mismatch of these anyway, due to different programs being installed etc. The additional and minimum components are separate, and the core files (msvcr120.dll and msvcp120.dll) are the main files used the majority of the time. The remaining minimum files are there as well. Now, the only chance of it being an issue is if the new msvc files have a different output or different command syntax for something, which they don't. They are simple bug fixes, as well as possible security and performance improvements (the last two being unlikely in this case, so mainly bug fixes). So, that is why in this case it is perfectly fine. If you believe that it is compiler and runtime specific, you will have to hunt down every vcredist ever made (both easy downloadable releases and 'hidden') to cover every program you might come across. Good luck with that .
Good day guys... I have a 1511 iso.. i want to make an updated wim... what are the updates i need to integrate to wim? Do I only need the 2 updates inside the 10586 folder (WHD Updates) ? or do i still need to integrate the Baseline updates? thanks.
No, no, no! The files you inserted are NOT VC12 library files, they just happen to have the same name! They are not redistributable and are NOT guaranteed to work with VC12 apps! You are correct that new versions of actual redistributable files are backward-compatible.
Are you sure? I tested it out with several VC 2012 programs. The programs will load the dll's from the executable location first before the system folders, which is why if you want to use the latest version properly you need to remove these (or replace them manually). This is also how things like SweetFX, Reshade etc work for games. The programs worked perfectly, and I made sure it was using the files in the folder (plus you can't delete them if they're in use). What made you think they aren't desktop (non-APP and non-.NET) VC 12 library files?