The error message "The code execution cannot proceed because msvcr120.dll was not found" is one of the most common runtime issues encountered by Windows users. It typically appears when you try to launch a video game, a graphic design tool, or a server application. This error indicates that the software requires a specific library file to communicate with the Windows operating system, but that file is either missing, corrupted, or incorrectly installed.

To resolve this issue immediately, the most effective solution is to install the Microsoft Visual C++ 2013 Redistributable package. Most users find that installing both the x86 (32-bit) and x64 (64-bit) versions of this package fixes the problem permanently. However, depending on the state of your operating system, further steps like system file repairs or application re-registrations might be necessary.

Understanding the MSVCR120.dll Component

To fix a problem effectively, it helps to understand what you are fixing. The file name msvcr120.dll is not a random string of characters; it follows a specific naming convention used by Microsoft for its development environments.

  • 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 Visual Studio 2013 to write programs in C++. To ensure these programs run on any Windows computer without requiring the full development environment, Microsoft provides "Redistributable" packages. These packages contain the essential DLL (Dynamic Link Library) files that act as a bridge between the software code and the hardware. If a program was built using the 2013 toolset, it will look specifically for the version 12.0 libraries. If they aren't there, the program simply refuses to start.

Why is msvcr120.dll Missing from Your Computer?

There are several reasons why this specific file might vanish or become inaccessible:

  1. Fresh Windows Installation: A clean install of Windows 10 or Windows 11 does not always include every legacy Visual C++ Redistributable by default. Many older programs and games still rely on the 2013 version.
  2. Accidental Deletion: Users or poorly designed uninstaller scripts might accidentally remove the DLL from the System32 or SysWOW64 folders.
  3. Antivirus Interference: Occasionally, an overzealous antivirus program might flag a DLL as a false positive and quarantine it, preventing applications from accessing it.
  4. File Corruption: Hard drive errors, sudden power outages, or system crashes can lead to "bit rot," where the data within the DLL file becomes unreadable.
  5. Architecture Mismatch: A 64-bit Windows system can run both 64-bit and 32-bit applications. If you only have the 64-bit version of the redistributable installed, but you are trying to run a 32-bit game (like many titles on Steam), you will still see the "not found" error.

Primary Solution: Installing the Microsoft Visual C++ 2013 Redistributable

This is the "gold standard" fix recommended by system administrators. Since the error is directly tied to the 2013 runtime library, reinstalling the official package from Microsoft is the safest and most reliable method.

Determining Which Version You Need

A common mistake is assuming that if you have a 64-bit PC, you only need the 64-bit (x64) installer. In the world of Windows runtimes, the architecture of the application matters as much as the architecture of the operating system. Many modern apps are still 32-bit or contain 32-bit components. Therefore, it is highly recommended to install both versions.

Steps to Perform the Installation

  1. Navigate to the official Microsoft download center or the "Latest Supported Visual C++ Redistributable" documentation page on the Microsoft Learn portal.
  2. Locate the section specifically for Visual Studio 2013 (VC++ 12.0).
  3. Download two files:
    • vcredist_x86.exe (for 32-bit support)
    • vcredist_x64.exe (for 64-bit support)
  4. Once downloaded, right-click the vcredist_x86.exe file and select Run as Administrator. Follow the prompts to complete the installation.
  5. Repeat the process for the vcredist_x64.exe file.
  6. If the installer gives you an option to Repair instead of Install, choose Repair. This will overwrite any corrupted versions of the file currently on your disk.
  7. Restart your computer. While some changes take effect immediately, a full reboot ensures that the Windows registry correctly maps the new DLL locations.

Using System File Checker to Repair Corrupted DLLs

If installing the Redistributable package didn't work, it is possible that your Windows system image itself is damaged. Windows includes built-in tools to verify the integrity of protected system files.

Running the SFC Command

The System File Checker (SFC) scans all protected system files and replaces corrupted files with a cached copy located in a compressed folder at %WinDir%\System32\dllcache.

  1. Press the Windows Key, type cmd, and select Run as Administrator.
  2. In the Command Prompt window, type the following command and press Enter: sfc /scannow
  3. The process will take several minutes. Do not close the window until the verification is 100% complete.
  4. If the scan says "Windows Resource Protection found corrupt files and successfully repaired them," try launching your application again.

Running the DISM Tool

If SFC fails to fix the issue, you should use the Deployment Image Servicing and Management (DISM) tool. DISM is more powerful because it can download fresh copies of system files from Windows Update servers if the local cache is also corrupted.

  1. In the same Administrator Command Prompt, type: DISM /Online /Cleanup-Image /RestoreHealth
  2. This tool requires an active internet connection to fetch files from Microsoft's servers.
  3. Once the process reaches 100%, run the sfc /scannow command one more time to ensure everything is synchronized.

Reinstalling the Problematic Application

Sometimes the error isn't with Windows, but with how the application was installed. Many programs come bundled with the necessary DLLs in their own installation directory. If the application's installation was interrupted, these files might be missing.

Why Reinstallation Works

When you uninstall and then reinstall a program, the installer typically performs a "dependency check." It looks for required files like msvcr120.dll and often attempts to trigger the installation of the VC++ Redistributable automatically.

For Steam users, you can use the Verify Integrity of Game Files feature. Right-click the game in your library, go to Properties > Local Files (or Installed Files), and select Verify Integrity. This will compare your local files with the official ones on the server and redownload any missing DLLs specifically for that game.

Re-registering the DLL File Manually

In rare cases, the file might exist on your computer, but Windows doesn't "know" where it is or how to use it. This happens when the file's entry in the Windows Registry is missing or pointing to the wrong location. You can manually register the DLL using the Microsoft Register Server.

  1. Open the Command Prompt as an Administrator.
  2. To unregister the file first (to clear any bad data), type: regsvr32 /u msvcr120.dll and press Enter.
  3. To register the file again, type: regsvr32 msvcr120.dll and press Enter.
  4. You should see a dialog box saying "DllRegisterServer in msvcr120.dll succeeded."

Note: If you get an error saying the module could not be found, it means the file is physically missing from the System32 folder, and you should return to the Redistributable installation step.

The Hidden Danger of Third-Party DLL Download Sites

When you search for "msvcr120.dll was not found," the first few results are often websites that allow you to download the individual DLL file. In our experience, you should avoid these sites at all costs. Here is why:

1. Security Risks

DLL files are executable code. When you download a standalone DLL from an unofficial source, you have no way of knowing if the code has been tampered with. Malicious actors often inject spyware or keyloggers into these files. Since DLLs run with the same permissions as the program using them, they can bypass many standard security checks.

2. Version Incompatibility

There are dozens of different builds of msvcr120.dll. Some are designed for specific Windows updates, while others are "Debug" versions meant for developers. Downloading a random version from the internet might cause your program to crash with a different error, such as "Entry Point Not Found" or "Instruction at Referenced Memory Could Not Be Read."

3. Dependency Chains

DLLs rarely work in isolation. msvcr120.dll often needs other files from the 2013 Redistributable package to function. By downloading only one file, you are ignoring the rest of the ecosystem it needs to run, which often leads to a "cascading error" where you fix one missing DLL only to be told another one is missing.

Copying the File from a Trusted Source

If you have another computer in your home or office that is running the same version of Windows and does not have the error, you can safely copy the file from there. This is a manual way to restore the file without using an installer.

  1. On the working PC, navigate to C:\Windows\System32.
  2. Search for msvcr120.dll.
  3. Copy it to a USB drive.
  4. On the problematic PC, paste it into C:\Windows\System32.
  5. If you are on a 64-bit system, also look for the file in C:\Windows\SysWOW64 on the working PC and copy it to the same folder on the target PC.

How to Prevent Future DLL Errors

Once you have fixed the "msvcr120.dll was not found" error, you likely want to avoid seeing it again. Preventive maintenance is key to a stable Windows environment.

  • Keep Windows Updated: Microsoft frequently pushes updates for the Visual C++ Runtimes through Windows Update. Go to Settings > Update & Security > Windows Update and ensure you are current.
  • Install All Redistributables: If you are a gamer or a power user, it is often a good idea to have a "Full Set" of runtimes. This includes the versions for 2005, 2008, 2010, 2012, 2013, and the unified 2015-2022 package. Having these pre-installed prevents almost all "DLL not found" errors before they happen.
  • Avoid Registry Cleaners: Many third-party "PC Booster" or "Registry Cleaner" tools are too aggressive. They often flag valid DLL paths as "unused" and delete them, causing the very errors they claim to prevent.
  • Run Regular Malware Scans: Use a reputable security suite to ensure that no malicious software is deleting or replacing your system libraries.

Conclusion

Fixing the "msvcr120.dll was not found" error is straightforward once you identify it as a missing component of the Microsoft Visual C++ 2013 Redistributable. By following the official installation path and avoiding the temptation of quick-fix DLL websites, you ensure your system remains secure and stable. Whether you are troubleshooting a game like Battlefield 4 or a productivity tool like OBS, the combination of official runtime installers and system file repairs (SFC/DISM) will resolve the vast majority of cases.

FAQ: Frequently Asked Questions about msvcr120.dll

What is the difference between msvcr120.dll and msvcp120.dll?

Both are part of the Visual C++ 2013 Redistributable. msvcr120.dll is the C Runtime library, while msvcp120.dll is the C++ Runtime library. If one is missing, the other often is as well. Installing the 2013 Redistributable package fixes both simultaneously.

Does Windows 11 support msvcr120.dll?

Yes, Windows 11 is fully compatible with legacy Visual C++ Redistributables. However, because it is a newer OS, it may not come with the 2013 version pre-installed. You will need to download and install it manually to run older software.

Can I just put the DLL file in the program's folder?

Yes, this is known as "local deployment." If you place msvcr120.dll in the same folder as the .exe file you are trying to run, the program will usually find it. However, this is a "band-aid" fix and won't help other programs that might need the same file. It is better to install it system-wide.

Why do I have so many versions of Microsoft Visual C++ Redistributable installed?

This is normal. Different programs are built with different versions of Visual Studio. A program built in 2010 cannot use the 2013 libraries, and vice versa. You should leave all these versions installed; they take up very little space and are essential for your software library to function.

Is msvcr120.dll a virus?

The legitimate msvcr120.dll is a safe, official Microsoft file. However, like any system file, malware can sometimes disguise itself by using the same name. If the file is located anywhere other than System32 or SysWOW64 (or an official program folder), you should scan it with an antivirus tool.

I installed the Redistributable but I still get the error. What now?

Check your "Apps & Features" list. Ensure you see both the x86 and x64 versions of the 2013 Redistributable. If you only see one, install the other. If both are present, try a "Repair" install on them, or move on to the SFC/DISM system repair steps.