vcruntime140.dll Not Found: The Complete Runtime Repair Path

If Windows reports that vcruntime140.dll is missing or was not found, install or repair the official Microsoft Visual C++ v14 Redistributable that matches the application. On 64-bit Windows, install both the x86 and x64 packages when you do not know which type of program is failing, then restart Windows and repair the affected application if the message remains.

What this file actually does

vcruntime140.dll is a Microsoft Visual C/C++ runtime library. Programs compiled with Microsoft Visual C++ use it for common runtime functions, so the file belongs to the application’s software dependencies rather than to a particular game, graphics card, printer, or browser.

As an Amazon Associate I earn from qualifying purchases.

Microsoft includes this library in the compatible Visual C++ v14 runtime family used by Visual Studio 2015, 2017, 2019, 2022, and later MSVC toolsets. Applications built with the compatible toolsets can use the latest supported v14 Redistributable. Microsoft documents this binary compatibility.

Some file catalogs describe a historical copy as part of Microsoft Visual Studio 2015 RC, with the internal description Microsoft® C Runtime Library. That label does not mean you should install the full Visual Studio development environment or search for an old standalone DLL. The supported repair is the current Microsoft Visual C++ Redistributable.

The runtime may be installed centrally in these locations:

• %WINDIR%\System32 for native x64 or ARM64 runtime files.
• %WINDIR%\SysWOW64 for x86 runtime files on 64-bit Windows.
• The application’s own folder when the developer uses local deployment.

System32 does not automatically mean that the file shipped with the original Windows installation. The official Visual C++ Redistributable can install runtime files there as centrally managed components. Microsoft explains the difference between central and application-local deployment in its Visual C++ deployment documentation.

The current package is not limited to vcruntime140.dll. It can also contain related files such as:

• vcruntime140_1.dll
• msvcp140.dll
• msvcp140_1.dll
• msvcp140_2.dll

These files work together, but they are not interchangeable. Renaming one file to create another will not repair the runtime.

Historical version numbers and file sizes are not useful replacement criteria. Microsoft updates the current v14 Redistributable, so the version shown on the official download page changes over time.

Causes and symptoms at a glance

What you see	Most likely meaning	First repair to try
“vcruntime140.dll is missing”	The required runtime is absent, incomplete, or the wrong architecture	Install the matching x86, x64, or ARM64 Redistributable
“vcruntime140.dll was not found”	Windows could not locate the runtime in the application or system search path	Install or repair the Redistributable, then repair the application
“Not designed to run on Windows” or error 0xc000012f	The DLL is damaged, incompatible, or the wrong architecture	Repair the runtime and application; use DISM and SFC if several programs fail
“vcruntime140_1.dll was not found”	A related v14 runtime component is missing	Repair the same Visual C++ Redistributable rather than renaming files
Error 0xc000007b	Often an x86/x64 mismatch or broader dependency problem	Install the architecture required by the application and repair the application
Only one game or program fails	Its local runtime copy or installation may be damaged	Verify or repair that application
The path contains WindowsApps	A packaged application may depend on Microsoft VCLibs	Repair or reset the Store application and update Windows
Many unrelated programs fail	Windows components, security software, storage, or the central runtime may be damaged	Repair the Redistributable, then run DISM followed by SFC
The file disappeared after antivirus detection	Security software may have quarantined it	Inspect Protection history and reinstall from Microsoft if appropriate
A device installer fails	The vendor’s utility may depend on Visual C++, but the DLL is not a driver	Repair the runtime, then reinstall the complete device package

Fix 1: Install the official Visual C++ Redistributable

This is the most likely solution for a clean Windows installation, a newly installed game, an interrupted application setup, or a missing runtime message.

Use Microsoft’s latest supported Visual C++ Redistributable download page. The direct Microsoft installers are:

• x86: vc_redist.x86.exe
• x64: vc_redist.x64.exe
• ARM64: vc_redist.arm64.exe

Choose the package by application architecture

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

