msvcr120d.dll Not Found: The Safe Fixes for Windows 11 and 10

msvcr120d.dll is the Debug version of Microsoft’s Visual C++ 2013 C runtime. If Windows says this file is missing, the most likely explanation is that a program, game, plugin, or developer build was packaged incorrectly as a Debug build.

The normal Visual C++ 2013 Redistributable does not install msvcr120d.dll. It installs the release runtime named msvcr120.dll, without the final d. That difference determines which repair will work.

As an Amazon Associate I earn from qualifying purchases.

File or package	What it means	Normal end-user action
msvcr120d.dll	Visual C++ 2013 Debug C runtime	Obtain a corrected Release build from the software publisher
msvcr120.dll	Visual C++ 2013 Release C runtime	Install or repair the matching VC++ 2013 Redistributable
vcredist_x86.exe	32-bit Visual C++ 2013 release runtime	Required by 32-bit programs
vcredist_x64.exe	64-bit Visual C++ 2013 release runtime	Required by 64-bit programs
msvcp120d.dll or vcomp120d.dll	Other Visual C++ 2013 Debug dependencies	Usually confirms that a Debug build was distributed

Microsoft identifies msvcr120d.dll as the non-redistributable Debug counterpart to msvcr120.dll. It is part of Visual Studio 2013 development files, not a protected Windows system component. Microsoft’s C runtime guidance

What the final d means

The final d in msvcr120d.dll means Debug.

A developer normally creates two kinds of Windows application builds:

• A Debug build contains extra information and development checks.
• A Release build is prepared for ordinary distribution.

Visual Studio 2013 uses the v120 toolset. Its Debug CRT files include names such as:

msvcr120d.dll
msvcp120d.dll
vcomp120d.dll

The corresponding release files omit the d:

msvcr120.dll
msvcp120.dll
vcomp120.dll

Microsoft lists the Debug CRT under Visual Studio paths such as Debug_NonRedist, including separate x86, x64, and ARM locations. The name “NonRedist” is important: Microsoft does not license these Debug files for ordinary application redistribution. Visual Studio 2013 redistribution file list

That is why the usual fix is not to find a copy of the DLL. The software publisher needs to rebuild the application and distribute a Release version.

First, confirm which file Windows is requesting

Read the complete error message carefully. The following messages point to different situations:

• “The code execution cannot proceed because MSVCR120D.dll was not found.”
• “The program can’t start because MSVCR120D.dll is missing from your computer.”
• “The specified module could not be found.”
• “The procedure entry point could not be located.”
• “The program was not designed to run on Windows or it contains an error.”
• A message mentioning “bad image” or an error such as 0xc000007b.

Check whether the name is exactly:

msvcr120d.dll

Do not confuse it with:

msvcr120.dll

The first file is the Debug runtime. The second is the release runtime supplied by the Visual C++ 2013 Redistributable.

If the message names msvcr120.dll without the d, follow the redistributable instructions below. If it names msvcr120d.dll, continue with the publisher and Debug-build fixes first.

Fix 1: Install a corrected version of the program

For most people, this is the correct solution.

A released application, game, mod, or plugin should normally use the Release CRT. If it requests msvcr120d.dll, the publisher may have accidentally shipped a Debug executable or a native DLL compiled for internal testing.

Repair the program from Windows

1. Press Windows + I to open Settings.
2. Select Apps.
3. Select Installed apps in Windows 11, or Apps & features in Windows 10.
4. Find the affected program.
5. Select the three-dot menu beside it.
6. Choose Advanced options if available.
7. Select Repair.
8. Start the program again.

If there is no Repair button, uninstall and reinstall the program using the publisher’s official installer. Save your settings or game saves first if the program does not synchronize them.

A repair will help when an installed file is incomplete or corrupted. It will not help if the publisher’s installer consistently ships a Debug build. If the same msvcr120d.dll message returns immediately after reinstalling, contact the publisher and explain that the distributed program depends on the non-redistributable Visual C++ 2013 Debug CRT.

Verify game files through the launcher

If the error belongs to a game:

1. Open the game launcher.
2. Open the game’s properties or management menu.
3. Look for Verify, Verify integrity, Repair, or a similar command.
4. Let the launcher replace missing or damaged files.
5. Restart Windows if the launcher reports that files were repaired.
6. Start the game again.

