The error message "The code execution cannot proceed because msvcr120.dll was not found" is a common hurdle for Windows users attempting to launch video games, professional design software, or tax applications. This specific dynamic link library (DLL) file is not a random system component; it is a critical piece of the Microsoft Visual C++ 2013 Redistributable package. When a program built using Visual Studio 2013 attempts to run, it calls upon this file to execute core C++ functions. If the file is missing, corrupted, or unregistered, the application simply fails to start.

The immediate and most effective solution to this problem is to download and install the official Microsoft Visual C++ 2013 Redistributable packages (both x86 and x64 versions) from the official Microsoft website. For most users, this single action resolves the issue permanently. However, depending on system health and file integrity, further steps like running System File Checker (SFC) or repairing the application itself might be necessary.

Understanding the Msvcr120.dll Component

To fix a system error effectively, one must understand what is being fixed. The filename msvcr120.dll follows a standard Microsoft naming convention that provides information about its origin and version:

  • MS: Stands for Microsoft.
  • V: Stands for Visual.
  • C: Refers to the C++ programming language.
  • R: Stands for Runtime.
  • 120: Refers to version 12.0 of the Visual C++ compiler, which corresponds to Visual Studio 2013.

Software developers use libraries like these so they do not have to write every piece of basic functionality from scratch. These libraries are "redistributable," meaning Microsoft allows developers to include these components with their software so the programs can run on any Windows machine. If you are running an older game or a specialized utility that has not been updated in a few years, it likely relies on this 2013 runtime environment.

Why Is Msvcr120.dll Missing from Your Computer?

There are several scenarios where a Windows 10 or Windows 11 system might lack this file, even if the computer is brand new and fully updated.

Fresh Windows Installations

Modern versions of Windows, such as Windows 11, come pre-packaged with the latest runtime libraries (like the 2015-2022 combined redistributables). However, they do not always include legacy libraries like the 2013 version by default. If you have recently performed a clean install of your operating system, you will need to manually add these older components to support older software.

Accidental Deletion or Quarantine

In some cases, users browsing their system folders might delete files they do not recognize, assuming they are "junk." More commonly, overzealous antivirus software might flag a DLL as a false positive. If the antivirus quarantines the file, the application calling for it will trigger the "not found" error.

Architecture Mismatch

This is a frequent source of confusion. A 64-bit Windows operating system can run both 64-bit and 32-bit applications. A 32-bit application requires the 32-bit version of the DLL (x86), while a 64-bit application requires the 64-bit version (x64). If you only have the x64 version of the redistributable installed but are trying to run a 32-bit game, the error will persist.

File Corruption

Sudden power outages, hard drive "bit rot," or failed system updates can corrupt the data within a DLL file. Even if the file exists in the directory, its corrupted state makes it unreadable to the operating system, resulting in a failure to load the module.

Primary Solution: Installing Microsoft Visual C++ 2013 Redistributables

This is the definitive fix recommended by technical support professionals. Because the error specifically identifies a version 12.0 file, you must install the Visual Studio 2013 runtime.

Step 1: Access the Official Microsoft Download Center

Navigate to the official Microsoft website and search for the "Visual C++ Redistributable Packages for Visual Studio 2013." Avoid third-party mirror sites, as they may bundle the installer with unwanted software or malware.

Step 2: Download Both Architectures

When prompted to choose a download, you will typically see two options:

  1. vcredist_x86.exe (This is for 32-bit support)
  2. vcredist_x64.exe (This is for 64-bit support)

Important: Even if you are running a 64-bit version of Windows, you should download and install both files. Many modern applications still use 32-bit components, and having both versions installed ensures full compatibility across all software.

Step 3: Run the Installers

Locate the downloaded files in your "Downloads" folder. Right-click the vcredist_x86.exe file and select "Run as Administrator." Follow the installation prompts, which usually involve agreeing to the licensing terms and clicking "Install." Once finished, repeat the exact same process for vcredist_x64.exe.

Step 4: Restart the System

While some system changes take effect immediately, Windows often requires a reboot to properly register new DLL locations in the Windows Registry. After restarting, attempt to launch the problematic application again.

What to Do if the Redistributable Is Already Installed

