Installed with App-V 4.6 SP2 & 5.0 SP2, maybe others too. Version seen at one point for crt/atl source unknown. Required by App-V 4.6RTM and 4.6.1 Sequencer and Client, claims to be an 2005 SP1 in App-V Installer.
VS 2005 Team Suite SP1 Update for Windows Vistaħ.42 file and add remove, 7.4053 files only, 1 files and add remove Microsoft Visual Studio 2005 Team Explorer - ENU These dlls are not compatible with App-V. VC++ 2005 Files are primarily in the C:\Windows\winsxs subfolders look for folders with names like C:\Windows\winsxs\x86_microsoft.vc._1fc8b9a1e18e3b_ or C:\Windows\winsxs\amd64_microsoft.vc._1fc8b9a1e18e3b_ VS DotNet 2003 SP1 MFC71.dll Security Update VS DotNet 2002 Service Pack 1 MFC70.dll Security Update This installer is an exe that requires the previous version to patch. These dlls are compatible with App-V and do not require special treatment when sequencing. The older runtimes are "non managed" dlls, which means they are not DotNet and are just placed in the folder. These dlls should be compatible with App-V. VS 2002/2003 Files are primarily in the C:\Windows\system32 subfolders look for files with names like C:\Windows\system32\mfc7*.dll, where 70 is the VS 2002 version and 71 is the VS 2003 version. When you sequence a package and see a VC Runtime file, grab the version string and consult these tables to find the exact installer that you need to use external to the package. Several versions have known vulnerabilities, and are fixed in security updates. There is a good security reason to keep these out of the package as well. You can override that behavior via sequencer option on the package, but it would be better to just keep them out of the package.
Those indicated as incompatible also don't work on App-V 5 inside the package, in which case (by default) the sequencer will detect these incompatible versions and automatically install them on the App-V client by extracting them from the package when published. See this blog article for explanation.Įxcept where indicated, these are incompatible with App-V 4 packages. This is a really useful mapping for when you catch one of these in your package you can use it to figure out exactly what the prerequisite is.
Run the Modify Setup repair functionality for Microsoft Visual C++ 2012 Redistributable by starting the installer from the following Microsoft Download Center website:A list of known VC Runtime version numbers and installers, including mapping to KBs.After the repair process is completed, restart the computer if you are prompted to do this.
In the Modify Setup dialog box, click Repair.Right-click the entry name, and then click Change.
In the programs list, locate Microsoft Visual C++ 2012 Redistributable (X64) - 0 or Microsoft Visual C++ 2012 Redistributable (X86) - 0, depending on your system architecture.In Control Panel, click Uninstall a program in the Programs group.In the meantime, we recommend that customers who are receiving multiple offers of KB3119142 try the following methods to work around this issue. Microsoft is working to address this issue.
Unity Pro install returns the error 'The installation of Microsoft visual C++ 2012 Update 4 Redistributable Package failed'. Installing Unity Pro returns the error 'The installation of Microsoft visual C++ 2012 Update 4 Redistributeable Package failed.