⏱ 8 min read  ·  ✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

When a game says a DLL such as VCRUNTIME140.dll, MSVCP140.dll or d3dx9_43.dll is missing, the fix is almost always to install the correct Microsoft runtime package, not to download the single file from a random site. VCRUNTIME and MSVCP errors point to the Microsoft Visual C++ Redistributable, while d3dx, xinput and d3dcompiler errors point to the legacy DirectX runtime components.

This guide explains how to identify which runtime your game wants, the order of fixes that solves most cases, and what to avoid. It applies to Windows 10 and Windows 11 as they work in 2026, but package names and menu paths can change, so confirm details against Microsoft’s current documentation and your game launcher’s help pages before you act.

What These Errors Actually Mean

A DLL is a shared code library that many programs load at run time. Games built with Microsoft Visual Studio depend on the Visual C++ runtime, and many older games depend on pieces of DirectX that Windows does not install by default. When the library is absent, damaged or the wrong version, the game fails at launch with a message naming the missing file.

Visual C++ runtime errors

Files beginning with VCRUNTIME, MSVCP or MSVCR belong to the Microsoft Visual C++ Redistributable. VCRUNTIME140.dll, VCRUNTIME140_1.dll and MSVCP140.dll belong to the current 14.x family, which is a single shared package covering several Visual Studio releases. Files such as MSVCR100.dll or MSVCR120.dll belong to older, separate packages.

DirectX runtime errors

Windows includes DirectX 12 and the core DirectX 11 and 9 components, but it does not include every legacy helper library. Files such as d3dx9_43.dll, d3dx10_43.dll, xinput1_3.dll and d3dcompiler_43.dll come from the older DirectX End-User Runtime, which some games still need.

System and graphics errors

Errors naming api-ms-win-crt files point to the Universal C Runtime, which is delivered through Windows Update. Errors naming d3d12.dll or dxgi.dll usually point to a Windows or graphics driver problem rather than a missing download.

Match the Error to the Likely Fix

Missing file or messageLikely causeFirst fix to try
VCRUNTIME140.dll or MSVCP140.dllVisual C++ 14.x runtime missing or damagedInstall or repair the current Visual C++ Redistributable
VCRUNTIME140_1.dllRuntime is older than the game requiresInstall the latest 64-bit Redistributable
MSVCR100.dll or MSVCR120.dllOlder Visual C++ package missingInstall the matching older Redistributable, or the game’s bundled one
d3dx9_43.dll or xinput1_3.dllLegacy DirectX components missingRun the DirectX End-User Runtime installer
api-ms-win-crt-runtimeUniversal C Runtime not installedRun Windows Update and install pending updates
Error after update or crash on launchDamaged game files or conflicting softwareVerify game files and review antivirus quarantine

Step-by-Step Fix Order

Work through these steps in order and retest the game after each one. Stopping as soon as it launches keeps changes small and easier to undo.

  1. Restart the PC, then launch the game again. A pending update or locked file can cause a one-off error.
  2. Verify the game’s files in its launcher, which re-downloads missing or damaged files. Launchers usually offer this in the game’s properties or settings.
  3. Check the game folder for a redistributables folder, often named something like Redist or CommonRedist, and run the installers inside it. These match what the developer expects.
  4. Download and install the current Microsoft Visual C++ Redistributable from Microsoft’s official site. Install both the 64-bit and 32-bit versions, since some games and launchers use the 32-bit one.
  5. If the message mentions d3dx, xinput or d3dcompiler, install the DirectX End-User Runtime from Microsoft’s official site.
  6. Run Windows Update and install pending updates, including optional graphics or component updates that match your hardware.
  7. Update the graphics driver from the GPU maker’s official site, then restart.

Repairing an existing Visual C++ install

If the runtime already shows in Installed apps, select it, choose Modify or Repair, and let the wizard finish. Repair replaces damaged files without losing other settings. If repair fails, uninstall that entry, restart, and reinstall from Microsoft’s current download.

Repairing Windows system files

If the error persists, open Command Prompt as administrator and run sfc /scannow. If it reports problems it cannot fix, run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc again. These tools repair protected Windows files using trusted sources and can take several minutes.