If you attempt to install the package and receive a message saying it is already present, the existing installation may be corrupted. In this scenario, you should repair the installation rather than trying to install it again.

Repairing Visual C++ 2013

  1. Open the Control Panel and navigate to Programs and Features.
  2. In the list of installed programs, scroll down until you find Microsoft Visual C++ 2013 Redistributable. You will likely see two entries (x86 and x64).
  3. Select the x86 version and click the Change button at the top (do not click Uninstall).
  4. In the window that appears, click Repair.
  5. Wait for the process to complete, then repeat these steps for the x64 version.
  6. Restart your computer.

Using System File Checker (SFC) to Fix DLL Issues

If the redistributable installation does not solve the problem, the issue might lie deeper within the Windows system files. Windows includes a built-in utility called the System File Checker (SFC) that scans all protected system files and replaces corrupted versions with a healthy cached copy.

How to Run the SFC Scan

  1. Press the Windows Key and type cmd.
  2. Right-click Command Prompt and select Run as Administrator. This is crucial; the tool will not work without elevated privileges.
  3. In the black console window, type the following command and press Enter: sfc /scannow
  4. The system will begin a multi-stage scan. This process can take anywhere from 5 to 20 minutes depending on your hardware. Do not close the window until you see a message stating the verification is 100% complete.
  5. If the scan reports that "Windows Resource Protection found corrupt files and successfully repaired them," restart your PC and test your application.

Running the DISM Tool for Advanced Repair

If the SFC scan is unable to fix the files (sometimes it reports "Windows Resource Protection found corrupt files but was unable to fix some of them"), you should use the Deployment Image Servicing and Management (DISM) tool. DISM uses Windows Update to provide the files required to fix corruptions in the local system image.

How to Run DISM

  1. Open the Command Prompt as an Administrator.
  2. Type the following command and press Enter: dism /online /cleanup-image /restorehealth
  3. This tool requires an active internet connection. It will compare your local files with the official Windows image on Microsoft's servers and download any missing or damaged components.
  4. Once the DISM process reaches 100%, it is a best practice to run the sfc /scannow command one more time to ensure all repairs are synchronized.

Re-registering the msvcr120.dll File Manually

In rare instances, the msvcr120.dll file might be physically present on your hard drive, but the Windows Registry doesn't "know" it's there. This is essentially a communication breakdown between the file system and the operating system. You can force Windows to re-register the file using the Command Prompt.

Steps to Register the DLL

  1. Open the Command Prompt as an Administrator.
  2. To ensure you are working with a clean slate, first unregister the file by typing: regsvr32 /u msvcr120.dll Press Enter. A dialog box should confirm the unregistration.
  3. Now, register the file again by typing: regsvr32 msvcr120.dll Press Enter.
  4. If you receive an error saying the "module could not be found," it means the file is missing from the System32 or SysWOW64 folders, and you must return to the step of installing the Redistributable package.

Reinstalling the Affected Application

If you have repaired the Windows runtimes and the system files, but the error persists for only one specific program, the application's own installation might be the culprit.

Why Application Reinstallation Works

When you uninstall and reinstall a program, the installer performs a "dependency check." Most modern installers are designed to detect if the required C++ runtimes are present. If they are missing, the installer will often attempt to trigger the Microsoft Redistributable installation automatically.

Furthermore, some applications place a local copy of msvcr120.dll directly in their own installation folder (e.g., C:\Program Files (x86)\AppFolder). If this local copy is deleted or corrupted, the program will crash even if the system-wide DLL is healthy. Reinstalling the app restores these local dependencies.

For Steam and Gaming Platforms

If you are seeing this error while trying to launch a game on Steam, Epic Games, or EA App, you don't necessarily need to reinstall the entire game.

  1. Open your Steam Library.
  2. Right-click the game and select Properties.
  3. Go to the Installed Files tab and click Verify integrity of game files.
  4. The platform will scan the game folder and automatically redownload any missing or corrupted DLL files specifically required for that game.

Safety Warning: Why You Should Never Use "DLL Fixer" Websites

When you search for "msvcr120.dll not found," the first page of search results is often cluttered with websites offering a direct download of the single DLL file. It is extremely tempting to just download the one missing file and drop it into a folder, but this is a dangerous practice for several reasons:

