sodcalculator

10 Tech How-To

Error Version DLL Not Found Windows: Fixes

Guide 10-51182 · Updated · Step by step

If you see an error saying a DLL file was not found or a version of a DLL is missing on Windows, it usually means a program you launched is looking for a specific dynamic link library that isn’t installed or is the wrong version. The fix is to reinstall the program, install the required Microsoft Visual C++ Redistributable, or run the System File Checker, depending on which DLL is named in the error.

What This Error Actually Means

Windows programs don’t contain every piece of code they need. Instead, they call on shared libraries called DLLs (Dynamic Link Libraries). When a program starts, Windows looks for the DLLs it needs in a specific order: the program’s own folder, the system folders (System32 or SysWOW64), and then the Windows directory. If the right DLL isn’t in any of those places, or if the version present is older or newer than what the program expects, you get an error like “The code execution cannot proceed because X.dll was not found” or “A required DLL version is missing.”

These errors became much more common after Windows 10 and 11 because many older programs were built to expect DLLs that are no longer included by default. The most frequent culprits are the Visual C++ Redistributable packages, which contain runtime components for programs written in C++.

Common DLL Names and Their Causes

  • VCRUNTIME140.dll, MSVCP140.dll, VCRUNTIME140_1.dll – These come from the Microsoft Visual C++ Redistributable 2015–2022. Games and productivity apps often need them. If they’re missing, install the latest x64 and x86 versions.
  • D3DCOMPILER_47.dll, XINPUT1_3.dll, D3DX9_43.dll – DirectX runtime files. Older games need DirectX 9 even on Windows 11. Installing the DirectX End-User Runtime fixes this.
  • MSVCR100.dll, MSVCR120.dll – Visual C++ 2010 and 2013 runtimes. Each major version has its own set.
  • MFC140.dll – Microsoft Foundation Classes library, part of the same Visual C++ redistributable as above.
  • python3.dll or similar – Some apps bundle their own Python runtime, but if they rely on a system-wide install, a missing or mismatched version causes this error.

How to Fix It: Step by Step

  1. Reinstall the program that shows the error. Uninstall it completely, restart your PC, then download the latest version from the official source. This often replaces any missing DLLs that came with the app.
  2. Install the Visual C++ Redistributables. Go to Microsoft’s official download page and get the latest “Visual C++ Redistributable for Visual Studio 2015-2022” package. Install both the x64 and x86 versions, even if your Windows is 64-bit. Many 32-bit programs need the x86 files.
  3. Run the System File Checker. Open Command Prompt as administrator and type sfc /scannow. This scans protected system files and replaces corrupted ones. It can take 10–15 minutes.
  4. Check for Windows Updates. Some DLL errors are fixed by cumulative updates. Go to Settings > Windows Update and install any pending updates.
  5. If the error names a DirectX file, install the DirectX End-User Runtime. This is a legacy package from Microsoft that installs all older DirectX 9.0c files. It’s safe and doesn’t overwrite newer versions.
  6. If the error names a file in the program’s own folder, reinstall the program and make sure your antivirus isn’t quarantining the file. Some security tools flag DLLs as false positives.

Why You Should Never Download DLLs from Random Sites

A common search result for “dll not found” leads to sites that offer a direct download of the missing DLL file. Avoid these. They are not official, and they often contain malware or adware. Even if the file is clean, it may be the wrong version or architecture (32-bit vs 64-bit), which can cause a different error. The only safe sources are the original software installer, Microsoft’s official redistributables, or the Windows component store. If a site asks you to pay for a DLL download, that’s a scam.

32-bit vs 64-bit: Why Version Matters

Windows has two system folders for DLLs: System32 (for 64-bit DLLs on 64-bit Windows) and SysWOW64 (for 32-bit DLLs). When a 32-bit program runs on 64-bit Windows, it looks in SysWOW64. If you copy a 64-bit DLL into SysWOW64, the program will fail with a “bad image” or “version” error. The reverse also fails. So when you install a redistributable, always install both the x64 and x86 versions to cover all programs.

What to Do If the Error Persists

If you’ve tried the steps above and the error still appears, check the exact DLL name in the error message. Search for that name plus the name of the program. Often, the program’s official forums or support pages have a specific fix. You can also use the Dependency Walker tool (for older programs) or the built-in Process Monitor to see which DLL fails to load, but these are advanced tools. Another option is to uninstall the program completely, delete its leftover folder in Program Files or AppData, and reinstall it fresh. If the error happens with a game, update your graphics drivers – some games need newer GPU drivers to provide certain DLLs.

Frequently Asked Questions

Can I just copy a DLL from another computer?

Technically yes, but it’s risky. The DLL must be the same version and architecture, and it must not depend on other DLLs that are missing on your system. Copying a system DLL can also trigger Windows Resource Protection. It’s better to reinstall the program or the redistributable that provides the DLL.

Why does a 64-bit program need a 32-bit DLL?

It usually doesn’t. But some installers place both versions, and a 64-bit program might call a helper tool that is 32-bit. That helper tool needs the 32-bit runtime. That’s why installing both architectures of the Visual C++ Redistributable is recommended.

What is the difference between “not found” and “version missing”?

“Not found” means Windows can’t locate the DLL at all. “Version missing” or “version is incorrect” means a DLL with that name exists, but it’s an older or newer version than the program expects. The fixes are the same: reinstall the program or update the runtime package.

Will System Restore fix this error?

Sometimes, if the error started after a recent change (like uninstalling a program or a Windows update), restoring your system to a point before that change can fix it. But if the DLL is missing because it was never installed, System Restore won’t help.

Does this error mean my Windows is broken?

No. It’s almost always a per-program issue. The rest of your system is fine. The error only affects the program that can’t start.

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 →