Dependencies · Troubleshooting guide

VCRUNTIME140.dll How to troubleshoot and fix it

For a missing VCRUNTIME140.dll, check the Visual C++ v14 runtime, application architecture and launcher files. Follow this installation, repair and verification sequence.

The short answer

Check the Visual C++ v14 runtime before replacing a DLL.

Install or repair Microsoft's v14 runtime for the application's architecture, then restart and test. The 120-series files from VC++ 2013 do not replace VCRUNTIME140.dll.

Common symptoms

Match the complete error before following the checks:

  • Launching reports that VCRUNTIME140.dll cannot be found.
  • Reinstalling the application still leaves it exiting before loading.
  • If only one application fails, check its local dependencies and quarantine history, restoring trusted files through the original installer.
AirPrinter.exe reports VCRUNTIME140.dll was not found
Error screenshot source: Flyingbee SupportThe source interface language is preserved; application names and Windows appearance may differ.

What causes VCRUNTIME140.dll

The same message can have different causes. Check Windows version, application architecture and logs.

Possible causeDetails
Required runtime absentSelect a Microsoft v14 package that supports your Windows version and meets the application's version requirement. Match the application architecture and choose Repair if installed. Do not remove all runtimes to install an older package.
Package architecture mismatchAn x64 runtime does not replace the x86 components needed by a 32-bit application.
Damaged runtime or application filesIf only one application fails, check its local dependencies and quarantine history, restoring trusted files through the original installer.

Repair steps

Follow these 4 steps in order, starting with the simplest checks.

1

Identify the application architecture and Windows version

Difficulty: Easy5–10 min

Check the vendor's requirements for x86, x64 or ARM64. A 32-bit application on 64-bit Windows still needs the x86 runtime. Select packages for the application, not just the operating system.

Check after repair

You have recorded Windows version, application architecture and the exact missing filename.

2

Install or repair Visual C++ v14

Difficulty: Easy5–10 min

Select a Microsoft v14 package that supports your Windows version and meets the application's version requirement. Match the application architecture and choose Repair if installed. Do not remove all runtimes to install an older package.

Read Microsoft's official guidance
Check after repair

Setup finishes successfully. Restart if requested, then test. Record any setup error code.

3

Check versions and the loaded copy

Difficulty: Easy5–10 min

If only one application fails, check its local dependencies and quarantine history, restoring trusted files through the original installer.

Check after repair

No system DLLs were overwritten; vendor-supplied dependencies in the game folder were repaired through the original installer.

4

Verify application files and test again

Difficulty: Easy5–10 min

Verify files in the original game launcher or use the vendor's repair installer. Keep saves and settings, launch the same application through its original launcher and record any new error.

Check after repair

File verification completes and both launcher and application open. If the message changes, investigate the new filename.

Verify the fix

Verify with the same application and launch method that originally failed:

The original VCRUNTIME140.dll missing-file message no longer appears.The application reaches its main screen, not just its launcher.Close and relaunch to confirm the same failure does not recur.

Frequently asked questions

Can VC++ 2013 fix missing VCRUNTIME140.dll?

It does not replace v14. Identify the application's required runtime major version and architecture first.

Why is a dependency still missing after installing x64?

The launcher, plugins and main program can use different architectures. Check each against vendor requirements; 32-bit dependencies need the x86 package.

Can I copy a downloaded DLL into System32?

Use the complete Microsoft or application-vendor installer. A loose DLL can have the wrong architecture, version or origin and does not restore its dependencies. Do not overwrite system-directory files.

Need a hand? Explore Baomiao Repair Tool

Check system settings, game components and common issues for repair suggestions.

Get Baomiao Repair Tool
  • Safety first
  • No game-data changes
  • For popular games on Windows