1. Malware Risk

DLL files are executable code. When you download a DLL from an unofficial source, you are essentially running code from a stranger on your computer. Many of these "fixer" sites bundle malware, keyloggers, or spyware into the DLL files. By the time you realize something is wrong, your personal data could already be compromised.

2. Version and Architecture Mismatches

Even if the file is clean, there are dozens of different builds of msvcr120.dll. If you download a version meant for an older update of Visual Studio, or a version for the wrong processor architecture, the error will simply change to a "0xc000007b" error (Invalid Image Format), which is even harder to troubleshoot.

3. Missing Dependencies

A DLL file rarely works in isolation. It often depends on other "helper" files within the same runtime package. Downloading the single DLL doesn't solve the underlying lack of the full Redistributable environment, which means the program will likely fail on the next file it tries to call.

4. Security Vulnerabilities

Official Microsoft Redistributables receive security patches through Windows Update. If you manually place an old version of a DLL into your system folder, it will never be updated, leaving your computer vulnerable to exploits that were patched years ago.

Always stick to official Microsoft installers to ensure safety and system stability.

Troubleshooting "Error 0xc000007b" After Fixes

Sometimes, after a user manually tries to fix the msvcr120.dll error by copying files into System32, they encounter "The application was unable to start correctly (0xc000007b)." This almost always indicates that a 32-bit DLL has been placed into a 64-bit system folder, or vice versa.

To fix this:

  1. Navigate to C:\Windows\System32 and C:\Windows\SysWOW64.
  2. If you manually pasted msvcr120.dll into these folders, delete them.
  3. Run the Repair function in the Programs and Features menu for the Visual C++ 2013 Redistributables as described earlier. This will place the correct files in the correct directories.

Summary of the Recommended Fix Order

If you are currently staring at the error message, follow this sequence for the highest success rate:

  1. Download and Install both the x86 and x64 versions of the Microsoft Visual C++ 2013 Redistributable.
  2. Restart your computer.
  3. If the error persists, Repair both versions of the 2013 Redistributable via the Control Panel.
  4. Run SFC /scannow in an Administrator Command Prompt to fix system-level corruption.
  5. Reinstall the specific application or game that is failing to launch.

Frequently Asked Questions (FAQ)

Is msvcr120.dll a virus?

No, msvcr120.dll is a legitimate Microsoft file. However, like any system file, a virus can infect or mimic it. If you find this file in a folder other than System32, SysWOW64, or a legitimate program's directory, you should run a full system scan with Windows Defender.

Can I just copy msvcr120.dll from another computer?

It is not recommended. While it might work if the other computer has the exact same Windows version and architecture, it often leads to registry mismatches and "0xc000007b" errors. Using the official installer is faster and safer.

Why do I need the 2013 version if I already have the 2022 version?

Visual C++ versions are not backward compatible in the way you might expect. A program written for the 2013 runtime cannot use the 2022 library. You can—and often must—have multiple versions of the Visual C++ Redistributable (2010, 2012, 2013, 2015-2022) installed simultaneously to support all your different apps.

I installed the 2013 Redistributable, but the error still says msvcp120.dll (with a 'p') is missing. Is that the same thing?

They are closely related. msvcr120.dll is the C Runtime, while msvcp120.dll is the C++ Standard Library. Both are included in the same Visual C++ 2013 Redistributable package. If one is missing, the other often is too. Installing the package fixes both.

Does this error apply to Windows 7 or 8?

Yes, the fix is identical. The Visual C++ 2013 Redistributable is compatible with Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows 10, and Windows 11.

Conclusion

Encountering the "msvcr120.dll was not found" error can be a major disruption, but it is one of the most straightforward Windows issues to resolve. By understanding that this file is simply a component of the 2013 C++ runtime environment, you can avoid the "wild goose chase" of searching for individual files on sketchy websites.

In almost every scenario, installing or repairing the official Microsoft Visual C++ 2013 Redistributable (x86 and x64) will restore the missing link between your operating system and your software. By following the structured troubleshooting steps—starting with the official installer and moving to system repairs like SFC and DISM—you ensure that your Windows environment remains stable, secure, and ready to run your favorite applications.