vccorlib120.dll Not Found: A Complete Runtime Repair Path

vccorlib120.dll is a Microsoft Visual C++ 2013 runtime file used by some applications built with C++/CX and Windows Runtime support. If vccorlib120.dll is missing, not found, or cannot be loaded, the safest first repair is to install or repair the official Visual C++ 2013 Redistributable that matches the affected program.

On 64-bit Windows, install both the x86 and x64 Visual C++ 2013 packages when you do not know whether the program is 32-bit or 64-bit. On 32-bit Windows, install the x86 package. Do not download a loose copy of vccorlib120.dll from a DLL download site, and do not use regsvr32 to register this runtime file.

As an Amazon Associate I earn from qualifying purchases.

Fix 1: Install the official Visual C++ 2013 runtime

Time needed: 10 to 15 minutes, plus a restart.

vccorlib120.dll belongs to the Microsoft Visual C++ 2013, also called VC++ 12.0, runtime family. The 2013 runtime is separate from the newer Visual C++ 2015–2022 or 2015–2026 packages. Installing only a newer runtime does not necessarily install vccorlib120.dll.

Start with Microsoft’s Visual C++ 2013 Redistributable download page. Microsoft also maintains a latest supported Visual C++ Redistributable reference, which explains why older runtime families remain installed side by side.

Choose the correct package

The package must match the application, not merely the Windows installation.

• vcredist_x86.exe installs the 32-bit runtime.
• vcredist_x64.exe installs the 64-bit runtime.
• A 32-bit application requires the x86 runtime even when Windows is 64-bit.
• A 64-bit application requires the x64 runtime.
• On 64-bit Windows, installing both packages is appropriate when several programs are affected or the application architecture is unknown.
• On 32-bit Windows, install only the x86 package.

The names of the Windows folders can be confusing. On 64-bit Windows, Microsoft places the 32-bit runtime in %WinDir%\SysWOW64 and the 64-bit runtime in %WinDir%\System32. On 32-bit Windows, the x86 runtime is placed in %WinDir%\System32.

For direct Microsoft downloads, use the official x86 installer and official x64 installer.

Install the packages

1. Close the affected program or game.
2. Download the x86 installer from Microsoft.
3. Open File Explorer and go to the folder containing the download.
4. Right-click vcredist_x86.exe.
5. Select Run as administrator.
6. Accept the license terms if prompted.
7. Select Install.
8. Wait for the installer to finish.
9. If Windows is 64-bit, repeat the process with vcredist_x64.exe.
10. Restart Windows.
11. Open the original application.

If the program starts normally, the missing runtime was the immediate problem. If the same error returns, continue with the repair steps below rather than copying a DLL manually.

Repair an existing installation

The runtime may already be installed but damaged, incomplete, or registered incorrectly in the installer database.

1. Press Win+R.
2. Type appwiz.cpl.
3. Press Enter.
4. Find Microsoft Visual C++ 2013 Redistributable in the list.
5. Look for the x86 and x64 entries separately.
6. Select one entry.
7. Choose Change or Uninstall/Change.
8. Select Repair.
9. Allow the repair to finish.
10. Repeat for the other architecture if it is installed.
11. Restart Windows.
12. Test the affected program again.

If the repair option fails, uninstalling and reinstalling the official package can help, but record the displayed error first. Do not remove unrelated Visual C++ versions simply because they have similar names. Different applications can require different runtime families.

Microsoft’s currently listed legacy package table identifies the 2013 x86 and x64 packages as version 12.0.40664.0. Older legitimate Microsoft builds also exist, including 12.0.40660.0 and 12.0.21005.1. The filename alone is not enough to decide whether an older copy is suitable.

Fix 2: Repair the application or game that reports the error

Time needed: 10 minutes for a launcher repair, or longer for a full reinstall.

The Visual C++ runtime can be installed system-wide, but Microsoft also allows applications to deploy runtime files privately in the application’s own directory. This means a program can still fail after the system redistributable has been repaired if its local copy of vccorlib120.dll is missing or damaged.

This is especially common after:

• An interrupted application or game update.
• A failed reinstall.
• A cleanup utility removing an application file.
• A launcher restoring only part of a game.
• A vendor installer deploying an incomplete prerequisite.
• An application carrying an older private runtime copy.

Use the affected program’s own repair or verification feature first.

Repair a desktop application

1. Press Win+I to open Settings.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on Windows 10.
4. Find the application that displays the error.
5. Select the three-dot menu on Windows 11, or select the application entry on Windows 10.
6. Choose Advanced options if available.
7. Select Repair.
8. Start the program again.