• A 32-bit application needs the x86 Redistributable.
• A 64-bit application needs the x64 Redistributable.
• A native ARM64 application needs the ARM64 Redistributable.
• A 32-bit program can need x86 even when it runs on 64-bit Windows.
• A 64-bit program cannot use the x86 DLL.
• A 32-bit program cannot use the x64 DLL.

WOW64 allows 32-bit applications to run on 64-bit Windows, but it does not make 32-bit and 64-bit DLLs interchangeable. Microsoft explains this architecture boundary here.

To check the Windows architecture:

1. Right-click Start.
2. Select Settings.
3. Open System > About.
4. Read System type.

That tells you the operating system architecture, not necessarily the architecture of the failing application. A program installed under C:\Program Files (x86) is commonly 32-bit, while one under C:\Program Files is commonly 64-bit, but the folder is only a clue.

If you are on 64-bit Windows and do not know which type of application is failing, install both x86 and x64. This is also the correct approach when both 32-bit and 64-bit programs report runtime errors.

Install or repair the package

1. Close the application showing the error.
2. Download the required installer from one of Microsoft’s links above.
3. Open your Downloads folder.
4. Right-click vc_redist.x86.exe, vc_redist.x64.exe, or vc_redist.arm64.exe.
5. Select Run as administrator.
6. Accept the license terms.
7. Choose Install if the package is absent.
8. Choose Repair if the installer offers that option.
9. Repeat for the other architecture if needed.
10. Restart Windows.
11. Start the affected application again.

The repair worked if the program opens without the missing-DLL message. If the application still fails, note the complete path shown in the error and continue with the path-based diagnosis below.

You normally do not need to install the full Visual Studio development environment. The Redistributable supplies the runtime components required by compiled applications.

Fix 2: Repair the installed Redistributable through Windows

If Microsoft’s installer says that a newer version is already installed, repeatedly installing an older package is the wrong direction. The existing package may be present but damaged, or you may be repairing the wrong architecture.

1. Right-click Start.
2. Select Installed apps.
3. Search for Microsoft Visual C++ Redistributable.
4. Look for the x86 and x64 entries separately.
5. Select the three-dot menu beside the architecture you need.
6. Choose Modify.
7. Approve the administrator prompt.
8. Select Repair.
9. Restart Windows.
10. Test the application again.

The display name may contain a range such as Microsoft Visual C++ 2015–2022 Redistributable. The architecture shown in the entry, such as x86 or x64, matters more than the year range in the name.

If Modify or Repair is unavailable:

1. Download a fresh installer from Microsoft’s latest supported Redistributable page.
2. Right-click it.
3. Select Run as administrator.
4. Run the installation or repair.
5. Restart Windows.

Microsoft supports installer switches including /install, /repair, /uninstall, /passive, /quiet, /norestart, and /log. For an administrator repairing an existing package, these commands are valid:

vc_redist.x64.exe /repair /norestart

vc_redist.x86.exe /repair /norestart

Run the command from the folder containing the installer, or provide its full path. Microsoft describes the package behavior and registry locations in its Visual C++ redistribution documentation.

Do not uninstall every Visual C++ entry as a cleanup experiment. Different applications can require different runtime families, and x86 and x64 packages can both be needed.

Fix 3: Repair the affected application or game

If only one application fails after the Redistributable has been repaired, the application may carry a private copy of the runtime beside its executable. Windows searches the application directory early in the DLL search process, so a damaged local copy can override a healthy centrally installed copy. Microsoft documents the DLL search order.

For a normal desktop application:

1. Right-click Start.
2. Select Installed apps.
3. Find the affected program.
4. Open its three-dot menu.
5. Choose Modify, Repair, or Advanced options, depending on the program.
6. Select Repair.
7. Restart the application.

If there is no repair option:

1. Open the application’s installer from the original vendor.
2. Choose Repair if offered.
3. If repair is unavailable, uninstall the application.
4. Restart Windows.
5. Install the application again from its trusted installer.
6. Launch it before adding optional plugins or modifications.

For a game, open the game launcher and go to its Library. Open the menu beside the game and choose Verify, Verify files, Validate files, or the equivalent option. This replaces missing or damaged application-local files without requiring you to copy a DLL into a Windows folder.