Special Cases Worth Knowing

Errors after a Windows or driver update

A game that worked yesterday and fails today often points to an update that replaced or changed a component. Restart first, then repair the Visual C++ entries in Installed apps and reinstall the graphics driver using the maker’s clean install option if one is offered. If the problem began right after a Windows update, check whether Microsoft or the game developer has acknowledged it, since a later patch may resolve it.

Mod managers, launchers and anti-cheat

Mod tools, overlays and anti-cheat services load their own libraries and can trigger missing-file messages that look like game errors. If a mod loader or overlay was recently added, disable it and relaunch the base game. Anti-cheat services usually have their own repair option in the launcher or in the game folder, and the game’s support page normally lists it.

Portable and copied game folders

A game copied from another PC, an external drive or an old backup does not carry the runtimes registered on the original machine. Run its bundled redistributable installers, or reinstall through the launcher so the correct packages are set up on the new system.

Safety Notes: What Not to Do

Websites offering single DLL downloads are a common source of malware and mismatched files. Even a legitimate-looking file may be the wrong version or architecture, and copying it into the Windows system folder can cause problems that are harder to diagnose than the original error.

  • Download runtimes only from Microsoft’s official pages or from your game launcher.
  • Do not copy DLL files into System32 or SysWOW64 by hand.
  • Do not disable all security software permanently to make a game launch.
  • Be cautious with cracked or modified game files, which often trigger these errors and may carry other risks.

If your antivirus quarantined a file, review its history before restoring anything. Restore only files you trust, and prefer reverifying the game through its launcher.

When Fixes Do Not Work

If the game still fails, narrow the cause. Look at the Windows Event Viewer under Windows Logs and Application for the crash entry, which often names the faulting module. Note whether the error appears only for one game or several, since several games failing at once suggests a runtime or Windows problem, while one game failing suggests a damaged install.

Also confirm architecture. A 64-bit game needs the 64-bit runtime, and Windows on ARM devices may need specific Redistributable versions. Check the game’s support page for the exact requirements, and keep your launcher and Windows build up to date.

Quick Checklist Before You Contact Support

  • Restarted the PC and relaunched the game.
  • Verified game files through the launcher.
  • Installed the current 64-bit and 32-bit Visual C++ Redistributable.
  • Installed the DirectX End-User Runtime if the error named d3dx or xinput.
  • Ran Windows Update and updated the graphics driver.
  • Ran sfc and DISM if system files may be damaged.
  • Noted the exact error text, game version and Windows version.

Reading the Error Message Carefully

The wording of the message often tells you more than the file name. A message that says the program cannot start because a file is missing usually means the library is absent. A message that says the application was unable to start correctly with a hexadecimal code points to a damaged or incompatible library, and a repair or reinstall of the runtime is the logical first move. If the message names a file inside the game’s own folder, verify the game files instead.

Common Mistakes

  • Downloading one DLL from an unofficial site instead of installing the runtime package.
  • Installing only the 64-bit Redistributable when the game or launcher needs the 32-bit one.
  • Skipping the game’s own redistributable folder, which contains the versions the developer expects.
  • Ignoring Windows Update, which delivers the Universal C Runtime and key system fixes.
  • Restoring quarantined files without checking whether they came from a trusted source.

Related guides

Frequently Asked Questions

Why does a new Windows install keep showing these errors?

A fresh Windows install does not include every runtime a game may need. Installing the Visual C++ Redistributable and, for older titles, the DirectX End-User Runtime usually solves it, and many launchers install the correct versions the first time you run a game.

Do I need to install every Visual C++ version?

Not always. Newer 14.x versions cover several Visual Studio releases, but older families such as 2010 or 2013 are separate packages. Install the ones your game asks for, or those listed in its redistributable folder.

Will installing these runtimes slow down my PC?

No. Runtimes are small libraries that sit on disk until a program loads them. Having several versions installed side by side is normal on gaming PCs.

Is it safe to use a DLL fixer tool?

It is better to avoid them. Tools that promise automatic DLL repair can bundle unwanted software or replace files with wrong versions. Official runtime installers, the launcher’s verify option and Windows repair tools are safer and more reliable.

Explore Our Guides & Free Tools