If there is no Repair option, use the application’s original installer and select Repair, Modify, or a similar option. If the program was installed through a launcher, open that launcher and look for Verify, Repair, or Scan and repair under the game or application menu.

Reinstall the application when its local files are damaged

If repairing the runtime does not help and only one program fails, reinstall that program from its official installer or launcher.

1. Close the program and its launcher.
2. Open Settings > Apps > Installed apps.
3. Select the affected application.
4. Choose Uninstall.
5. Restart Windows if prompted.
6. Reinstall the program from its original vendor or launcher.
7. Allow all prerequisite installers to run.
8. Start the program again.

Do not assume that reinstalling a game always reinstalls every Microsoft prerequisite. Some installers offer an optional prerequisite step, while others expect the Visual C++ runtime to already exist on the computer. Install or repair the official Visual C++ 2013 packages separately if the application still reports the missing file.

Fix 3: Check Windows Security quarantine

Time needed: 5 to 10 minutes.

Antivirus protection can quarantine a runtime file or block an installer. This is more likely when the error appeared immediately after a security scan, application update, or attempted reinstall.

Check Protection History before restoring anything.

1. Open the Start menu.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Open any item that mentions the application, installer, or vccorlib120.dll.
8. Check the file path and detection details.
9. If the item clearly came from the official Microsoft redistributable or the affected program’s verified installer, follow your organization’s security policy before choosing Restore or Allow on device.
10. If the path is a temporary folder, an unexpected user-writable folder, or an unknown download location, do not restore it.
11. Reinstall the runtime or application from its official source instead.

Restoring an unverified DLL can bring back a modified or unsafe file, and Windows Security may detect it again. The filename by itself does not prove that a file is genuine.

If the security product belongs to an employer or school, contact the administrator before changing quarantine decisions. For a personal computer, the safer recovery path is normally to remove the questionable copy and reinstall the application or Microsoft runtime from its official installer.

Fix 4: Check whether the wrong local copy is loading

Time needed: 10 to 20 minutes.

A file can exist on the computer while the application still fails. Windows desktop applications commonly search the application directory before system directories. Therefore, a damaged application-local copy can take precedence over a correctly installed system runtime.

Check the folder named in the error message first.

1. Read the full error dialog and note the path, if one is shown.
2. Open File Explorer.
3. Browse to the application’s installation folder.
4. Look for vccorlib120.dll.
5. Right-click the file and select Properties.
6. Review the Digital Signatures tab if present.
7. Review the Details tab, but do not expect every Microsoft file table to publish a human-readable description or internal name.
8. Do not replace the file with a random download.
9. Use the application’s repair or reinstall function instead.

You can also check the normal runtime locations:

• On 64-bit Windows, the 64-bit copy is normally under %WinDir%\System32.
• On 64-bit Windows, the 32-bit copy is normally under %WinDir%\SysWOW64.
• On 32-bit Windows, the x86 copy is normally under %WinDir%\System32.

The presence of a file in one of these folders does not prove that it matches the application architecture. A 32-bit program cannot use the x64 runtime merely because the operating system is 64-bit.

A persistent error can also mean that another dependent runtime file is missing. The named DLL may be the first unresolved dependency reported by the loader, not the only damaged file. Repairing the complete Visual C++ 2013 package is safer than replacing individual files.

Fix 5: Check Windows Features without enabling random components

Time needed: 5 minutes.

vccorlib120.dll is not installed through the Windows Features dialog. It is part of the Visual C++ runtime or an application’s private deployment. Turning on unrelated features such as .NET Framework components, legacy media features, or virtualization will not normally restore it.

You can confirm this without changing anything:

1. Press Win+R.
2. Type optionalfeatures.
3. Press Enter.
4. Review the available Windows features.
5. Do not enable a feature merely because its name includes “Windows,” “Runtime,” or “Framework.”
6. Select Cancel when finished.

Windows Features can be relevant to a different application error, but there is no general checkbox that replaces the Visual C++ 2013 Redistributable. Install the matching Microsoft package instead.

Fix 6: Run DISM and SFC when Windows itself may be damaged

Time needed: 15 to 30 minutes, depending on the system.

DISM and SFC are appropriate when several unrelated programs fail, system files also report errors, Windows components behave abnormally, or the Visual C++ installer cannot write or validate files. They are not the primary replacement for a missing third-party Visual C++ runtime.

Microsoft recommends running DISM before SFC.

