Visual C++ Redistributable: which versions games need and how to install them

What Visual C++ Redistributable is and why games require it

Visual C++ Redistributable installs Microsoft's C and C++ runtime libraries. An application built with Visual Studio does not carry these libraries inside it; it calls them from the operating system. The PC therefore needs a package that is at least as recent as the build tools used to compile the game.

Three points explain most problems:

• It is a system component, not part of the game. Reinstalling the game will not help if the libraries are missing from the system.
• The installed package must be at least as recent as the build tools. A newer package works; an older one does not.
• The package architecture must match the application architecture. That is why 64-bit systems need both packages: many games and launchers are still 32-bit.

Most games install the required packages automatically on first launch, and the game folder usually contains a _CommonRedist or Redist directory. Problems begin when that installation is interrupted, the package is corrupted, or the game is distributed without an installer.

Which versions you need in 2026

Two installers are enough: the current Visual C++ v14 package in x64 and x86 versions. Since Visual Studio 2017, all releases have shared the same package files, so one package covers 2017, 2019, 2022, and 2026. Installing separate packages labelled “2017,” “2019,” and “2022” is unnecessary—a common misconception.

One important point about 2015: support for Visual Studio 2015 ended on 15 October 2025, and the final Visual C++ 2015 package version is 14.0.24212.0. However, the current v14 package is binary-compatible with applications built using the 2015 tools. In most cases, a separate 2015 installer is therefore unnecessary because the current package supersedes it.

Packages from 2013 and earlier install side by side with the current package rather than replacing it. They do not conflict with v14 and are not superseded by it. If an older game specifically requires the 2013 package, install the 2013 package.

Official Microsoft download links

Microsoft's permanent links for the current package:

• x64: https://aka.ms/vc14/vc_redist.x64.exe
• x86: https://aka.ms/vc14/vc_redist.x86.exe
• ARM64: https://aka.ms/vc14/vc_redist.arm64.exe

These addresses always point to the latest supported version, so they are worth saving. The full list, including older versions, is available on the Visual C++ Redistributable downloads page in Microsoft Learn.

Two details are worth knowing:

• The x64 package also includes ARM64 files. This simplifies installation on ARM devices, but it does not remove the need for the x86 package for 32-bit applications.
• The current package supplied with Visual Studio 2026 supports only Windows 10 and 11 , along with Windows Server versions from 2016 through 2025. Older operating systems require earlier package releases.

Microsoft's links for the 2013 packages are also permanent: https://aka.ms/highdpimfc2013x64enu for x64 and https://aka.ms/highdpimfc2013x86enu for x86; the current version is 12.0.40664.0.

Why you need both x86 and x64

This is the most common reason people say, “Everything is installed, but the game still will not launch.” The package architecture must match the application architecture, not the Windows architecture.

• A 64-bit game looks for 64-bit libraries and requires the x64 package.
• A 32-bit game or launcher looks for 32-bit libraries and requires the x86 package, even on 64-bit Windows.
• Many games, anti-cheat services, and launchers are still 32-bit, even when the game executable itself is 64-bit.

The practical conclusion is simple: always install both packages on 64-bit Windows. They do not conflict and together take up only a few dozen megabytes. Installing both is the standard setup, not a workaround.

How to check what is already installed

Open Settings, go to Apps, then Installed apps, and search for Visual C++. You will see the installed packages, their versions, and architectures.

A properly configured system for modern games should include:

• Microsoft Visual C++ 2015-2022 Redistributable (x64) or a newer name with the same meaning.
• Microsoft Visual C++ 2015-2022 Redistributable (x86).
• When required, the 2013, 2012, and 2010 packages in both architectures.

If the required package appears in the list but the error persists, the package may be corrupted. Do not simply install over it: run the installer and select Repair, or remove the package and reinstall it.

Common errors and what they mean

A note about error 0xc000007b: downloading a single DLL almost never fixes it. In fact, an unrelated msvcp140.dll file placed in the game folder “to make it work” is one of the most common causes of this error. Remove such files and install the libraries as a package.

How to install the packages correctly

1. Download both installers from the official links above: x64 and x86.
2. Close the game and its launcher. The installer cannot replace files that are currently in use.
3. Run the installers as administrator, x64 first and then x86. The order is not critical, but this sequence helps avoid confusion.
4. Restart the PC. Some libraries are replaced only after a restart. Skipping this step can create the false impression that the installation did not work.
5. If the package is already installed, select Repair in the installer. This is quicker than removing and reinstalling it.
6. Verify the integrity of the game files in Steam or Epic Games Launcher. Corrupted game files can cause exactly the same symptoms as missing libraries.

If the error remains, check the Windows system files by running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in Command Prompt as administrator. A corrupted component store can prevent any system package from installing correctly.

What not to do

• Do not download individual DLL files from library sites. The file may be the wrong version, use the wrong architecture, or contain malware. Install these libraries only through Microsoft's official package.
• Do not use third-party “All-in-One” Visual C++ 2005–2022 bundles. They usually repackage the same official installers, but without any guarantee of authenticity or current versions.
• Do not remove “unnecessary” Visual C++ packages. Each one may be required by a particular application. You will recover only a few dozen megabytes and may break software you need.
• Do not install a package architecture that does not match your system. An ARM64 package will not install on an x86 system, and an x64 package will not install on 32-bit Windows.

If the error persists

If the packages are installed, the game files have been verified, and the system files have been repaired, but the game still will not launch, the libraries are usually not the cause:

• The anti-cheat blocks startup. Check the game's Secure Boot and virtualization-based security requirements.
• The antivirus removed a game file. Check the quarantine.
• The user profile is corrupted or the account does not have permission to access the game folder.
• There is a memory or storage problem. If other applications also crash or blue screens appear, see our guide to Windows blue screens: how to read the stop code and identify the cause.

If self-diagnosis does not resolve the issue, technical service can check the system files, memory, storage, and overall stability as part of a standard diagnostic procedure in Dubai.