Get it from the official source
We don't host files. These links take you straight to the genuine, safe installer on the developer's website.
A DLL (Dynamic Link Library) is a shared bundle of code that many programs use instead of each carrying its own copy. When Windows tells you a specific DLL is missing — names like MSVCP140.dll, VCRUNTIME140.dll, or d3dx9_43.dll are classic examples — it means a program tried to load that shared file and couldn't find it. The application then refuses to start.
It is tempting to search the file name, land on a 'DLL download' site, and grab the single file you are missing. Resist that urge. These sites are one of the oldest and most reliable sources of malware on the internet, and even when the DLL is clean it is often the wrong version, which only causes new errors.
The correct and safe fix is almost always to reinstall the official software package that provides the DLL, usually a Microsoft runtime. This guide explains how to identify the missing file and restore it the right way.
Helpful tools
Visual C++ Redistributable
Provides MSVCP and VCRUNTIME DLLs many programs need
Visit official site ↗
DirectX End-User Runtime
Restores d3dx9 and xinput DLLs required by many games
Visit official site ↗
Dependencies (lucasg)
Open-source utility that lists every DLL an executable loads
Visit official site ↗
Process Monitor (Sysinternals)
Microsoft tool that shows exactly which DLL load is failing
Visit official site ↗
Step-by-step fix
-
1
Read the error carefully and note the exact DLL name and the application that failed.
-
2
Identify the owning package: MSVCP/VCRUNTIME/MSVCR means Visual C++; d3dx9/xinput means DirectX; unusual names mean the app itself.
-
3
For Visual C++ errors, download and install the latest x86 and x64 redistributables directly from Microsoft.
-
4
For DirectX errors, run Microsoft's DirectX End-User Runtime Web Installer to restore legacy DirectX files.
-
5
Open an elevated Command Prompt and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and reboot.
-
6
Check your antivirus quarantine in case the DLL was removed as a false positive, and restore it if appropriate.
-
7
If the DLL belongs to a specific program, uninstall and reinstall that application from its official site.
-
8
Never download loose DLL files from third-party 'DLL download' sites, as they are a common malware source.
Why You Should Never Use DLL Download Sites
Standalone DLL download sites are notorious for distributing malware-laced files, bundling adware, or serving outdated versions that don't match what your program expects. Because a DLL runs with the same privileges as the program loading it, a malicious one can do serious damage.
Beyond the security risk, dropping a random DLL into your system folder masks the real problem. The file belongs to a software package, and installing it loose means it won't be updated, repaired, or registered correctly. Reinstalling the parent package is both safer and more reliable.
Identify Which Package Owns the DLL
The DLL's name usually reveals its origin. Files starting with MSVCP, VCRUNTIME, or MSVCR belong to the Visual C++ Redistributables. Files like d3dx9_xx.dll or xinput come from DirectX. Anything with 'mfc' is also Visual C++. Once you know the owner, you simply reinstall that package from Microsoft.
- MSVCP140.dll, VCRUNTIME140.dll — Visual C++ Redistributable
- d3dx9_43.dll, xinput1_3.dll — DirectX End-User Runtime
- App-specific DLLs — Reinstall the application itself
Reinstall the Official Runtime
For Visual C++ errors, download the latest supported redistributables directly from Microsoft and install both the x86 and x64 versions. For DirectX errors, run the DirectX End-User Runtime Web Installer, which restores the older DirectX 9 files that modern games still rely on. These packages are free, official, and clean.
If the runtime is already installed but the error persists, uninstall it from Settings > Apps and reinstall a fresh copy to clear any corruption.
Repair Windows System Files
If the missing DLL is a core Windows file rather than a runtime component, use the built-in repair tools. Open an elevated Command Prompt and run sfc /scannow to restore protected system files, then DISM /Online /Cleanup-Image /RestoreHealth to repair the component store. Reboot and test again.
These commands pull clean copies from Windows itself, so they are far safer than any external file source.
When the DLL Belongs to the App Itself
If the missing DLL has an unusual, application-specific name, it almost certainly shipped with the program rather than with Windows. In that case, reinstall the application from its official source. An antivirus may also have quarantined the DLL as a false positive, so check your security software's quarantine before reinstalling.
Frequently asked questions
Questions & answers
No questions yet — be the first to ask!
Ask a question
Please sign in with your email to ask a question.
Comments (0)
No comments yet. Share your experience!
Leave a comment
Please sign in with your email to comment.