VCRUNTIME140.dll and MSVCP140.dll Missing Errors: Visual C++ Redistributable Repair Guide

by

Few Windows error messages are as frustrating as launching a game, design app, accounting tool, or productivity program and seeing: “The code execution cannot proceed because VCRUNTIME140.dll was not found” or “MSVCP140.dll is missing from your computer.” These messages sound highly technical, but the fix is usually straightforward: the application needs a Microsoft Visual C++ runtime component that is missing, damaged, or mismatched.

TLDR: VCRUNTIME140.dll and MSVCP140.dll are Microsoft Visual C++ runtime files used by many Windows programs and games. If they are missing or corrupted, reinstalling or repairing the correct Microsoft Visual C++ Redistributable package usually solves the problem. Avoid downloading DLL files from random websites, because that can introduce malware or version conflicts. The safest fix is to install the latest supported Visual C++ Redistributables from Microsoft and then restart your PC.

Contents

What Are VCRUNTIME140.dll and MSVCP140.dll?

The files VCRUNTIME140.dll and MSVCP140.dll are part of the Microsoft Visual C++ Redistributable, a package that provides shared code libraries used by software built with Microsoft Visual Studio. Instead of every developer bundling all required runtime code inside their app, Windows programs can rely on these redistributable libraries being installed on the system.

VCRUNTIME140.dll contains essential runtime functions for programs compiled with Visual C++. MSVCP140.dll is related to the Microsoft C++ Standard Library, which includes common programming features such as strings, input/output operations, containers, and memory handling.

In plain English: if a program was built using Visual C++, it may need these DLL files to run. If Windows cannot find them, the program may refuse to start.

Common Error Messages You Might See

The wording can vary slightly depending on the application, Windows version, and affected runtime file. Common examples include:

  • “VCRUNTIME140.dll is missing from your computer.”
  • “MSVCP140.dll was not found.”
  • “The code execution cannot proceed because VCRUNTIME140.dll was not found.”
  • “The program can’t start because MSVCP140.dll is missing.”
  • “Error loading VCRUNTIME140.dll. The specified module could not be found.”

These errors often appear after installing a new program, updating Windows, moving software between drives, restoring a system backup, or removing older applications that accidentally took shared components with them.

Why These DLL Errors Happen

Although the message says a DLL file is missing, the underlying cause can be more than a simple deleted file. Here are the most common reasons:

  • The Visual C++ Redistributable is not installed: Some apps assume the required runtime is already present.
  • The installation is damaged: A failed update, hard drive issue, or interrupted installation can corrupt runtime files.
  • The wrong architecture is installed: A 64-bit PC may still need the 32-bit package for 32-bit apps.
  • An application folder is incomplete: Some software includes local DLL files, and they may be missing after a manual copy or migration.
  • Security software quarantined a file: Rarely, antivirus software may flag or isolate a runtime file or related program file.
  • Windows system files are damaged: Broader operating system corruption can affect shared libraries and app loading.

The Golden Rule: Do Not Download Random DLL Files

When searching online, you may find websites offering individual downloads for VCRUNTIME140.dll or MSVCP140.dll. This is tempting, especially if you want a quick fix, but it is risky.

Individual DLL download sites may provide outdated, incompatible, modified, or malicious files. Even if the file is clean, placing it in the wrong folder can cause new problems. DLL files are not just interchangeable puzzle pieces; they must match the correct runtime version, architecture, and dependency chain.

The safer approach is to install or repair the official Microsoft Visual C++ Redistributable package. That ensures Windows receives the correct files in the correct locations with the proper registration and supporting components.

Step 1: Install the Latest Visual C++ Redistributable

The most reliable fix is to install the latest supported Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022. These versions share a unified redistributable, which means the newest package generally covers apps built with those toolsets.

For most modern Windows systems, install both of these:

  • x64 version: Required for 64-bit applications on 64-bit Windows.
  • x86 version: Required for 32-bit applications, even on 64-bit Windows.

