msvcp110.dll Is Missing: A Safe Repair Path for Windows 11 and 10

The exact dialog often says: “The program can’t start because MSVCP110.dll is missing from your computer. Try reinstalling the program to fix this problem.”

That msvcp110.dll message points to the Microsoft Visual C++ 2012 runtime, not to an ordinary Windows file that should be downloaded by itself.

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$128.99	Buy on Amazon
2		Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |...	$119.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use the description that best matches what you see.

• If the program says the file is missing or was not found, repair or install the Visual C++ 2012 redistributable first.
• If the error appears in a 32-bit program on 64-bit Windows, install the x86 package. Windows bitness and application bitness are not always the same.
• If the error appears in a 64-bit program, install the x64 package.
• If you do not know whether the program is 32-bit or 64-bit and Windows is 64-bit, install both x86 and x64 packages.
• If the message says “Bad Image,” “not designed to run on Windows,” or includes 0xc000012f, repair the runtime and the affected application rather than copying a replacement DLL.
• If only one game or application fails, verify or repair that application after repairing the runtime.
• If the DLL is present but Windows still cannot load it, suspect the wrong architecture, a damaged application-local copy, or another missing dependency.
• If antivirus quarantined the file, inspect Protection History before restoring anything.
• If several unrelated Windows programs fail, investigate Windows component corruption with DISM and SFC.

What exactly is msvcp110.dll

msvcp110.dll is a Microsoft Visual C++ runtime library file supplied with Visual Studio 2012, also known as VC11. It provides part of the C++ Standard Library used by programs compiled with that development environment.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$128.99

Buy on Amazon

Microsoft lists the file under the Microsoft.VC110.CRT package for x86, x64, and ARM redistribution packages in its Visual Studio 2012 redistribution documentation.

The publisher is Microsoft Corporation, but the file is not normally an inbox Windows component. An application may receive it through the Visual C++ redistributable installer, or a developer may deploy a private copy beside the application executable.

Some file databases describe its internal name as “Microsoft® C Runtime Library.” In practical troubleshooting terms, msvcp110.dll is the C++ runtime component. It is separate from msvcr110.dll, which is the separately named C runtime component.

The number 110 identifies the VC11 runtime generation. That corresponds to Visual Studio 2012. Visual Studio 2013 is VC12 and uses names such as msvcp120.dll, so installing the 2013 runtime does not provide the VC11 msvcp110.dll component.

Visual Studio 2012 reached the end of extended support on January 10, 2023, but older applications can still depend on its runtime. An old runtime can therefore be required on a fully updated Windows 10 or Windows 11 computer.

The safest first fix: repair Visual C++ 2012

The most likely solution is to repair or install the official Visual C++ 2012 Update 4 redistributable.

Use Microsoft’s Visual C++ 2012 Update 4 download page, or use the direct Microsoft installers:

• Visual C++ 2012 Update 4 x86 installer
• Visual C++ 2012 Update 4 x64 installer

Repair an existing installation

1. Close the affected application.
2. Press Win + R.
3. Type appwiz.cpl and press Enter.
4. Find Microsoft Visual C++ 2012 Redistributable (x86) and Microsoft Visual C++ 2012 Redistributable (x64).
5. Right-click the entry that matches the program and choose Change.
6. Select Repair.
7. Follow the installer prompts.
8. Restart Windows.
9. Try the application again.

If both entries exist, repair both. They are independent installations. Repairing the x86 package does not repair the x64 package, and repairing x64 does not repair x86.

If Change is not available, download the matching official installer and run it. The installer may offer repair, or it may reinstall the package over the existing installation.

Install the missing architecture

The correct package is determined by the application, not merely by the Windows edition.

• A 32-bit application needs the x86 redistributable.
• A 64-bit application needs the x64 redistributable.
• A 32-bit application still needs x86 when it runs on 64-bit Windows.
• On 64-bit Windows, install both when the application architecture is unknown or when several older programs are affected.

Do not assume that “64-bit Windows” means every application needs x64. Many games, launchers, utilities, and older creative applications remain 32-bit.

If the installer refuses to run on a 32-bit edition of Windows, the x64 package is not appropriate there. Use x86 for 32-bit Windows.

After installation, restart Windows even if the installer does not insist on it. Then launch the program again. A successful repair normally means the missing-DLL dialog disappears and the application proceeds to its normal startup.

Why System32 and SysWOW64 can be confusing

On 64-bit Windows, the directory names are counterintuitive:

• %WINDIR%\System32 normally contains 64-bit system files.
• %WINDIR%\SysWOW64 normally contains 32-bit system files.