This is especially useful when the game worked before an update, when an installation was interrupted, or when only a mod or plugin now fails.

If verification restores the same Debug-dependent files and the error continues, the issue belongs with the game or plugin publisher. A launcher cannot convert a Debug build into a Release build.

When this fix is definitive

This is the most likely final answer when:

• The affected software came from a small developer or mod author.
• The program is a beta, test utility, plugin, or custom build.
• The error also mentions msvcp120d.dll or another filename ending in d.dll.
• The program fails on more than one computer.
• Reinstalling the same installer produces exactly the same error.

Several missing Debug DLLs are particularly strong evidence that the package itself was built incorrectly.

Fix 2: Install Visual C++ 2013 Redistributable only when the error is for msvcr120.dll

The Visual C++ 2013 Redistributable is appropriate for the release runtime, not for msvcr120d.dll.

Microsoft lists the Visual C++ 2013 packages as:

• vcredist_x86.exe for 32-bit applications
• vcredist_x64.exe for 64-bit applications

The packages are available from Microsoft’s Visual C++ Redistributable downloads page. Microsoft lists the current Visual C++ 2013 packages as version 12.0.40664.0.

Use these official package links when the error names msvcr120.dll without the final d:

• Visual C++ 2013 x86 Redistributable
• Visual C++ 2013 x64 Redistributable

Choose x86 or x64 correctly

The required architecture is determined by the application, not only by the version of Windows.

• A 32-bit program needs the x86 runtime.
• A 64-bit program needs the x64 runtime.
• A 64-bit Windows computer can run both 32-bit and 64-bit programs.

Many gaming PCs need both packages because they run a mixture of 32-bit launchers, older games, utilities, and 64-bit software.

To identify the program architecture, check the publisher’s system requirements or documentation. A Task Manager entry marked “32-bit” or “32-bit (x86)” is a useful indication that the application needs x86. If the publisher provides separate x86 and x64 downloads, use the version matching the program.

On 64-bit Windows, Windows normally uses SysWOW64 for 32-bit system components and System32 for native 64-bit system components. Do not use those folder names as a reason to copy DLLs manually. Microsoft’s WOW64 file-system redirector documentation

Install the release runtime

1. Download the x86 or x64 package from Microsoft.
2. Close the affected program.
3. Right-click the downloaded installer.
4. Select Run as administrator.
5. Accept the license terms.
6. Select Install.
7. Restart Windows.
8. Start the program again.

If Microsoft reports that the package is already installed:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Find Microsoft Visual C++ 2013 Redistributable.
5. Select the matching x86 or x64 entry.
6. Select Change.
7. Choose Repair.
8. Restart Windows.

Microsoft also documents command-line repair:

vcredist_x86.exe /repair /norestart

or:

vcredist_x64.exe /repair /norestart

Run the command from the folder containing the downloaded installer, using the package that matches the application.

What success looks like

Installing or repairing the release package should resolve an error that names:

msvcr120.dll

It should not be expected to resolve an error that names:

msvcr120d.dll

Installing a newer Visual C++ runtime, such as the 2015–2022 family, also does not replace the older v120 runtime. Visual C++ versions are installed side by side. Microsoft’s supported Visual C++ downloads

Fix 3: Check Windows Security quarantine

Windows Defender or another antivirus program may have quarantined a file belonging to the application. This is more plausible when the error started immediately after an antivirus detection, application update, or fresh installation.

To inspect Microsoft Defender’s history:

1. Open the Start menu.
2. Search for Windows Security.
3. Open Virus & threat protection.
4. Select Protection history.
5. Review recent detections.
6. Expand a detection associated with the affected program.
7. Check the file path and detection details.

Restore a quarantined file only when all of the following are true:

• The file came from a trusted, verifiable application installation.
• The application was downloaded from its legitimate publisher.
• The detection is confirmed as a false positive.
• The publisher has specifically advised restoring the file.

Do not restore or approve a DLL downloaded from an unknown source. Microsoft explains how to review and manage detections in Protection history.

If the antivirus repeatedly quarantines the same file, contact the software publisher before adding an exclusion. A Debug DLL in a consumer application may indicate a packaging problem rather than a false positive.

Fix 4: Check whether a plugin or secondary DLL is responsible

The main program may be correctly built while an add-on is not.

