Skip to main content
Back to all fixes
hard15 min

Diagnose & Replace Missing/Corrupt DLLs

When the error names a specific DLL, or when you suspect a DLL mismatch, use dependency analysis to find the exact culprit.

One-Click Script

Save as find-missing-dlls.bat, right-click → Run as Administrator.

@echo off
echo === Checking common missing DLLs ===
echo.
set "dlls=msvcp140.dll vcruntime140.dll vcruntime140_1.dll d3dx9_43.dll xinput1_3.dll msxml3.dll"
for %%d in (%dlls%) do (
  if exist "C:\Windows\System32\%%d" (
    echo [OK] %%d (x64)
  ) else (
    echo [MISSING] %%d (x64)
  )
  if exist "C:\Windows\SysWOW64\%%d" (
    echo [OK] %%d (x86)
  ) else (
    echo [MISSING] %%d (x86)
  )
)
echo.
echo If any are MISSING, run the corresponding fix.
pause

Step-by-Step

  1. 1

    Download Dependencies (modern replacement for Dependency Walker) from GitHub: https://github.com/lucasg/Dependencies

    Dependencies (DLL Analyzer)Find exactly which DLL is missing
  2. 2

    Run DependenciesGui.exe as Administrator.

  3. 3

    File → Open → browse to your broken application's .exe file.

  4. 4

    Look for DLLs highlighted in RED or YELLOW. These are missing or have architecture mismatches (x64 app loading x86 DLL = red).

  5. 5

    For missing DLLs: do NOT download from random DLL sites. Instead:

  6. 6

    • If it's a game DLL (xinput1_3.dll, d3dx9_43.dll): reinstall DirectX (Fix #4).

  7. 7

    • If it's msvcp140/vcruntime140: reinstall VC++ Redist (Fix #2).

  8. 8

    • If it's ntdll/kernel32: run SFC (Fix #6).

  9. 9

    For architecture mismatch: ensure you installed BOTH x86 and x64 VC++ Redistributables. 64-bit Windows running 32-bit apps needs SysWOW64 DLLs.

How to Verify It Worked

  • Dependencies shows 0 red modules after fix.
  • The application launches without error.

Still Not Working?

The DLL issue may be caused by deeper system corruption. Run Fix #6 (SFC + DISM) followed by Fix #8 (Check Disk).