This does not mean that every copy of msvcp110.dll must be in one of those folders. Some applications use an application-local copy in the same directory as the executable. Windows also follows a DLL search order that can cause an application-directory copy to be loaded before a centrally installed copy.

Microsoft explains this behavior in its documentation for the file-system redirector and DLL search order.

The path shown in the error can provide useful evidence:

• A path under System32 usually points toward the 64-bit runtime path.
• A path under SysWOW64 usually points toward the 32-bit runtime path.
• A path inside the application folder suggests a private copy supplied by the application.
• A path under a temporary or profile directory deserves additional investigation.

Do not delete a copy from either Windows directory to force another copy to load. Repair the appropriate redistributable instead.

Match the repair to the exact error

Different messages can point to different failures.

The 0xc000012f status does not prove that msvcp110.dll is the only problem. The same type of error can involve another invalid or incompatible binary.

If the DLL exists but the application still fails

A visible file is not proof that the application can use it. Windows may reject the file because of architecture, corruption, an incompatible private copy, or a missing dependency.

Work through these checks in order.

Check the application architecture

Look at the application’s documentation, installer name, vendor support information, or installation package. If the program is described as x86 or 32-bit, install x86. If it is described as x64 or 64-bit, install x64.

When you are uncertain on 64-bit Windows, installing both Visual C++ 2012 packages is appropriate. Installing x86 and x64 does not make them interchangeable; it simply supplies both runtime architectures for different applications.

Repair the application-local copy

If the error names a DLL inside the application’s own folder, the application may have deployed a private copy. Use the application’s repair option, reinstall it from the official installer, or use its file-verification feature.

Do not overwrite the private copy with a file copied from System32, SysWOW64, another computer, or a download site. A private deployment may require a particular serviced build or companion files.

Look for another missing dependency

“Specified module could not be found” can mean that a dependency of msvcp110.dll is missing. The visible filename is not always the true missing component.

If the official Visual C++ 2012 repair succeeds but the application still fails, repair or reinstall the application. If the application has a prerequisite folder, run the Visual C++ installer supplied by that application only when it comes from the application’s legitimate installation media or vendor installer.

Repair games and launchers after fixing the runtime

Games often install prerequisite packages during the first launch. If that installer was canceled, blocked, or interrupted, the game can remain unable to start even though the game files themselves are present.

First repair Visual C++ 2012. Then verify the game files.

Steam

1. Open Steam.
2. Open Library.
3. Right-click the affected game.
4. Choose Properties.
5. Select Installed Files.
6. Choose Verify integrity of game files.
7. Wait for the process to finish.
8. Launch the game again.

If the game includes a secondary installer for Microsoft Visual C++ components, allow it to complete. If Steam repeatedly skips or fails the prerequisite installer, repair the redistributable manually with Microsoft’s official package.

Epic Games Launcher

1. Open Epic Games Launcher.
2. Open Library.
3. Select the three-dot menu beside the game.
4. Choose Manage.
5. Select Verify.
6. Wait for verification to finish.
7. Start the game again.

If verification finds damaged files, let the launcher replace them. If only one game continues to fail after verification and the runtime repair, reinstalling that game may be necessary.

A launcher can hide the original Windows dialog. If possible, open the game’s installation folder and run its main executable directly once. The direct launch may reveal whether the problem is the runtime, a game file, or another dependency.

Repair creative applications and other desktop software

Older versions of Photoshop, Illustrator, Premiere, and similar applications can depend on Visual C++ runtime files. If only one Adobe or other desktop application shows the error, use this order:

1. Repair Visual C++ 2012 x86 and x64 as appropriate.
2. Restart Windows.
3. Use the application’s own repair or update function.
4. Reinstall the application if repair does not restore its private files.
5. Restart again and test the application.

Do not remove every Visual C++ redistributable installed on the computer. Older generations remain side by side because different programs were built against different runtime versions.

Check antivirus quarantine carefully

Security software can remove or block a DLL, particularly when the file is inside an application directory. Do not assume quarantine is the cause without checking the security record.

1. Open Windows Security.
2. Select Virus & threat protection.
3. Choose Protection history.
4. Review events from the time the error began.
5. Open any event that names msvcp110.dll or the affected application.
6. Check the reported path and publisher.
7. Do not restore the file solely because its name looks familiar.

If the file came from an official Microsoft redistributable or a trusted, properly signed application installation and the detection is demonstrably a false positive, follow the security product’s restore process. Reinstalling the official package is often safer than restoring a damaged application-local file.