This commonly happens with:

• Game mods
• Audio or video plugins
• Graphics overlays
• Hardware control utilities
• Office or browser extensions with native components
• Custom codecs
• Python, MATLAB, or other development integrations
• DLL files placed in a program’s plugin directory

To test this safely:

1. Close the affected program.
2. Open its installation folder.
3. Identify recently added plugins, mods, or native DLL files.
4. Temporarily disable the add-on using the program’s own settings.
5. If necessary, move the suspected plugin to a separate backup folder outside the application directory.
6. Start the main program again.

Do not delete the plugin immediately. Moving it preserves a way to restore it, although the program should be closed before changing files in its installation directory.

If the main application starts after the plugin is disabled, contact the plugin author. Provide the exact msvcr120d.dll message and the plugin version. The main developer may not be able to correct a third-party Debug dependency.

Fix 5: Ask the publisher for a Release build

When an ordinary application requests msvcr120d.dll, the publisher needs to provide a corrected build.

Use a support form, issue tracker, or official contact method and include:

• The full error message
• The application or game name
• The application version
• The plugin or mod name and version, if relevant
• Whether Windows 10 or Windows 11 is installed
• Whether Windows is 32-bit or 64-bit
• Whether the application itself is x86 or x64, if known
• Whether the issue began after an update, reinstall, file move, or antivirus quarantine
• Whether the same error occurs on another computer
• Any additional missing files, such as msvcp120d.dll

A useful report can say:

The application fails because it requests msvcr120d.dll, the Visual C++ 2013 Debug CRT. Please provide a Release build using the appropriate release runtime, or confirm the controlled test-machine requirements.

Do not ask the publisher to upload a single DLL without the surrounding application. The executable and all native dependencies must be built and packaged consistently.

Fix 6: Developer solution — rebuild in Release mode

If you own the source code, do not deploy the Debug output to end users.

Select the Release configuration

1. Open the solution in Visual Studio.
2. Select the configuration dropdown on the main toolbar.
3. Choose Release.
4. Select the intended platform, such as Win32 or x64.
5. If the configuration is missing, open Build.
6. Select Configuration Manager.
7. Add or select the Release configuration for every relevant project.

Select the release runtime library

1. Right-click the project in Solution Explorer.
2. Select Properties.
3. At the top, set Configuration to Release.
4. Set Platform to the intended architecture.
5. Open Configuration Properties.
6. Select C/C++.
7. Select Code Generation.
8. Find Runtime Library.
9. Select Multi-threaded DLL (/MD).
10. Select Apply.
11. Select OK.

The /MDd option selects the Debug CRT and can cause a dependency on msvcr120d.dll. The /MD option selects the release DLL runtime. Microsoft documents these choices in its runtime-library compiler options.

Rebuild the executable and every native library it loads. A Release executable can still depend on a Debug plugin or library, so changing only the main project may not be enough.

Rebuild all native dependencies

Check third-party libraries, plugins, and project references for Debug output. Look for:

msvcr120d.dll
msvcp120d.dll
vcomp120d.dll

Replace Debug library references with compatible Release versions. Ensure that all modules use compatible runtime settings and the same intended architecture.

Microsoft’s Release and Debug configuration guidance explains how to select and manage these configurations.

When a Debug build really is intentional

A developer may need to run a Debug executable on a controlled test machine. Microsoft documents deployment of Debug executables for testing, but that is different from distributing a consumer application. Debug executable deployment guidance explains the controlled testing scenario.

For normal users, provide a Release build. Visual Studio 2013 itself is an older, out-of-support development platform, so plan future maintenance around a supported toolchain where practical. Microsoft Visual Studio 2013 lifecycle information

Fix 7: Inspect which module actually requests the DLL

Sometimes the error appears when launching one program, but a secondary DLL is the real requester.

Developers with Visual Studio build tools can inspect an executable with:

dumpbin /DEPENDENTS program.exe

Replace program.exe with the actual executable name. The same inspection can be performed on a plugin or native DLL suspected of causing the failure.

Microsoft documents the /DEPENDENTS option in DUMPBIN’s dependency reference.

This inspection can reveal:

• A Debug runtime dependency hidden in a plugin
• A 32-bit module loaded by a 64-bit process
• A missing dependency of another dependency
• A release executable that loads a Debug library at startup

