32-bit x86 installer
What does not
64-bit x86_64 installer, it puts the files into syswow64 (wrong folder, it's for 32-bit)
What was not tested
although 32-bit installer is flawless, giving bronze rating here as the 64-bit installer has issues.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Fedora 19 x86_64||May 02 2015||1.7.42||Yes||Yes||Bronze||Anastasius Focht|
|Show||Ubuntu 14.10 "Utopic" i386 (+ variants like Kubuntu)||Oct 29 2014||1.7.29||No||Not installable||Garbage||Chris Z|
|Show||Linux Mint 17 "Qiana" x86_64||Nov 20 2014||1.6.2||No||Not installable||Garbage||an anonymous user|
|Show||Fedora 19 x86_64||Dec 15 2013||1.7.8||No||Not installable||Garbage||Anastasius Focht|
|Show||Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu)||Apr 08 2013||1.5.27||No||Not installable||Garbage||Nell Hardcastle|
|Bug #||Description||Status||Resolution||Other apps affected|
|17273||Many apps and games need SetNamedPipeHandleState implementation (support for named pipe message mode)(FireFox+Flash, Win8/NET 4.x SDK/vcrun2012, WiX installers)||CLOSED||FIXED||View|
|30713||Microsoft Visual C++ 64-bit redistributables get incorrectly installed into SysWOW64 (system directory for 32-bit files) when run under 64-bit Wine||CLOSED||FIXED||View|
|33576||Multiple applications need persistence support for ACL/file security information (storage in extended file attributes)(Paint Tool SAI, Finale Notepad 2012, SmartDeviceMonitor)||STAGED||View|
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
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.