Rank #2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

• STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
• OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
• OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
• PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
• GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

Buy on Amazon

Do not permanently disable antivirus protection or create a broad folder exclusion to make the error disappear. Re-enable protection after any controlled test. Microsoft describes the relevant choices in its Protection History guidance.

Use DISM and SFC for broader Windows corruption

msvcp110.dll is normally supplied by Visual C++ rather than protected as an ordinary Windows inbox file. That makes the redistributable installer the primary repair.

DISM and SFC become relevant when:

• Several unrelated Windows applications fail.
• Windows components are also reporting corruption.
• The Visual C++ installer will not run.
• Windows Installer or other system services are damaged.
• The error began alongside broader system instability.

Run DISM and SFC

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. Then run:

sfc /scannow

1. Wait for SFC to reach 100 percent.
2. Restart Windows.
3. Repair or reinstall Visual C++ 2012 again if the original application error remains.

Microsoft provides the recommended sequence in its SFC and DISM repair instructions.

A successful result means the commands complete and report their findings without an unrecoverable error. If SFC reports that it repaired files, restart and test again. If it reports that it found corrupt files but could not repair some of them, the Windows component store or installation may need further repair.

Running DISM and SFC manually can mean waiting through long scans and interpreting results without knowing what changed. Outbyte PC Repair can scan and show what it found, while repair is performed by the full version; it is optional, and the official Visual C++ installer remains the direct fix for this runtime.

Check Windows Update when installation fails

Windows Update does not normally install Visual C++ 2012 as a replacement for the redistributable. It can still matter when Windows Installer or related system components are damaged.

1. Open Start.
2. Select Settings.
3. Choose Windows Update.
4. Select Check for updates.
5. Install pending updates.
6. Restart Windows.
7. Run the official Visual C++ 2012 installer again.

If the installer reports access, file-lock, or Windows Installer errors, restart first. Then run the Microsoft installer as administrator and check whether security software recorded a block. Microsoft also provides Visual C++ redistributable installation troubleshooting.

Drivers are usually not the fix

msvcp110.dll is not a graphics-driver DLL, chipset-driver DLL, or printer-driver DLL. Reinstalling a GPU driver is not a general solution for this message.

Driver repair is relevant only when the error appears inside a specific vendor’s driver, firmware, or hardware utility installer. In that case:

1. Note the exact installer or utility named in the error.
2. Open Device Manager by right-clicking Start and choosing Device Manager.
3. Expand the category related to the affected hardware.
4. Right-click the device and choose Properties.
5. Review the Driver tab for the provider and version.
6. Obtain the correct package from the hardware vendor.
7. Install the vendor package and restart Windows.
8. Retry the utility that originally failed.

Do not use Device Manager to search for msvcp110.dll. Device Manager manages hardware drivers, not Visual C++ runtime deployment.

Hunting through Device Manager and vendor pages can mean guessing which of many drivers is stale. Outbyte Driver Updater can scan and show which drivers need attention, while driver installation is performed by the full version; it is optional and does not replace repairing the Visual C++ runtime or reinstalling an affected application.

Why Visual C++ 2013 or 2015–2022 is not enough

Installing the newest Visual C++ package is not automatically the right fix.

Microsoft treats Visual C++ 2013 and earlier redistributables as separate, side-by-side runtime generations. The current Visual C++ 2015–2022 package is the v14 generation and does not replace the VC11 runtime required by msvcp110.dll.

Use the latest supported Visual C++ downloads documentation to understand the side-by-side model, but install the specific Visual C++ 2012 Update 4 package for this file.

Do not uninstall Visual C++ 2010, 2012, 2013, or 2015–2022 packages simply because another version is also installed. Removing an unrelated generation can break a different program.

Why regsvr32 does not repair this error

Do not run:

regsvr32 msvcp110.dll

A C++ runtime DLL is not normally a self-registering COM or ActiveX component. It does not need to be registered in the Windows Registry for an application to use it.

regsvr32 applies to particular COM or ActiveX DLLs that expose a registration entry point such as DllRegisterServer, normally when the vendor specifically instructs the user to register that component. Microsoft explains this distinction in its documentation about COM self-registration.

If regsvr32 reports that the entry point is missing, that does not indicate a new msvcp110.dll problem. It means the command is not appropriate for this runtime file.

Do not download the DLL by itself

Avoid search-result DLL download sites and random file mirrors. A standalone download can contain malware, the wrong architecture, an incompatible serviced build, or a modified binary. Even a genuine file may not fix the root cause if the application needs another dependency or if the installed runtime registration and servicing state are damaged.