If the DLL exists but Windows still reports that the module could not be found, the named file may not be the only missing dependency. A loader error can also result from an incompatible architecture, a damaged binary, or another DLL required by the first one.

Fix 8: Repair Windows components only when broader corruption exists

msvcr120d.dll is not a protected Windows system file, so System File Checker is not the primary repair for this specific error.

Use DISM and SFC when there are additional signs of Windows component corruption, such as multiple built-in Windows features failing, damaged system files, unexplained servicing errors, or other Windows components reporting corruption.

Microsoft recommends running DISM before SFC.

Run DISM

1. Open the Start menu.
2. Search for Terminal or Command Prompt.
3. Right-click it.
4. Select Run as administrator.
5. Enter:

DISM /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to finish.
3. Restart Windows.

Run System File Checker

Open an elevated Terminal or Command Prompt again and enter:

sfc /scannow

Press Enter and wait until the scan completes. Restart Windows afterward, then test the affected program.

SFC repairs protected Windows system files. It does not normally supply Visual Studio Debug libraries. Microsoft’s instructions are available in Use the System File Checker tool.

If you repeatedly run SFC and DISM without identifying any change, stop treating them as the main solution. The application may simply need a corrected Release build.

When manually running DISM and SFC becomes repetitive and you cannot tell which Windows component is damaged, Outbyte PC Repair can scan for the problems and show what needs attention; its repair functions require the full version, and it is not required for an application that specifically needs a publisher-provided Release build.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 9: Update drivers only when the symptoms point to a driver problem

Generic driver updates are not a normal fix for msvcr120d.dll. Updating a graphics, chipset, audio, or storage driver will not convert a Debug application into a Release build.

Driver troubleshooting becomes relevant when the error appeared together with:

• Device Manager warning icons
• Repeated graphics or audio crashes
• A new device installation
• A failed Windows upgrade
• Blue screens or hardware initialization failures
• A device-specific utility that now refuses to start

Check Device Manager

1. Right-click the Start button.
2. Select Device Manager.
3. Expand categories such as Display adapters, Sound, video and game controllers, Network adapters, and Universal Serial Bus controllers.
4. Look for a yellow warning symbol.
5. Right-click the affected device.
6. Select Properties.
7. Read the Device status message.
8. Open the Driver tab.
9. Use Update Driver only when a trusted driver source is available.
10. Restart Windows and test the program.

Prefer the computer manufacturer, motherboard manufacturer, or device manufacturer for driver packages. Do not use a driver update as a substitute for repairing an application that requests msvcr120d.dll.

When hunting through Device Manager and manufacturer pages leaves you guessing which of many installed drivers is stale, Outbyte Driver Updater can scan and identify driver issues; installing updates through its full version is optional, and driver repair will not fix a program whose publisher shipped a Debug dependency.

Fix 10: Check Windows Features only for feature-related symptoms

There is no Windows Feature that installs msvcr120d.dll.

You can still check optional features when the program also reports a separate missing Windows component:

1. Press Windows + R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the Windows Features list.
3. Enable only a feature required by the application’s documentation.
4. Select OK.
5. Restart Windows if prompted.

Do not enable random features in an attempt to obtain the Visual C++ 2013 Debug CRT. DirectX, .NET Framework, legacy components, and Windows Features are separate dependencies.

Fix 11: Consider System Restore after a recent system change

System Restore is appropriate only when the problem clearly began after a recent driver installation, system change, or update and the application previously worked.

1. Press Windows + R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select Choose a different restore point if that option appears.
3. Select a restore point from before the problem began.
4. Review the affected programs and drivers.
5. Start the restore process.
6. Let Windows restart.

System Restore does not replace an incorrectly packaged application. It is a fallback for a wider system change that may have damaged several programs. Microsoft documents the process in System Restore.

What “bad image” and “entry point not found” mean

Not every error involving this filename means that a file is simply absent.

“Specified module could not be found”

This usually indicates that Windows could not load the requested module or one of its dependencies. The named DLL may be absent, or another DLL it needs may be missing.

“Entry point not found”

This usually indicates a version or application binary interface mismatch. A DLL may be present but not contain the function the program expects. Installing a random replacement can make this worse.

“Bad image” or “not designed to run on Windows”

This can indicate:

