DLL ERRORS · VISUAL C++ RUNTIMES

MSVCP140.dll not found: repair the Visual C++ runtime

MSVCP140.dll belongs to Microsoft Visual C++. Repair the complete runtime instead of downloading a DLL from an unknown site.

The short answer

Repair the complete Visual C++ runtime instead of downloading MSVCP140.dll on its own.

Use the Microsoft Visual C++ v14 package required by the application. Select x86 for a 32-bit process, or x64 or ARM64 as appropriate. Match the launcher and game separately if their architectures differ, then relaunch.

Common symptoms

Common symptoms of an MSVCP140.dll issue include:

  • Code execution cannot proceed because MSVCP140.dll was not found
  • The application cannot start and reports a missing DLL
  • The error appears after updating or reinstalling a game
  • Some games work while one specific game cannot launch

An original screenshot of this message is not available here. Compare the full error with the details below.

What causes MSVCP140.dll

This file belongs to Visual C++; missing files, corruption or an architecture mismatch may be responsible.

Possible causeDetails
Runtime not installedThe required Visual C++ v14 runtime version is missing.
MSVCP140.dll · 14.51.36247.0This System32 sample on Windows 11 build 22621 had a valid signature. Its import table lists both VCRUNTIME140.dll and VCRUNTIME140_1.dll, which explains why copying one file can still leave a dependency unresolved.
Damaged runtime filesInterrupted updates, disk errors or cleanup damaged the DLL
Only one architecture installedA 64-bit system may still need x86 runtimes for 32-bit games
Incomplete game filesDependencies or launcher components are missing
Security software interferenceRequired runtime files were quarantined or removed

Repair steps

Follow these 4 steps in order, starting with the simplest checks.

1

Repair the required Visual C++ v14 package

Difficulty: Easy2–5 min

Run the Microsoft v14 installer for the architecture of the failing process and choose Install or Repair.

Check after repair

Check Installed apps for the selected v14 package, then reopen the same executable.

2

Restart and reload components

Difficulty: Easy2–3 min

Restart Windows after repairing runtimes so that files in use can be replaced.

Check after repair

After restarting, launch the game and check whether the error is gone.

3

Verify game file integrity

Difficulty: Easy5–15 min

Use the platform's file verification to restore missing launcher files or dependencies.

Check after repair

After verification, the platform should confirm integrity or redownload missing files.

4

Check system files and security software

Difficulty: Moderate10–20 min

If the error persists, check system files and whether trusted runtime components were quarantined.

Check after repair

Restart after repairs and check that the application launches reliably.

Verify the fix

Check these results after completing the repair:

The missing MSVCP140.dll message no longer appears.The game or app reaches its main screen and runs normally.The error does not return after restarting the PC.

Frequently asked questions

Do “MSVCP140.dll missing” and “MSVCP140.dll was not found” mean the same thing?

Both messages identify MSVCP140.dll. Check the Microsoft v14 package for the architecture of the failing process, then relaunch that program.

Can I download MSVCP140.dll into the game folder?

This is not recommended. Its version or architecture may not match, and other runtime dependencies may still be missing.

Why does 64-bit Windows need x86 runtimes?

Many games and launchers are 32-bit programs and need x86 runtimes even on 64-bit Windows.

Will reinstalling the game always help?

Not necessarily. Reinstalling a game may not restore a missing or damaged system-wide Visual C++ runtime.

Need a hand? Explore Baomiao Repair Tool

Check system settings, game components and common issues for repair suggestions.

Get Baomiao Repair Tool
  • Safety first
  • No game-data changes
  • For popular games on Windows