msvcp140.dll, vcruntime140.dll, msvcr100.dll… errors: fixing Visual C++ errors

The msvcp…, msvcr…, vcruntime…, mfc… and vcomp… files belong to Microsoft’s Visual C++ runtime libraries. Almost every Windows game and program uses one of these versions: when it is missing, the program refuses to start.

This guide explains how to find the right version and install it properly.

In short

Look at the number in the file name (140, 120, 110, 100…): it tells you which version of Visual C++ to install (table below).
Install Microsoft’s official package, in both x86 and x64 versions on 64-bit Windows.
For a single file, you can also download the DLL and copy it to the program’s folder.

Which Visual C++ package should you install?

The number after msvcp, msvcr, vcruntime, mfc or vcomp matches a specific version of Visual C++:

Files	Package to install
msvcp140.dll, vcruntime140.dll, vcruntime140_1.dll, concrt140.dll, vcomp140.dll, mfc140.dll	Visual C++ 2015-2022 (a single package for 2015, 2017, 2019 and 2022)
msvcr120.dll, msvcp120.dll, mfc120.dll	Visual C++ 2013
msvcr110.dll, msvcp110.dll, mfc110.dll	Visual C++ 2012
msvcr100.dll, msvcp100.dll, mfc100.dll	Visual C++ 2010
msvcr90.dll, msvcp90.dll	Visual C++ 2008
msvcr80.dll, msvcp80.dll	Visual C++ 2005
msvcr71.dll, msvcp71.dll	Visual C++ .NET 2003: no official package, the file must be in the program’s folder
ucrtbase.dll, api-ms-win-crt-*.dll	Universal C Runtime: built into Windows 10 and 11; on Windows 7 and 8.1, Windows Update (KB2999226) or the 2015-2022 package
files ending in “d” (msvcp140d.dll…)	Debug versions: provided only with Visual Studio

The packages do not replace each other: the 2015-2022 package does not contain msvcr100.dll, for example. It is normal to have several of them installed.

Installing or repairing the package

Download the package from Microsoft’s website: Visual C++ 2015-2022 (64-bit), Visual C++ 2015-2022 (32-bit), or the older versions on the official Visual C++ packages page.
Close the program that shows the error, run the downloaded file and accept the licence.
Message “Another version of this product is already installed”? The package is there but may be damaged: Settings › Apps › Installed apps › select the Visual C++ package concerned › Modify › Repair.
Restart your computer, then launch the program again.

32-bit or 64-bit: why install both?

What matters is the architecture of the program, not that of Windows. A 32-bit game needs the x86 package, even on 64-bit Windows. As it is hard to know how a program was compiled, install both versions (x86 and x64) on 64-bit Windows: they do not get in each other’s way.

To check your version of Windows: Settings › System › About › System type. On 32-bit Windows, only the x86 package can be installed.

The _CommonRedist folder trick

Many games (especially on Steam) ship the right packages in their own folder: look for a _CommonRedist\vcredist folder in the game’s installation folder, then run the vcredist_x86.exe and vcredist_x64.exe files of the year shown. You are then sure to install exactly the version the game expects.

If the error persists

“Entry point not found” in msvcp140.dll or vcruntime140.dll: the installed version is too old for the program. Install the latest 2015-2022 package from the Microsoft link above.
File ending in “d” (msvcp140d.dll, msvcr100d.dll…): this is a debug version; the program was compiled for developers, ask its publisher for another version.
Antivirus: check that it has not quarantined the file.
Damaged system files: repair Windows with SFC and DISM (see the missing system DLL guide).
Error 0xc000007b: 32-bit and 64-bit DLLs have been mixed up; see the error 0xc000007b guide.
As a last resort, reinstall the program concerned: its installation often includes the required packages.

DLL files concerned

Each file page offers the download of the file alone and the complete method suited to it.

Frequently asked questions

Can I uninstall the old Visual C++ packages?

Better to keep them: each version is used by different programs, and keeping them causes no problem. Uninstalling them is precisely what causes missing DLL errors.

Does the 2015-2022 package replace 2010 or 2013?

No. It only covers versions 2015, 2017, 2019 and 2022. Versions 2005 to 2013 are installed separately.

Other guides

DirectX errors (d3dx9, xinput, d3dcompiler) steam_api.dll error unarc.dll / ISDone.dll error Missing Windows system DLL Error 0xc000007b (32-bit / 64-bit DLL)