• A corrupted file
• The wrong architecture
• An incompatible binary
• A damaged dependency
• A file that is not a valid Windows DLL

Treat this as a binary or dependency problem rather than assuming that installing another redistributable will solve it.

What not to do

Do not download the DLL from a random website

Unverified DLL download pages can provide:

• Malware
• A modified file
• The wrong architecture
• An incompatible Visual C++ build
• A file with a different update level
• A DLL that hides the real application packaging problem

There is no official standalone Microsoft download of msvcr120d.dll for general end-user redistribution. Use the application publisher’s corrected installer, or install Visual Studio development components on a controlled development machine when you own the source code.

Do not copy a random file into System32 or SysWOW64

Copying a DLL into a Windows directory can create:

• Architecture mismatches
• DLL search-order problems
• Conflicts with other software
• Security risks
• A failure that is harder to diagnose

Microsoft documents how DLL search order affects which file Windows loads in Dynamic-link library search order.

Do not copy the file into the application folder as a permanent repair

Application-local DLL deployment can be legitimate when controlled by the application developer, but copying an unknown Debug DLL beside an executable does not make the program correctly built. It may also cause Windows to load an incompatible file before a valid dependency.

Do not use regsvr32

regsvr32 is used for DLLs that support COM self-registration, normally through a function such as DllRegisterServer.

msvcr120d.dll is a C runtime library, not a COM or ActiveX component. Registering it will not repair a missing runtime dependency and may produce an error such as “the module was loaded but the entry point was not found.” Microsoft documents the intended use of regsvr32 and COM self-registration.

Do not assume SFC repairs every DLL

SFC repairs protected Windows system files. It does not normally install Visual Studio Debug libraries or fix a third-party program that was compiled with /MDd.

Do not install every Visual C++ package blindly

Installing both x86 and x64 release packages can be appropriate for a computer running many applications. It still will not supply msvcr120d.dll, and installing newer Visual C++ versions does not replace Visual C++ 2013.

Frequently asked questions

Is msvcr120d.dll a Windows system file?

No. It is a Microsoft Visual C++ 2013 Debug runtime file associated with Visual Studio and applications built with that toolset. It is not a normal Windows component.

Is msvcr120d.dll included in Visual C++ 2013 Redistributable?

No. The normal Visual C++ 2013 Redistributable supplies the release runtime, including msvcr120.dll. Microsoft identifies the Debug CRT as non-redistributable.

Why did installing Visual C++ 2013 do nothing?

You probably installed the correct package for msvcr120.dll, while the program is requesting msvcr120d.dll. The final d means that the program needs a Debug build dependency, which the ordinary redistributable is not intended to install.

Should I install both the x86 and x64 packages?

Install the package matching the application. A 32-bit application needs x86 even on 64-bit Windows. A 64-bit application needs x64. Installing both can help a computer that runs different applications, but neither package supplies the Debug DLL.

What if msvcr120d.dll is already on the computer?

The file may be the wrong architecture, damaged, incompatible with the application, or located somewhere Windows does not search. Another plugin or dependency may also be requesting a different missing file. Do not replace it with an unverified download.

Does msvcp120d.dll indicate the same problem?

Usually. The d suffix identifies another Visual C++ 2013 Debug dependency. Multiple filenames ending in d.dll strongly suggest that the program or plugin was built in Debug mode.

Can I install Visual Studio to get the file?

A developer can install the matching Visual Studio development components for controlled testing. That is not a normal consumer repair, and it does not make an incorrectly distributed application suitable for end users.

Can Windows Update install this file?

There is no verified basis to expect ordinary Windows Update to install msvcr120d.dll. It belongs to Visual Studio and application development rather than the Windows operating system.

Will DirectX, .NET, or a driver update fix this error?

Not normally. Those are separate dependencies. Use them only when the program reports an additional problem that specifically requires them.

What should I tell the software developer?

Send the full error text, program name and version, Windows version, application architecture if known, and details about when the error began. Mention whether it started after an update, reinstall, file move, antivirus quarantine, or plugin installation. Include any other missing Debug DLL names.

What is the most likely final fix?

For an ordinary released program, the publisher must rebuild and distribute a Release version that uses the release runtime. For a developer-owned project, select Release, use /MD, rebuild all native dependencies, and match the intended x86 or x64 architecture.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.