If verification reports damaged files but the game still fails, uninstall and reinstall the game. The application’s own installer remains the definitive repair when the failing DLL path points into the game directory.

Fix 4: Check antivirus quarantine

A security product can quarantine a runtime file from an application directory or block an installer before the package is complete. Do not restore a file blindly just because the filename looks familiar.

To inspect Microsoft Defender’s records:

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Open the detection related to the application or DLL.
7. Check the complete file path and detection details.

Only restore or allow the file when its origin is clear, it came from a trusted Microsoft-signed installer or trusted application installer, and the detection is confirmed to be a false positive. Microsoft warns that allowing a genuine threat can put the computer and data at risk. Its Protection history guidance explains the available actions.

If the file was quarantined from a trusted application:

1. Leave the questionable file in quarantine until its provenance is established.
2. Update the security product.
3. Run a full scan.
4. Download the official Visual C++ Redistributable again.
5. Repair or reinstall the affected application.
6. Test the application after the scan completes.

If the same DLL is repeatedly quarantined, stop restoring it and investigate the detection. Repeated disappearance can indicate a compromised installer, an unsafe modification, or malware rather than an ordinary missing-runtime problem.

Fix 5: Handle a WindowsApps or Microsoft.VCLibs path

If the error names a path similar to:

C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop...

the application may be using a packaged C++ framework rather than only the ordinary centrally installed desktop Redistributable. Microsoft documents Microsoft.VCLibs.140.00.UWPDesktop as a framework dependency for packaged desktop applications. See Microsoft’s C++ Runtime packages documentation.

Do not take ownership of WindowsApps, delete files from it, or copy a replacement DLL into that directory.

Instead:

1. Open Microsoft Store.
2. Select Library.
3. Select Get updates.
4. Let the Store update the affected application and its framework packages.
5. Open Settings.
6. Select Apps > Installed apps.
7. Find the affected application.
8. Open its three-dot menu.
9. Select Advanced options.
10. Choose Repair.
11. If Repair does not help, choose Reset.
12. Restart Windows.
13. Test the application again.

Reset can remove the application’s local settings or cached data, so use it after Repair. If the application still fails, uninstall it from Installed apps, restart Windows, and reinstall it through Microsoft Store.

Fix 6: Repair Windows components with DISM and SFC

Use this step when several unrelated applications fail, built-in Windows applications are also damaged, the error points to a Windows component, or the issue began after an update or system reset.

Microsoft recommends running DISM before System File Checker. DISM repairs the Windows component store, while SFC checks protected Windows system files. These commands do not replace the Visual C++ Redistributable when that package itself is missing.

1. Open Start.
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:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish.
2. After it completes, run:

sfc /scannow

1. Wait until the scan reaches 100 percent.
2. Restart Windows.
3. Repair or reinstall the Visual C++ Redistributable again if the original error remains.

A successful repair means DISM completes without an error and SFC reports either that no integrity violations were found or that damaged files were repaired. If SFC reports that it could not repair some files, restart and run the commands again once. If the problem affects only one program, return to application repair rather than repeating system scans indefinitely.

Running DISM and SFC by hand can leave you repeating long checks without knowing which component changed. I recommend Outbyte PC Repair as an optional way to scan for the underlying Windows problems; its free scan shows what it found, while repair is performed by the full version.

Microsoft’s DISM and SFC instructions contain the current command sequence.

Fix 7: Install pending Windows updates

Windows updates can service centrally deployed runtime components, but they cannot repair every application-local copy.

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install all available updates.
5. Restart Windows, even if the update process does not appear to require it.
6. Check for updates again.
7. Test the application.

If the error began immediately after an update and many Windows applications fail, run DISM and SFC after installing pending updates. If only one application fails, repair that application instead of assuming that Windows Update damaged its private runtime.

Microsoft’s current Windows Update installation guidance covers the standard update process.

Fix 8: Repair drivers and device utilities correctly

vcruntime140.dll is not a hardware driver. If the message appears while installing software for a graphics card, camera, printer, scanner, or other device, the failing component is usually the vendor’s installer or user-mode utility that depends on Visual C++.