1. Open the Start menu.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait until DISM completes.
2. Keep the elevated Command Prompt open.
3. Run:

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Repair or reinstall the Visual C++ 2013 Redistributable.
4. Test the affected program.

Possible SFC results include:

• Windows Resource Protection found no integrity violations.
• Windows Resource Protection found corrupt files and successfully repaired them.
• Windows Resource Protection found corrupt files but was unable to fix some of them.

SFC scans protected Windows files. It may not restore a missing Visual C++ redistributable because that runtime is supplied by Microsoft’s redistributable installer or by the application that deployed it.

Repeating SFC and DISM without knowing what changed can make this step tedious. Outbyte PC Repair offers a free scan that shows what it identifies, while the repair is performed by the full version; it is optional, and reinstalling the affected program remains the definitive fix when the missing file belongs to that application.

If DISM or SFC reports errors that it cannot repair, restart Windows, install pending updates, and run the commands again. If the problem affects many system components, use Microsoft’s recovery options rather than continuing to replace individual DLL files.

Fix 7: Troubleshoot a failed Visual C++ installer

Time needed: 15 to 30 minutes.

If vcredist_x86.exe or vcredist_x64.exe will not install, the installer may be blocked by permissions, a pending restart, an incomplete Windows update, or installer-cache damage.

Try these steps in order:

1. Restart Windows.
2. Close browsers, launchers, and other installers.
3. Download the package again from Microsoft.
4. Right-click the installer.
5. Select Run as administrator.
6. Install the x86 package.
7. Restart if requested.
8. Install the x64 package on 64-bit Windows.
9. Restart again.
10. Test the application.

Microsoft documents optional command-line switches for supported Visual C++ redistributable installers. Open an elevated Command Prompt, change to the folder containing the installer, and run commands such as:

vcredist_x86.exe /install /passive /norestart

vcredist_x64.exe /install /passive /norestart

These commands request an installation with limited user interaction and no automatic restart. Legacy 2013 installer behavior can differ, so use the normal graphical installer first.

For logging, Microsoft documents the /log option. If the installer fails, examine the temporary installer log path:

%TEMP%\dd_vcredist_<arch>_<timestamp>.log

Record the displayed error code. Codes such as 1603, 1620, or 1714 can point to different installer conditions, so the code and log are more useful than repeatedly running the installer.

Do not delete random files from System32, SysWOW64, or the Windows Installer cache to force an installation. If the log indicates a broader Windows Installer problem, repair that problem first or contact the application vendor with the log details.

Fix 8: Install pending Windows updates

Time needed: 10 minutes plus the update and restart time.

A pending update or incomplete restart can interfere with installers and application launches.

Windows 11

1. Press Win+I.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart when Windows requests it.
6. Return to Windows Update.
7. Check again until no immediate updates remain.
8. Repair or reinstall the Visual C++ 2013 package.
9. Test the affected application.

Windows 10

1. Press Win+I.
2. Select Update & Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart Windows.
7. Re-run the Visual C++ repair.

Updates are useful when the error began after a failed upgrade or system change, but they do not replace the Visual C++ 2013 runtime. Keep the runtime repair in the sequence.

Fix 9: Check drivers only when the vendor package is involved

Time needed: 10 to 30 minutes.

vccorlib120.dll is not itself a driver component. Reinstalling a graphics, chipset, printer, or audio driver is not a general solution for this error.

A driver-related repair makes sense only when:

• The error appears inside a vendor’s driver control panel.
• The driver package also installs a desktop application.
• The error began immediately after a driver installation.
• Device Manager reports a related device problem.
• The vendor installer specifically lists Visual C++ as a prerequisite.

Check Device Manager as follows:

1. Right-click the Start button.
2. Select Device Manager.
3. Expand the category related to the affected hardware.
4. Look for a yellow warning icon.
5. Right-click the device.
6. Select Properties.
7. Review the General tab for a device status message.
8. Open the Driver tab.
9. Record the provider, date, and version.
10. Use Update Driver only when you have a verified driver source or Windows Update offers a suitable driver.
11. If the problem began immediately after a driver change, review whether Roll Back Driver is available.
12. Restart Windows.
13. Repair the Visual C++ runtime and the vendor application separately.

Guessing among dozens of driver versions is time-consuming. Outbyte Driver Updater provides a free scan showing what it identifies, while the driver installation is performed by the full version; it is optional, and it does not replace the application installer when that installer owns the missing runtime.

Fix 10: Use System Restore only after identifying a suitable restore point

