Visual C++ Redistributable 2013 what it is, which version to install, and how to fix common errors
If you are trying to run an older Windows application and receive an error mentioning Visual C++ 2013, MSVCP120.dll, or MSVCR120.dll, the problem is often related to a missing or damaged Microsoft Visual C++ runtime.
This is especially common with older desktop applications, games, utilities and other software originally developed with Microsoft Visual Studio 2013. The application itself may be installed correctly, but Windows can still prevent it from starting if the required runtime components are not available.
What is Visual C++ Redistributable 2013?
Microsoft Visual C++ Redistributable 2013 is a runtime package designed for applications built with the Visual Studio 2013 C++ toolset.
In simple terms, developers can use libraries provided by Visual C++ when creating their applications. End users normally do not need Visual Studio itself just to run those applications. Instead, the required runtime components can be installed through the corresponding Visual C++ Redistributable package.
The Visual C++ 2013 generation corresponds to the VC++ 12.0 toolset.
This is why an older application can specifically ask for the 2013 runtime even when a newer Visual C++ Redistributable is already installed on the computer.
Visual C++ 2013 x86 vs x64
One of the most common points of confusion is choosing between x86 and x64.
The basic difference is:
For example, an older 32-bit application running on 64-bit Windows may still depend on the x86 version of Visual C++ Redistributable 2013.
The correct choice should therefore be based on the architecture required by the application.
For anyone who needs the package, this Visual C++ Redistributable 2013 download and installation guide contains information about the available packages, x86/x64 architecture, installation and common runtime problems.
Why does an application say MSVCP120.dll is missing?
The MSVCP120.dll error is one of the common messages associated with applications that depend on the Visual C++ 2013 runtime.
You may see messages similar to:
A better first step is to determine which Visual C++ runtime the application requires and install the corresponding Redistributable package.
The same principle applies to MSVCR120.dll errors.
What is MSVCR120.dll?
MSVCR120.dll is another runtime component associated with Visual C++ 2013 applications.
If an application reports that MSVCR120.dll is missing, the installed Visual C++ runtime may be absent, damaged, or incompatible with what the application expects.
Before replacing individual DLL files manually, check the Visual C++ Redistributable installation.
This approach is generally easier to maintain because the runtime package installs the related components together rather than relying on an isolated file obtained from an unknown source.
Does Visual C++ 2013 work with Windows 10?
Older applications do not automatically stop depending on their original runtime simply because the operating system has been upgraded.
A program developed years ago can still require Visual C++ 2013 when running on a modern Windows system.
If you are running Windows 10 and an application specifically reports a missing Visual C++ 2013 component, check whether the appropriate Redistributable package is installed and whether its architecture matches the application.
What about Windows 11?
The same situation can occur on Windows 11.
Windows 11 may run applications that were originally developed for previous Windows versions, but those applications can still have their own runtime dependencies.
Therefore, if an older program requests Visual C++ 2013, installing the required runtime can be necessary even on a completely up-to-date Windows 11 installation.
Can different Visual C++ Redistributable versions be installed together?
Yes, Windows systems can have multiple Visual C++ Redistributable generations installed.
This is important because different applications can depend on different Visual C++ runtime versions.
For example, one application may require Visual C++ 2013 while another application was built using a newer Visual Studio toolset.
Installing a newer runtime should not be treated as a universal replacement for every older Visual C++ dependency.
If a program specifically requires the 2013 runtime, check that the corresponding package is actually installed.
What if Visual C++ 2013 will not install?
If the installer fails, there are several things worth checking.
First, verify that you downloaded the correct architecture for the application.
Next, check whether Visual C++ 2013 is already installed in Windows. If an existing installation is damaged, the available repair option may help.
You can also try reinstalling the appropriate package if the current installation is incomplete or corrupted.
If the installer itself produces an error, the problem may be unrelated to the application that originally requested the runtime. In that situation, Windows system components, permissions, existing runtime installations or the installer package itself may need to be checked.
Should you download MSVCP120.dll separately?
This is probably one of the most important points when troubleshooting these errors.
If a program reports that MSVCP120.dll or MSVCR120.dll is missing, downloading a random DLL from a third-party DLL website is not the first solution I would recommend.
Those files are components of the corresponding Microsoft Visual C++ runtime environment.
It is better to identify the required Visual C++ version and install the appropriate Redistributable package. This also reduces the chance of ending up with an incorrect DLL version or an incomplete set of runtime files.
A simple troubleshooting checklist
If an older application refuses to start, I would check the following in order:
1. Check the exact error message.
Look for references to Visual C++, MSVCP120.dll, MSVCR120.dll or another runtime component.
2. Identify the required Visual C++ version.
Do not assume that the newest Redistributable is automatically the correct one.
3. Check application architecture.
Determine whether the application is 32-bit or 64-bit.
4. Install the appropriate Visual C++ 2013 package.
Use the package corresponding to the application's runtime requirement.
5. Repair or reinstall if necessary.
If the runtime is already present but appears damaged, repair or reinstall it.
6. Test the application again.
After the installation completes, launch the application again and check whether the original error has disappeared.
Final thoughts
Visual C++ Redistributable 2013 is still relevant when dealing with software developed around the Visual Studio 2013 generation. The fact that it is an older runtime does not mean that every application using it can simply switch to a newer package.
The most common problems are relatively straightforward once the dependency is identified: selecting the correct x86 or x64 package, installing the required runtime, and avoiding unnecessary manual replacement of individual DLL files.
If anyone is troubleshooting an older Windows application, this Visual C++ Redistributable 2013 also covers the download, architecture differences, installation process and common MSVCP120.dll / MSVCR120.dll issues in one place.
Has anyone here encountered a particularly stubborn Visual C++ 2013 installation or MSVCP120.dll/MSVCR120.dll error? It would be interesting to compare which applications still depend on the 2013 runtime.
If you are trying to run an older Windows application and receive an error mentioning Visual C++ 2013, MSVCP120.dll, or MSVCR120.dll, the problem is often related to a missing or damaged Microsoft Visual C++ runtime.
This is especially common with older desktop applications, games, utilities and other software originally developed with Microsoft Visual Studio 2013. The application itself may be installed correctly, but Windows can still prevent it from starting if the required runtime components are not available.
What is Visual C++ Redistributable 2013?
Microsoft Visual C++ Redistributable 2013 is a runtime package designed for applications built with the Visual Studio 2013 C++ toolset.
In simple terms, developers can use libraries provided by Visual C++ when creating their applications. End users normally do not need Visual Studio itself just to run those applications. Instead, the required runtime components can be installed through the corresponding Visual C++ Redistributable package.
The Visual C++ 2013 generation corresponds to the VC++ 12.0 toolset.
This is why an older application can specifically ask for the 2013 runtime even when a newer Visual C++ Redistributable is already installed on the computer.
Visual C++ 2013 x86 vs x64
One of the most common points of confusion is choosing between x86 and x64.
The basic difference is:
- x86 — 32-bit applications
- x64 — 64-bit applications
For example, an older 32-bit application running on 64-bit Windows may still depend on the x86 version of Visual C++ Redistributable 2013.
The correct choice should therefore be based on the architecture required by the application.
For anyone who needs the package, this Visual C++ Redistributable 2013 download and installation guide contains information about the available packages, x86/x64 architecture, installation and common runtime problems.
Why does an application say MSVCP120.dll is missing?
The MSVCP120.dll error is one of the common messages associated with applications that depend on the Visual C++ 2013 runtime.
You may see messages similar to:
This does not necessarily mean that you should search for an individual DLL file and manually copy it into the Windows system directory.
A better first step is to determine which Visual C++ runtime the application requires and install the corresponding Redistributable package.
The same principle applies to MSVCR120.dll errors.
What is MSVCR120.dll?
MSVCR120.dll is another runtime component associated with Visual C++ 2013 applications.
If an application reports that MSVCR120.dll is missing, the installed Visual C++ runtime may be absent, damaged, or incompatible with what the application expects.
Before replacing individual DLL files manually, check the Visual C++ Redistributable installation.
This approach is generally easier to maintain because the runtime package installs the related components together rather than relying on an isolated file obtained from an unknown source.
Does Visual C++ 2013 work with Windows 10?
Older applications do not automatically stop depending on their original runtime simply because the operating system has been upgraded.
A program developed years ago can still require Visual C++ 2013 when running on a modern Windows system.
If you are running Windows 10 and an application specifically reports a missing Visual C++ 2013 component, check whether the appropriate Redistributable package is installed and whether its architecture matches the application.
What about Windows 11?
The same situation can occur on Windows 11.
Windows 11 may run applications that were originally developed for previous Windows versions, but those applications can still have their own runtime dependencies.
Therefore, if an older program requests Visual C++ 2013, installing the required runtime can be necessary even on a completely up-to-date Windows 11 installation.
Can different Visual C++ Redistributable versions be installed together?
Yes, Windows systems can have multiple Visual C++ Redistributable generations installed.
This is important because different applications can depend on different Visual C++ runtime versions.
For example, one application may require Visual C++ 2013 while another application was built using a newer Visual Studio toolset.
Installing a newer runtime should not be treated as a universal replacement for every older Visual C++ dependency.
If a program specifically requires the 2013 runtime, check that the corresponding package is actually installed.
What if Visual C++ 2013 will not install?
If the installer fails, there are several things worth checking.
First, verify that you downloaded the correct architecture for the application.
Next, check whether Visual C++ 2013 is already installed in Windows. If an existing installation is damaged, the available repair option may help.
You can also try reinstalling the appropriate package if the current installation is incomplete or corrupted.
If the installer itself produces an error, the problem may be unrelated to the application that originally requested the runtime. In that situation, Windows system components, permissions, existing runtime installations or the installer package itself may need to be checked.
Should you download MSVCP120.dll separately?
This is probably one of the most important points when troubleshooting these errors.
If a program reports that MSVCP120.dll or MSVCR120.dll is missing, downloading a random DLL from a third-party DLL website is not the first solution I would recommend.
Those files are components of the corresponding Microsoft Visual C++ runtime environment.
It is better to identify the required Visual C++ version and install the appropriate Redistributable package. This also reduces the chance of ending up with an incorrect DLL version or an incomplete set of runtime files.
A simple troubleshooting checklist
If an older application refuses to start, I would check the following in order:
1. Check the exact error message.
Look for references to Visual C++, MSVCP120.dll, MSVCR120.dll or another runtime component.
2. Identify the required Visual C++ version.
Do not assume that the newest Redistributable is automatically the correct one.
3. Check application architecture.
Determine whether the application is 32-bit or 64-bit.
4. Install the appropriate Visual C++ 2013 package.
Use the package corresponding to the application's runtime requirement.
5. Repair or reinstall if necessary.
If the runtime is already present but appears damaged, repair or reinstall it.
6. Test the application again.
After the installation completes, launch the application again and check whether the original error has disappeared.
Final thoughts
Visual C++ Redistributable 2013 is still relevant when dealing with software developed around the Visual Studio 2013 generation. The fact that it is an older runtime does not mean that every application using it can simply switch to a newer package.
The most common problems are relatively straightforward once the dependency is identified: selecting the correct x86 or x64 package, installing the required runtime, and avoiding unnecessary manual replacement of individual DLL files.
If anyone is troubleshooting an older Windows application, this Visual C++ Redistributable 2013 also covers the download, architecture differences, installation process and common MSVCP120.dll / MSVCR120.dll issues in one place.
Has anyone here encountered a particularly stubborn Visual C++ 2013 installation or MSVCP120.dll/MSVCR120.dll error? It would be interesting to compare which applications still depend on the 2013 runtime.