First repair the Redistributable. Then reinstall the complete device package from the hardware manufacturer’s trusted installation media.

You can also inspect the device in Device Manager:

1. Right-click Start.
2. Select Device Manager.
3. Expand the category for the device.
4. Right-click the device.
5. Select Properties.
6. Read the Device status message under the General tab.
7. Open the Driver tab.
8. Use Update Driver only when you have a suitable driver source.
9. If the vendor supplied a complete installer, close Device Manager and run that installer instead.
10. Restart Windows.
11. Test the utility or device again.

Do not replace a driver DLL with vcruntime140.dll. The runtime and the driver serve different purposes.

Device Manager can require hunting through hardware categories and guessing which package is stale. I recommend Outbyte Driver Updater as an optional way to scan for outdated drivers; its free scan identifies what it found, while driver installation is performed by the full version.

Fix 9: Use System Restore when the timing is clear

System Restore is appropriate when the problem began after a recent application installation, driver change, update, cleanup utility, or other system modification and a suitable restore point exists.

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point from before the problem began.
4. Select Scan for affected programs if available.
5. Review the programs and drivers that may be removed or rolled back.
6. Select Close to return to the restore wizard.
7. Select Next.
8. Select Finish.
9. Confirm the operation.
10. Let Windows restart and complete the restoration.

System Restore rolls back system files, registry settings, drivers, and installed programs. It does not normally remove personal documents, but recently installed applications or drivers may be removed. Do not use it merely because a single application needs the Redistributable.

Fix 10: Investigate recurring corruption or malware

If the official Redistributable installs successfully but vcruntime140.dll repeatedly disappears or becomes corrupted, the runtime may not be the original cause.

Check these possibilities:

• Antivirus or endpoint security repeatedly quarantines the file.
• A third-party cleanup utility removes an application-local copy.
• The disk has file-system or storage problems.
• Malware is altering or deleting files.
• An application update repeatedly installs a defective private runtime.
• A damaged user profile affects only one account.

Run a full security scan and inspect Protection history. If the problem returns after a clean Redistributable repair, check the drive for errors using the storage manufacturer’s diagnostic tools or Windows’ own drive properties. If the issue affects only one account, test the application from another Windows account. A user-profile-specific failure is a diagnostic possibility, not proof of a universal runtime problem.

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

Why regsvr32 does not fix this DLL

regsvr32 is designed for self-registering COM and ActiveX DLLs. It is not a general-purpose DLL installer.

Running this command is not a valid repair for the Visual C++ runtime:

regsvr32 vcruntime140.dll

The command does not install the runtime, restore missing dependencies, or select the correct architecture. It may produce an error saying that the DllRegisterServer entry point was not found. That result is expected for a normal runtime library. Microsoft explains the correct use and common errors for Regsvr32.

Use the Visual C++ Redistributable installer instead.

Why manual DLL copying is unsafe

Do not download a loose vcruntime140.dll from a random DLL website and copy it into System32, SysWOW64, or the application folder. That approach can introduce malware, install the wrong architecture, provide an incompatible build, or leave the rest of the runtime family damaged.

It also hides the cause. A missing runtime may result from an incomplete installation, a quarantined file, a damaged application-local copy, or a broken packaged framework. Copying one file does not repair those conditions.

Avoid these substitutions:

• Do not copy an x64 DLL into a 32-bit application directory.
• Do not copy an x86 DLL into a 64-bit application directory.
• Do not rename vcruntime140_1.dll to vcruntime140.dll.
• Do not replace only one runtime file from another computer.
• Do not delete files from WindowsApps.
• Do not overwrite a signed runtime with an unknown build.

Microsoft supports application-local deployment as a developer choice, but locally deployed files do not receive central updates automatically. For ordinary users, the official Redistributable or the application’s own repair process is the safer path.

What to do when the installer says a newer version is already installed

That message generally means Microsoft’s installer found a newer compatible v14 package and will not replace it with an older one. It does not prove that the installed package is healthy.

Repair the installed architecture:

