MSVCP140.dll or VCRUNTIME140.dll Was Not Found

What these DLLs are

msvcp140.dll is part of the C++ Standard Library, and vcruntime140.dll / vcruntime140_1.dll are Runtime components. The 140 in the name marks the Visual C++ v14 toolset family (Visual Studio 2015 and later, binary-compatible through current v14 builds). The supported fix is to install or repair the matching architecture of the official Visual C++ Redistributable — not to chase individual DLL files.

Microsoft documents which redistributable DLLs belong together on Determining which DLLs to redistribute.

vcruntime140 dll was not found

Treat vcruntime140.dll was not found and vcruntime140_1.dll was not found as the same named-DLL failure family: they are the same v14 Redistributable family. You do not need a separate product page — use the install matrix below.

The full dialog often reads: The code execution cannot proceed because msvcp140.dll was not found (or the vcruntime variant). That wording is a missing-dependency failure path. It is related to, but not the same error code as, 0xc000007b (STATUS_INVALID_IMAGE_FORMAT, often a bitness mismatch). If your primary complaint is 0xc000007b, use the home tree first.

Confirm the app bitness, then install

1. Confirm whether the failing app is 32-bit or 64-bit. Prefer Task Manager’s Architecture column, or the steps on 0xc000007b 32-bit redistributable missing. Also see the home bitness step.
2. Open Microsoft’s official Visual C++ Redistributable page on the package step.
3. Install X86 and/or X64 to match the app. On 64-bit Windows, 32-bit apps still need the X86 package.
4. If that package is already installed, run the same installer again and choose Repair (or vc_redist.x86.exe /repair / vc_redist.x64.exe /repair).
5. Restart Windows, then retry the app.

x86 / x64 install matrix

Architecture must match the app’s target architecture — Microsoft states this on the Learn redistributable page. Details on central deployment and repair options: Redistributing Visual C++ files.

Open the official Visual C++ Redistributable page on Microsoft Learn On that page, choose the X86 and/or X64 button that matches your app. We never host DLL files.

Do not

Still failing?

If the named DLL error persists after install/repair of the matching architecture:

• Return to the home system-files step for system-file checks, then use the still-failing step for next diagnostics.
• If you came from a game or launcher, also read came from a game.
• Contact the app vendor if their installer should have shipped the runtime.

FAQ

Why do I see “The code execution cannot proceed because msvcp140.dll was not found”?

Windows cannot load that Visual C++ v14 library for the app. Install or repair the official Redistributable that matches the app’s bitness (install matrix).

Is this the same as 0xc000007b?

No. Named “was not found” messages are a missing-dependency failure path. 0xc000007b is a different status (invalid image format), often from mixing 32-bit and 64-bit modules. Related troubleshooting, different code — start on 0xc000007b if that is what the dialog shows.

Do I need both x86 and x64 Visual C++ Redistributables?

Install what the failing app needs. Many PCs end up with both because they run both 32-bit and 64-bit software. That is common practice, not a universal mandate.

Can I fix this by copying msvcp140.dll into System32?

No. Do not download or copy loose DLLs into system folders. Use the official Redistributable only.

What about vcruntime140.dll / vcruntime140_1.dll?

Same v14 Redistributable family and the same install/repair steps as msvcp140.dll. See these DLLs.

How do I repair an existing Visual C++ Redistributable install?

Re-run the matching vc_redist.x86.exe or vc_redist.x64.exe from Microsoft Learn and choose Repair, or pass /repair on the command line. Prefer keeping a newer installed version if Windows reports a newer package is already present.