Do not copy msvcp110.dll from another computer. Do not copy a file into System32 or SysWOW64 manually. Do not replace an application-local file with a file taken from a different program.

Use one of these supported sources instead:

• The official Visual C++ 2012 Update 4 download page
• Microsoft’s official x86 installer
• Microsoft’s official x64 installer
• The affected application’s official installer, repair function, or file-verification feature

Microsoft documents application-local deployment as a developer-controlled deployment method, not as a reason for end users to copy DLLs manually. The safer approach is to let the redistributable or application installer deploy the complete matching set of files.

When System Restore is appropriate

System Restore is a fallback, not the first repair for a missing Visual C++ runtime.

Consider it only when:

• The failure began immediately after a software installation, update, or driver change.
• Repairing Visual C++ 2012 did not help.
• Repairing or reinstalling the application did not help.
• The computer has a suitable restore point.

To open it:

1. Press Win + R.
2. Type rstrui.exe.
3. Press Enter.
4. Choose a restore point from before the failure began.
5. Review the affected programs.
6. Follow the wizard if the restore point is appropriate.

Microsoft describes the process in its System Restore documentation.

System Restore does not replace the need to install the correct runtime if the application genuinely requires Visual C++ 2012.

Prevention after the application starts

Once the program works again:

• Leave the required x86 and x64 redistributables installed.
• Do not remove older Visual C++ generations as cleanup.
• Let game and application prerequisite installers finish.
• Keep the application installed from its official source.
• Review antivirus quarantine events instead of restoring unknown files automatically.
• Keep Windows updated, especially when installers or Windows Installer are failing.
• Record which architecture the application requires if you maintain several older programs.
• Avoid registry cleaners and DLL replacement utilities that alter system directories.

There is no single universal file size, timestamp, or version that proves every copy of msvcp110.dll is correct. Microsoft-serviced packages and application-bundled copies can differ. The installer source, architecture, application compatibility, and complete runtime package matter more than comparing a DLL’s size with a number found online.

FAQ

Is msvcp110.dll a Windows system file?

It is a Microsoft file, but it is not an ordinary Windows inbox component. It belongs to the Visual C++ 2012 runtime and may be installed centrally or deployed privately by an application.

Does msvcp110.dll belong to Visual Studio 2012?

Yes. The 110 name identifies VC11, the runtime generation associated with Visual Studio 2012.

Should I install Visual C++ 2012, 2013, or 2015–2022?

For msvcp110.dll, install or repair Visual C++ 2012. Visual C++ 2013 and 2015–2022 are separate generations and are not substitutes for VC11.

Do I need x86 or x64?

Use x86 for a 32-bit program and x64 for a 64-bit program. On 64-bit Windows, install both when you do not know which architecture the affected applications use.

Why does a 32-bit application need x86 on 64-bit Windows?

The application loads libraries matching its own architecture. A 32-bit program needs the 32-bit Visual C++ runtime even when the operating system itself is 64-bit.

The file is already in System32. Why does the error remain?

The program may be 32-bit and require x86, may be loading an incompatible application-local copy, or may be failing because another dependency is missing. Repair both runtime architectures when appropriate, then repair the application.

Can SFC repair msvcp110.dll?

SFC can repair protected Windows components, but it is not the primary repair for this Visual C++ runtime file. Use the official Visual C++ 2012 redistributable first. Use SFC and DISM when broader Windows corruption or installer failure is also present.

Should I run regsvr32 msvcp110.dll?

No. Runtime DLLs are not normally registered with regsvr32. Install or repair the redistributable instead.

What if antivirus quarantined the file?

Check Windows Security > Virus & threat protection > Protection history. Confirm the path and publisher before taking action. Reinstalling the official runtime or application is safer than restoring an unknown standalone DLL.

When should I reinstall the game or application?

Reinstall it when the runtime repair succeeds but only that application still fails, when the error names a file in the application directory, or when Steam or Epic verification reports damaged files.

What information should I collect if the error persists?

Record the application name, exact error text, executable path, full path shown for the DLL, Windows edition and architecture, whether the application is 32-bit or 64-bit, installed Visual C++ 2012 x86 and x64 entries, antivirus history, and any recent installation or update.

That information distinguishes a missing runtime from an architecture mismatch, damaged application files, a blocked prerequisite installer, a private deployment problem, or another missing dependency.

Quick Recap

SaleBestseller No. 1

Microsoft Windows 11 (USB)

Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation

$128.99

Bestseller No. 2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

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.