Visual C++ Redistributable Package

No Screenshot

Submit Screenshot
The Microsoft Visual C++ 2013 Redistributable Package (x86,x86_64 and ARM)

Application Details:

Version: 2013 (18.0.21005.1)
License: Retail
Votes: 0
Latest Rating: Bronze
Latest Wine Version Tested: 1.7.42

Maintainers: About Maintainership

No maintainers. Volunteer today!

Free Download Microsoft Visual C++ Redistributable 2013

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works


What does not



What was not tested

The operation of the library

Hardware tested


  • GPU:
  • Driver:

Additional Comments

Tested on ARMv7 with latest Git wine wine-1.7.41-15-gf3ff3e5 It fails with the 0x80090008 code.(null) 008:0029][2015-04-21T10:43:13]i304: Verified existing payload: vcRuntimeMinimum_arm at path: C:\users\Public\Application Data\Package Cache\{4B40C146-0B39-3D95-9311-B13DC2B074A9}v12.0.21005\packages\vcRuntimeMinimum_arm\vc_runtimeMinimum_arm.msi. [0008:0029][2015-04-21T10:43:13]e000: Error 0x80090008: Failed authenticode verification of payload: C:\users\Public\Application Data\Package Cache\.unverified\cab79BAAF42132B450E6546E387FB9BEFC1 [0008:0029][2015-04-21T10:43:13]e000: Error 0x80090008: Failed to verify signature of payload: cab79BAAF42132B450E6546E387FB9BEFC1 [0008:0029][2015-04-21T10:43:13]e310: Failed to verify payload: cab79BAAF42132B450E6546E387FB9BEFC1 at path: C:\users\Public\Application Data\Package Cache\.unverified\cab79BAAF42132B450E6546E387FB9BEFC1, error: 0x80090008. Deleting file. [0008:0029][2015-04-21T10:43:15]e000: Error 0x80090008: Failed to cache payload: cab79BAAF42132B450E6546E387FB9BEFC1 [0024:002B][2015-04-21T10:43:15]e314: Failed to cache payload: cab79BAAF42132B450E6546E387FB9BEFC1 from working path: C:\users\cubie\Temp\{1923ba03-9825-4803-b1c8-2b2f5291ab66}\cab79BAAF42132B450E6546E387FB9BEFC1 I can almost safely say that it's a crypto error. ========= Maintainer NOTE: Although interesting, ARM support is very low priority. There are like a dozen people around the world that actually use/run RT/cross compiled ARM apps with Wine on ARM (since RT/Xdev zone died almost off, there is not much interest given a very low number of available/cross compiled apps).

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowFedora 19 x86_64May 02 20151.7.42Yes Yes BronzeAnastasius Focht 
CurrentDebian GNU/Linux 7.x "Wheezy"Apr 21 20151.7.41No Not installable Garbagean anonymous user 
ShowMac OS X 10.9 "Mavericks"Jul 13 20141.7.21No Not installable GarbageQais Patankar 
ShowFedora 20 x86_64Mar 15 20141.7.13No Not installable GarbagePatrick Martin 

Known Bugs

Bug # Description Status Resolution Other apps affected
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

Show all bugs

HowTo / Notes


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:

­R6034: An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for moreinformation.

­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"!

The 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.

  • 64-bit versions supported as of 2015-05-02: vcrun2010
  • 64-bit versions not supported as of 2015-05-02: vcrun2012, vcrun2013

$ ­wget

$ bash winetricks -q vcrun2010

It's possible to work around manually by copying the dlls into the correct folders. Do that at your own risk (no support).


Comments Disabled

Comments for this application have been disabled because there are no maintainers.