This point surprises many users. A 64-bit version of Windows can run both 64-bit and 32-bit applications. If the problem program is 32-bit, it may require the x86 redistributable even when your computer itself is 64-bit.

  1. Go to Microsoft’s official Visual C++ Redistributable download page.
  2. Download the latest x64 installer.
  3. Download the latest x86 installer.
  4. Run each installer and choose Install or Repair if prompted.
  5. Restart your computer.
  6. Launch the affected program again.

Step 2: Use the Repair Option

If the Visual C++ Redistributable is already installed, the installer may offer a Repair option. Use it. Repairing checks the installed runtime and replaces missing or damaged components.

You can also repair it through Windows settings:

  1. Open Settings.
  2. Go to Apps and then Installed apps or Apps & features.
  3. Search for Microsoft Visual C++.
  4. Find the relevant 2015–2022 Redistributable entries.
  5. Select Modify.
  6. Choose Repair.

After the repair finishes, restart Windows. Runtime files are often loaded in memory, so rebooting helps ensure the repaired versions are used.

Step 3: Reinstall the Affected Application

If repairing the redistributable does not help, the application itself may be incomplete or misconfigured. This is especially common with games, plugins, older business tools, and programs copied manually from another computer.

Uninstall the application, restart your PC, and install it again from a trusted source. If the application has a launcher, such as a game client or software manager, use its verify files or repair installation feature. These tools compare installed files against official versions and restore anything missing.

Step 4: Check Windows Update

Windows Update can provide important system components, compatibility improvements, and security fixes. While Windows Update may not always install every Visual C++ Redistributable you need, keeping the system current reduces the chance of related runtime issues.

  1. Open Settings.
  2. Go to Windows Update.
  3. Click Check for updates.
  4. Install all recommended updates.
  5. Restart the computer if required.

Step 5: Run System File Checker

If multiple programs are failing or Windows behaves strangely, the issue may involve system file corruption. Windows includes a built-in tool called System File Checker, commonly known as SFC.

To run it:

  1. Right-click the Start button.
  2. Open Terminal, Command Prompt, or Windows PowerShell as administrator.
  3. Type sfc /scannow and press Enter.
  4. Wait for the scan to complete.
  5. Restart your computer.

If SFC reports that it found and repaired files, try launching the program again. If it reports that some files could not be repaired, you can follow up with the DISM tool.

Run this command in an administrator terminal:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run sfc /scannow again.

Step 6: Confirm Antivirus or Security Software Is Not Interfering

Security software can occasionally quarantine program files, especially if an application is old, obscure, modified, or downloaded from an unofficial source. Open your antivirus or Windows Security history and check whether anything related to the affected program was blocked.

If you find a quarantined file, do not automatically restore it. First, confirm the software came from a trustworthy source. If the program is legitimate, reinstalling it from the official installer is usually safer than restoring a suspicious file from quarantine.

Should You Copy DLL Files Into the Program Folder?

Some advice online suggests copying VCRUNTIME140.dll or MSVCP140.dll directly into the application’s folder. While this may work in limited cases, it is not the best first solution. The application may need additional runtime files, and the copied DLL may not match the expected version.

Use official redistributable installation first. Only consider local DLL placement if the software vendor specifically instructs you to do so, such as with certain portable applications or legacy tools.

How to Prevent These Errors in the Future

You can reduce the chance of Visual C++ runtime errors by following a few simple habits:

  • Install software from official sources whenever possible.
  • Avoid deleting shared runtime folders or manually cleaning system files.
  • Keep both x86 and x64 Visual C++ Redistributables installed on 64-bit Windows.
  • Update Windows regularly to maintain compatibility and security.
  • Use reliable uninstallers carefully and review what they remove.
  • Create restore points before major system changes.

Final Thoughts

Although VCRUNTIME140.dll and MSVCP140.dll errors look intimidating, they are usually symptoms of a missing or broken Visual C++ runtime rather than a serious PC failure. The fastest and safest repair is to install both the x86 and x64 versions of the latest Microsoft Visual C++ Redistributable, then restart your computer.

If that does not resolve the issue, repair the redistributable, reinstall the affected application, update Windows, and run system file checks. Most importantly, resist the urge to grab DLL files from random download sites. A clean, official redistributable installation is the stable foundation your Windows applications expect.