What does not
What was not tested
Visual C++ 2013 Runtime (x86)
Visual C++ 2013 Runtime (x86_64)
Visual C++ 2013 Runtime (ARM)
See bug #35790
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Fedora 19 x86_64||May 02 2015||1.7.42||Yes||Yes||Bronze||Anastasius Focht|
|Show||Debian GNU/Linux 7.x "Wheezy"||Apr 21 2015||1.7.41||No||Not installable||Garbage||an anonymous user|
|Show||Mac OS X 10.9 "Mavericks"||Jul 13 2014||1.7.21||No||Not installable||Garbage||Qais Patankar|
|Current||Fedora 20 x86_64||Mar 15 2014||1.7.13||No||Not installable||Garbage||Patrick Martin|
Always use winver "Windows XP" or later when running the Visual C runtime installer!
Don't install Visual C 2005 and later runtime using Wine winver "Windows 2000" or earlier when you intend to switch to winver > "Windows 2000" later! With winver "Windows 2000" the Visual C runtime installer will install assemblies in both, the side-by-side "WinSxS" storage and System32 directory.
If the loader fails to locate assemblies in WinSxS due to assembly manifest mismatch it fall back to load from System32 (Wine doesn't support assembly binding redirects yet). When the Visual C runtime is loaded from system32 directory in winver > "Windows 2000" mode, you will get the infamous:
ÂThis is due to checks done by the Visual C runtime itself upon load. By design, such assemblies are never to be loaded from System32 with winver set to > "Windows 2000"!
Visual C runtime uses FindActCtxSectionString API to check for
activation context support and if present it prevents any runtimes from
being loaded from system32 directory.
The 32-bit Visual C++ Redistributable installer can be run without issues, given a recent Wine version and clean WINEPREFIX (~/.wine)
For the 64-bit Visual C++ Redistributable installation you must use WinÂetricks which takes care of some problems.
$ Âwget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
$ bash winetricks -q vcrun2010