Time needed: 20 to 45 minutes if a restore point exists.

System Restore is appropriate when the error began immediately after a major application update, failed upgrade, or system change and a suitable restore point is available. It should not be the first step for an isolated missing Visual C++ file.

1. Open the Start menu.
2. Type Create a restore point.
3. Open the matching Control Panel result.
4. Select System Restore.
5. Choose Next.
6. Review available restore points.
7. Select one created before the error began.
8. Select Scan for affected programs if available.
9. Review the result.
10. Continue only if the restore point is appropriate.
11. Follow the prompts to restart Windows.

System Restore does not replace the need to reinstall a damaged application or Visual C++ package. Use it when the timing strongly points to a recent system change and normal repair has not worked.

Fix 11: Resolve a startup pop-up with no visible program

Time needed: 10 to 30 minutes.

Sometimes the error appears during startup even though no application window is visible. An incomplete uninstall, updater, scheduled task, or service may still be trying to launch an old executable.

Start with the error dialog:

1. Record the full message.
2. Record any executable path shown in the dialog.
3. Note whether the path belongs to a game, utility, driver control panel, or recently removed application.
4. Open Settings > Apps > Installed apps.
5. Search for the related program.
6. Repair or uninstall it if it is no longer needed.
7. Restart Windows.
8. If the program is still required, reinstall it from its official installer.

Do not solve an unidentified startup error by placing a loose DLL into a system folder. The correct repair is to identify the program that is launching and repair or remove that program.

If no path appears, inspect Task Manager > Startup apps for a matching vendor or program name. Disable only an entry you recognize, then restart and check whether the dialog disappears. A disabled startup entry may identify the source, but the underlying application should still be repaired or uninstalled properly.

Why regsvr32 is not the fix

regsvr32 registers DLLs that provide the appropriate registration entry point, commonly DllRegisterServer. It is not a general command for repairing every missing DLL.

Do not run:

regsvr32 vccorlib120.dll

This Visual C++ runtime library should be installed through the Visual C++ redistributable or the application’s installer. Running regsvr32 can produce an error that does not address the missing-runtime problem, and it does not correct a wrong architecture, missing dependency, damaged application-local copy, or incomplete installation.

Microsoft documents regsvr32 as a DLL registration tool, not as a general missing-DLL repair method.

Why downloading a standalone DLL is unsafe

Searching for vccorlib120.dll and downloading the first matching file is risky because the copy may have:

• The wrong x86 or x64 architecture.
• An incompatible build.
• Missing dependent runtime files.
• A damaged or modified binary.
• No trustworthy publisher verification.
• A location that causes the application to load a bad private copy.

It can also conceal the actual problem, such as an incomplete game installation or antivirus quarantine.

Use Microsoft’s Visual C++ 2013 Redistributable download page or the affected program’s official installer. A verified application-local deployment can be appropriate when the software vendor documents it, but manually copying an unknown DLL into System32 or SysWOW64 is not an official repair procedure.

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

What vccorlib120.dll is and is not

vccorlib120.dll is part of the Microsoft.VC120.CRT runtime file set. Microsoft lists it alongside other Visual C++ 2013 runtime files, including msvcp120.dll and msvcr120.dll.

The 120 in the filename refers to the VC++ 12.0 runtime generation, associated with Visual Studio 2013. It does not mean Visual C++ 2020 or Visual C++ 2022.

The file is related to C++/CX and Windows Runtime support. Microsoft’s current package tables do not provide a definitive human-readable Description or Internal Name for the file, so those fields should not be treated as authoritative identification.

It is not normally a base Windows component. It can be installed by:

• The Microsoft Visual C++ 2013 Redistributable.
• An application that deploys the runtime locally.
• A game installer or launcher.
• A vendor installer that includes Visual C++ as a prerequisite.
• Visual Studio or a development environment used to build or run software.

The application that displays the error is often the best clue to which installation originally supplied the file.

Root causes and the correct response

Likely cause	Typical clue	Correct response
Missing or damaged VC++ 2013 runtime	Several older applications fail at launch	Install or repair the official x86 and/or x64 2013 redistributable
Wrong architecture	One 32-bit application fails on 64-bit Windows	Install the x86 package, even on 64-bit Windows
Missing application-local copy	Only one program fails after an update or reinstall	Repair or reinstall that application
Antivirus quarantine	Error began after a security scan	Check Protection History and reinstall from a verified source
Damaged application files	The launcher reports missing or corrupt files	Use the launcher’s repair or verification feature
Windows component corruption	Multiple unrelated programs and system components fail	Run DISM, then SFC, and repair the runtime afterward
Installer permissions or cache damage	The redistributable installer fails	Run as administrator, restart, update Windows, and inspect the installer log
Recent system change	The error began after an update or failed upgrade	Repair the application and runtime, then consider System Restore
Stale startup entry	A pop-up appears before the desktop is fully ready	Identify and repair or remove the program launching at startup
Driver package application failure	A vendor control panel fails while the device itself works	Repair that vendor application and its VC++ prerequisite

