sodcalculator

10 Tech How-To

Fix Failed to Load DLL Error in Windows

Guide 10-38150 · Updated · Step by step

This guide walks you through the most common causes of “The code execution cannot proceed because [file].dll was not found” or similar “failed to load DLL” errors in Windows 10 and 11. You’ll learn how to identify the missing file, restore it safely, and prevent the error from coming back. No advanced tools are required, but you will need administrator access to your PC.

What You’ll Need

  • A Windows account with administrator privileges
  • Internet connection (to download official components if needed)
  • The name of the DLL file mentioned in the error message
  • Optional: a USB drive to back up important files before major changes

Step-by-Step

  1. Write down the exact DLL name and the program that triggered the error. The error dialog usually shows the file name (e.g., msvcp140.dll, vcruntime140.dll, d3dx9_43.dll). Note which app or game you were launching when it appeared.
  2. Restart your computer. A simple reboot clears temporary file locks and stale processes that sometimes cause DLL loading failures. Try launching the program again before doing anything else.
  3. Run the program as administrator. Right-click the app’s shortcut and select “Run as administrator.” Some DLLs need elevated permissions to load, especially if they access system folders. If this fixes it, you can set the app to always run as admin via Properties → Compatibility → “Run this program as an administrator.”
  4. Check if the DLL is a known system file. Search the web for the exact filename. If it’s part of Microsoft Visual C++ Redistributable, .NET Framework, or DirectX, skip to step 6. If it’s a standalone DLL from a specific program, go to step 5.
  5. Reinstall the program that shows the error. Uninstall the application from Settings → Apps → Installed apps, then download the latest version from the official website and install it. This replaces any missing or corrupted DLLs that came with the app.
  6. Install or repair the Microsoft Visual C++ Redistributable packages. Many DLL errors (msvcp*.dll, vcruntime*.dll) come from missing or outdated C++ runtime libraries. Download the latest “Visual C++ Redistributable for Visual Studio” from Microsoft’s official site (both x86 and x64 versions). Run the installer and choose “Repair” if you already have a version installed.
  7. Update DirectX and .NET Framework. For gaming-related DLLs like d3dx9_43.dll or xinput1_3.dll, install the latest DirectX End-User Runtime from Microsoft. For System.*.dll errors, install the latest .NET Framework (4.8 or newer) from Microsoft’s download page.
  8. Run the System File Checker (SFC) and DISM. Open Command Prompt as administrator (type “cmd” in Start, right-click, “Run as administrator”). Run sfc /scannow and wait for it to finish. Then run DISM /Online /Cleanup-Image /RestoreHealth. Restart after both complete.
  9. Check for Windows updates. Go to Settings → Windows Update → Check for updates. Install all pending updates, including optional ones, then restart. Updates often include DLL fixes for system components.
  10. Scan for malware. Run a full scan with Windows Security (or a reputable third-party antivirus). Malware can delete or replace DLL files. A clean scan removes the cause and may restore the file.
  11. Restore the DLL from the Recycle Bin or a backup. If you recently deleted a file or moved a folder, check the Recycle Bin. If you have a system backup or restore point, you can restore the original DLL from there (see Troubleshooting).
  12. If the DLL is from a third-party app, copy it from a working installation. Only do this if you have another PC with the same program and Windows version. Copy the DLL from the other machine’s program folder to the same location on your PC. Do not copy system DLLs this way.

Common Mistakes

  • Downloading DLLs from random websites. These files are often outdated, infected, or incompatible. Always get DLLs from official Microsoft installers or the original program’s installer.
  • Placing a 32-bit DLL into a 64-bit system folder. A 32-bit program needs its DLLs in C:\Windows\SysWOW64, while a 64-bit program uses C:\Windows\System32. Mixing them causes errors.
  • Copying a DLL from a different Windows version. A DLL from Windows 10 may not work on Windows 11, and vice versa. Always match the version.
  • Skipping the restart after installing updates. Many DLL fixes require a reboot to take effect.
  • Ignoring the “0x0000007e” or “0xc0000135” codes. These indicate a missing dependency, not the DLL itself. You need to install the parent component (like Visual C++ or .NET).

Tips

  • Always install both 32-bit and 64-bit versions of runtime libraries. Even if your Windows is 64-bit, many programs are 32-bit and need the x86 runtime.
  • Use the “Repair” option in the original installer. For many programs, running the installer again and choosing “Repair” is faster than uninstall/reinstall.
  • Keep a list of installed programs. If the error appears after an update, you can quickly identify which program changed.
  • Create a system restore point before making major changes. This lets you roll back if something goes wrong.
  • Update your graphics drivers. Some DLL errors (like d3dx9) are resolved by updating GPU drivers from the manufacturer’s website.

Troubleshooting

  • If the error still appears after reinstalling the program and runtimes: Try a clean boot. Press Win+R, type msconfig, go to the “Services” tab, check “Hide all Microsoft services,” click “Disable all,” then restart. If the error disappears, a third-party service is interfering. Re-enable services one by one to find the culprit.
  • If SFC reports corrupted files but cannot fix them: Run DISM first, then SFC again. If that fails, try sfc /scannow in Safe Mode (hold Shift while clicking Restart, then Troubleshoot → Advanced → Startup Settings → Restart → press 4).
  • If you have a restore point from before the error: Go to Control Panel → Recovery → Open System Restore. Choose a point before the issue started. This restores DLLs without affecting your personal files.
  • If the DLL is part of a game and it still fails: Verify the game’s files through its launcher (Steam, Epic, etc.) or reinstall the game. Also check that your game is updated to the latest patch.
  • If the error happens on startup for many programs: It may be a system-wide issue. Run sfc /scannow, then check for Windows updates. If it persists, consider a Windows repair install using the Media Creation Tool (keeps your files).
  • If you suspect malware: Run a full offline scan with Windows Defender (Settings → Privacy & Security → Windows Security → Virus & threat protection → Scan options → Microsoft Defender Offline scan).

Frequently Asked Questions

Is it safe to download DLL files from websites?

No. Most DLL download sites are not trustworthy and can contain malware or outdated versions. Always use official installers from Microsoft or the software vendor.

Why does the error say “not found” even though the DLL is in the folder?

The DLL might be a 32-bit version in a 64-bit program folder, or a required dependency (like a C++ runtime) is missing. Check the program’s architecture and install the correct runtime.

Can I just copy a DLL from another PC?

Only if the other PC has the same Windows version, service pack, and the same program version. Even then, it’s better to reinstall the program or runtime.

What does “0xc000007b” mean?

This error usually means a 32-bit program is trying to load a 64-bit DLL or vice versa. Install the correct version of the Visual C++ Redistributable (x86 for 32-bit apps, x64 for 64-bit apps).

Will reinstalling Windows fix the DLL error?

Yes, a clean install will fix almost any DLL issue, but it’s a last resort. Try the steps above first, as they are less disruptive.

How do I know if a DLL is a system file?

Search for the filename online. If it’s in the C:\Windows\System32 folder, it’s likely a system file. Never delete or replace system DLLs manually.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →