- Joined
- 11 Jul 2023
- Messages
- 6
- Reaction score
- 0
- Points
- 1
A practical guide to Visual C++ 2013 runtime problems, x86/x64 compatibility and application startup errors
If an older Windows application refuses to start and shows an error such as MSVCP120.dll was not found, MSVCR120.dll is missing, or the program requires Microsoft Visual C++ 2013, the cause is often a missing Visual C++ runtime dependency.
This can happen with older applications and games developed using Microsoft Visual Studio 2013. The software itself may be installed correctly, but Windows still cannot launch it because the required runtime libraries are missing or damaged.
You do not need Visual Studio itself simply to run an application. The Redistributable package supplies the runtime environment expected by compatible software.
This is also why installing a newer Visual C++ package does not necessarily solve a dependency specifically requiring the 2013 runtime.
If you are unsure which package an application needs, first determine whether the application is 32-bit or 64-bit rather than choosing a package based only on the Windows architecture.
For a reference covering the Visual C++ 2013 download, x86/x64 packages, installation and troubleshooting, see this Visual C++ Redistributable 2013 guide.
“The program can't start because MSVCP120.dll is missing from your computer.”
MSVCP120.dll is associated with the Visual C++ 2013 runtime. If an application requires this component and the appropriate runtime is missing or damaged, Windows may prevent the program from starting.
The same general situation applies to MSVCR120.dll.
Instead of downloading individual DLL files from random sources, it is preferable to identify the required Visual C++ version and install the corresponding Redistributable package.
For example, a 32-bit application may require x86 runtime components even on a 64-bit Windows installation.
If the correct package is already installed, repairing or reinstalling it can also help when the existing runtime files have become damaged.
This is normal because different applications can be built using different Visual Studio toolsets and therefore have different runtime requirements.
For example, one application may depend on Visual C++ 2013 while another requires a newer runtime. Installing the newer package should not automatically be considered a replacement for every older dependency.
An older application can still require the Visual C++ 2013 runtime on a modern Windows installation.
If an application specifically reports a missing 120-series runtime component, check the corresponding Visual C++ 2013 installation rather than assuming that the newest Visual C++ package will solve the issue.
Install the appropriate Visual C++ 2013 Redistributable, verify whether the application requires x86 or x64, and repair the runtime if an existing installation appears damaged.
For the package details, architecture information and installation steps, this Visual C++ Redistributable 2013 download guide provides a dedicated reference.
Has anyone here had a Visual C++ 2013 dependency break after upgrading Windows or reinstalling an older game/application? What error did you get?
If an older Windows application refuses to start and shows an error such as MSVCP120.dll was not found, MSVCR120.dll is missing, or the program requires Microsoft Visual C++ 2013, the cause is often a missing Visual C++ runtime dependency.
This can happen with older applications and games developed using Microsoft Visual Studio 2013. The software itself may be installed correctly, but Windows still cannot launch it because the required runtime libraries are missing or damaged.
What is Visual C++ Redistributable 2013?
Microsoft Visual C++ Redistributable 2013 provides runtime components required by applications built with the Visual Studio 2013 C++ toolset. The 2013 generation is associated with VC++ 12.0.You do not need Visual Studio itself simply to run an application. The Redistributable package supplies the runtime environment expected by compatible software.
This is also why installing a newer Visual C++ package does not necessarily solve a dependency specifically requiring the 2013 runtime.
x86 or x64?
The architecture is important when troubleshooting these errors.- x86 = 32-bit applications
- x64 = 64-bit applications
If you are unsure which package an application needs, first determine whether the application is 32-bit or 64-bit rather than choosing a package based only on the Windows architecture.
For a reference covering the Visual C++ 2013 download, x86/x64 packages, installation and troubleshooting, see this Visual C++ Redistributable 2013 guide.
Fixing MSVCP120.dll errors
A typical message looks like:“The program can't start because MSVCP120.dll is missing from your computer.”
MSVCP120.dll is associated with the Visual C++ 2013 runtime. If an application requires this component and the appropriate runtime is missing or damaged, Windows may prevent the program from starting.
The same general situation applies to MSVCR120.dll.
Instead of downloading individual DLL files from random sources, it is preferable to identify the required Visual C++ version and install the corresponding Redistributable package.
What if the runtime is already installed?
If Visual C++ 2013 appears in the installed programs list but the application still reports a missing DLL, check the application's architecture.For example, a 32-bit application may require x86 runtime components even on a 64-bit Windows installation.
If the correct package is already installed, repairing or reinstalling it can also help when the existing runtime files have become damaged.
Can older and newer Visual C++ versions coexist?
Yes. Windows can have multiple Visual C++ Redistributable versions installed at the same time.This is normal because different applications can be built using different Visual Studio toolsets and therefore have different runtime requirements.
For example, one application may depend on Visual C++ 2013 while another requires a newer runtime. Installing the newer package should not automatically be considered a replacement for every older dependency.
Quick troubleshooting checklist
If you encounter a Visual C++ runtime error, try the following:- Read the complete error message.
- Check whether it mentions MSVCP120.dll or MSVCR120.dll.
- Identify which Visual C++ version the application requires.
- Check whether the application is x86 or x64.
- Install the matching Visual C++ 2013 Redistributable.
- If it is already installed, try repairing or reinstalling it.
- Restart the application and test again.
- Avoid replacing individual DLL files from unknown sources.
Windows 10 and Windows 11
These problems can occur on both Windows 10 and Windows 11 because the application's runtime dependency does not automatically change when the operating system is upgraded.An older application can still require the Visual C++ 2013 runtime on a modern Windows installation.
If an application specifically reports a missing 120-series runtime component, check the corresponding Visual C++ 2013 installation rather than assuming that the newest Visual C++ package will solve the issue.
Final takeaway
When an application reports MSVCP120.dll missing, MSVCR120.dll missing, or requests Visual C++ 2013, the first thing to check is its runtime dependency and architecture.Install the appropriate Visual C++ 2013 Redistributable, verify whether the application requires x86 or x64, and repair the runtime if an existing installation appears damaged.
For the package details, architecture information and installation steps, this Visual C++ Redistributable 2013 download guide provides a dedicated reference.
Has anyone here had a Visual C++ 2013 dependency break after upgrading Windows or reinstalling an older game/application? What error did you get?