1. Open Settings > Apps > Installed apps.
2. Search for Visual C++.
3. Select Modify beside the x86 or x64 entry.
4. Select Repair.
5. Restart Windows.
6. Test the application.

If repair fails, download a fresh current installer from Microsoft and run it as administrator. Do not repeatedly install old Visual Studio 2015 packages unless the application vendor specifically requires that legacy package or the operating system is outside the current package’s supported range.

Installed v14 runtime information is recorded in registry locations under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x86

On 64-bit Windows, the x86 information may also appear under:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86

Use these locations for diagnosis only. Do not edit or delete the entries to force an installer to run.

Follow the path shown in the error

The path in the message often tells you which repair applies.

C:\Windows\System32\vcruntime140.dll

This usually points to the centrally deployed native runtime. Repair the x64 or ARM64 package as appropriate. Remember that System32 on 64-bit Windows is associated with native system-architecture files.

C:\Windows\SysWOW64\vcruntime140.dll

This usually points to the centrally deployed x86 runtime on 64-bit Windows. Repair or install the x86 package.

The application’s installation directory

A local copy may be missing, damaged, or stale. Repair or reinstall the application, or verify its files through the game launcher.

C:\Program Files\WindowsApps\Microsoft.VCLibs...

Treat this as a packaged framework problem. Update Microsoft Store applications, use the application’s Repair or Reset controls, and install pending Windows updates. Do not edit the protected folder.

A path under %LOCALAPPDATA% or %APPDATA%

The application may be installed per user. Repair its per-user installation, test another Windows account, and reinstall the application if necessary.

Frequently asked questions

Is vcruntime140.dll a Windows file or a Visual Studio file?

It is a Microsoft Visual C/C++ runtime library. It can be installed centrally by the Visual C++ Redistributable or locally beside an application. Its presence in System32 or SysWOW64 does not prove that it was part of the base Windows installation.

Do I need Visual Studio 2015?

Usually not. You need the Microsoft Visual C++ Redistributable, not the full Visual Studio development environment. The current compatible v14 Redistributable supports applications built with the relevant Visual C++ toolsets.

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

The application architecture controls the DLL architecture. A 32-bit process cannot load a 64-bit runtime DLL, even when the operating system itself is 64-bit.

Should I install both x86 and x64?

On 64-bit Windows, install both when you are unsure which program is failing or when both 32-bit and 64-bit applications report errors. On 32-bit Windows, the x86 package is the relevant choice.

What is the difference between vcruntime140.dll and vcruntime140_1.dll?

They are separate components in the Visual C++ runtime family. A program requesting vcruntime140_1.dll needs that component, not a renamed copy of vcruntime140.dll. Repair the appropriate Redistributable and the affected application.

Does 0xc000007b prove that vcruntime140.dll is the problem?

No. That error can involve architecture mismatches, corrupted dependencies, or other DLLs. Check whether the program is 32-bit or 64-bit, install the matching runtime, and repair the application.

Can Windows Features install this runtime?

Normally no. To check, press Win+R, type optionalfeatures, and press Enter. The Windows Features dialog is not the normal location for the Visual C++ v14 Redistributable. Do not enable unrelated features as a substitute for installing the Microsoft package.

Should I run regsvr32?

No. vcruntime140.dll is not a COM registration server. Use the Visual C++ Redistributable installer.

What if only one application fails?

Repair or reinstall that application after repairing the Redistributable. A private copy beside the application may be overriding a healthy system copy.

What if many applications fail?

Repair both relevant Visual C++ architectures, install pending Windows updates, then run DISM followed by SFC. If the problem began after a recent system change, consider System Restore.

Did a disk cleanup cause the error?

Do not assume that a normal Windows cleanup removed the runtime. A third-party cleanup utility may have removed an application-local file or installer cache, but the cause must be checked. Repair the application and Redistributable rather than restoring a loose DLL.

What information should I provide when asking for more help?

Include the exact error text, application name, complete path shown in the message, Windows system type, whether x86 or x64 was installed, and whether one application or several are affected. Also mention whether the issue began after an update, antivirus detection, application reinstall, cleanup utility, or driver installation.

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.