No universal list of games or programs uses vccorlib120.dll. Any native application built against the Visual C++ 2013 runtime can potentially depend on it.

Exact error messages you may see

Windows can present the same underlying problem with slightly different wording:

The program can't start because vccorlib120.dll is missing from your computer.
Try reinstalling the program to fix this problem.

The code execution cannot proceed because vccorlib120.dll was not found.
Reinstalling the program may fix this problem.

This application has failed to start because vccorlib120.dll was not found.
Reinstalling the application may fix this problem.

A damaged or incompatible copy may produce a bad-image message:

C:\path\vccorlib120.dll is either not designed to run on Windows
or it contains an error.
Try installing the program again using the original installation media
or contact your system administrator or the software vendor for support.
Error status 0xc000012f

The exact wording and status code vary between Windows versions and failure conditions. A bad-image message does not prove that the named DLL is the only damaged file.

When to contact the application vendor

Contact the software vendor when:

• The official Visual C++ 2013 packages install successfully but the program still fails.
• Only that program reports the error.
• The application has an application-local copy of the runtime.
• The launcher’s repair process reports an error.
• A clean reinstall does not restore the program.
• The startup dialog points to an updater or service from that vendor.

Include:

• The exact error text.
• A screenshot of the dialog.
• The program name and installed version.
• The executable path shown in the error.
• Whether Windows is 32-bit or 64-bit.
• Whether the x86 and x64 Visual C++ 2013 packages are installed.
• The result of the application’s repair or verification process.
• Any antivirus Protection History entry.
• The redistributable installer error code and log path, if installation failed.

Do not send a loose DLL as a workaround unless the vendor provides a documented, verified application-local package.

Frequently asked questions

Is vccorlib120.dll a Windows system file?

It is not normally a core Windows component. It is supplied by the Visual C++ 2013 runtime or by an application that bundles that runtime.

Which Visual C++ version provides it?

It belongs to Visual C++ 2013, also called the VC++ 12.0 runtime. The 120 in the name identifies that runtime generation.

Will Visual C++ 2015–2022 fix the error?

Not necessarily. Microsoft keeps the 2013 and earlier runtime families separate from newer packages. Install or repair Visual C++ 2013.

Why does a 64-bit computer need x86?

A 64-bit version of Windows can run 32-bit applications. Those applications require the x86 Visual C++ runtime, so the x86 package may be necessary even when the operating system is 64-bit.

Should I install both x86 and x64?

Install both on 64-bit Windows when the application architecture is unknown or several programs are affected. Install only x86 on 32-bit Windows.

Can I copy vccorlib120.dll into System32?

Do not copy a loose DLL from an unknown source. The wrong architecture or build can create another loader error and may leave dependent runtime files missing.

Should I use regsvr32?

No. regsvr32 is for registering DLLs that provide the appropriate registration entry point. The Visual C++ runtime should be installed through its redistributable or the application installer.

Why does the file exist but the program still fail?

The file may be the wrong architecture, a damaged application-local copy may be loading first, or another dependent runtime file may be missing. Repair the full runtime and the affected application.

Can antivirus quarantine cause the error?

Yes. Check Windows Security > Virus & threat protection > Protection history. Restore a quarantined file only when its path, source, publisher, and signature have been verified.

Will SFC repair the missing file?

Usually not by itself. SFC repairs protected Windows files, while vccorlib120.dll is normally supplied by the Visual C++ redistributable or the application. Run DISM and SFC when broader Windows corruption is suspected, then reinstall the correct runtime.

What if the redistributable installer fails?

Restart Windows, run the installer as administrator, install pending updates, retry, and inspect %TEMP%\dd_vcredist_<arch>_<timestamp>.log. Record any installer code before contacting Microsoft or the application vendor.

What about vccorlib120d.dll?

The d suffix identifies a debug runtime. It is intended for development scenarios and is not the normal end-user redistributable file. A retail application should normally be repaired with the released Visual C++ 2013 runtime or its own installer.