How to Fix Windows Error 0xC0000135 (DLL Not Found)

By ErrorFix · Updated October 26, 2026 · 7 min read

What error 0xC0000135 means

The full message usually reads something like this: the application failed to start because a particular DLL was not found, and reinstalling the program may fix the problem. Behind the scenes, Windows was assembling your program from small shared library files called DLLs. Every program lists the libraries it depends on, and Windows loads each one before the program itself runs. If even one of those files cannot be found in the program folder, System32, or SysWOW64, Windows cancels the launch and reports error 0xC0000135.

You will see this error most often with PC games, older desktop software, and programs that were copied from another computer instead of installed properly. A copied program folder does not register its runtimes, so the DLLs it expects are simply not there. It also appears after a careless cleanup tool deletes shared libraries, after an antivirus program quarantines a legitimate DLL, or after a Windows update or reinstall leaves a program pointing at libraries that no longer exist. The good news is that the fix is usually straightforward: restore the missing runtime package, and the program starts again. Your documents and personal files are not involved, and none of the steps below touch them.

Common causes

• Missing Visual C++ Redistributable: the program was built with Visual Studio and needs the matching runtime libraries, most commonly MSVCP140.dll or VCRUNTIME140.dll, which were never installed or were removed.
• Missing or damaged .NET Framework component: programs built on .NET fail at startup when the framework version they target is turned off, damaged, or absent after a Windows reinstall.
• Program copied instead of installed: moving a program folder between PCs skips the installer steps that place its DLLs and runtimes in the right system folders.
• DLL deleted by a cleanup tool or antivirus quarantine: aggressive cleaners and false-positive antivirus detections sometimes remove or lock away a shared library that several programs depend on.
• Damaged Windows system files: disk errors, interrupted updates, or malware can corrupt or remove system DLLs, so Windows reports them as missing even though the program itself is intact.

How to fix error 0xC0000135 — step by step

Work through these fixes in order. Step 2 resolves the majority of cases, so do not skip it even if the missing file name looks unfamiliar.

1. Read the error message and note the missing DLL name. The full message usually names the file, for example MSVCP140.dll or VCRUNTIME140.dll was not found. Write down that exact file name before you close the message, because it tells you which runtime package to reinstall in the next step. If no file name is shown, open Event Viewer, go to Windows Logs, then Application, and look for the most recent error entry for the program, which usually names the missing component.
2. Reinstall the Microsoft Visual C++ Redistributables. Open Settings, go to Apps, then Installed apps, and uninstall every Microsoft Visual C++ Redistributable entry. Then download the latest supported Visual C++ Redistributable packages from the official Microsoft site and install both the x86 and x64 versions, even on a 64-bit PC, because many programs still use 32-bit libraries. Restart the PC and try the program again.
3. Repair or reinstall the .NET Framework and DirectX. Some programs fail with 0xC0000135 because they need a .NET Framework version that is missing or damaged. Open Control Panel, go to Programs and Features, then Turn Windows features on or off, and make sure .NET Framework 3.5 and .NET Framework 4.8 Advanced Services are checked. If the program is a game, also run the DirectX End-User Runtime installer from Microsoft, which restores older DirectX libraries that newer Windows versions no longer include.
4. Run SFC and DISM to repair Windows system files. Right-click Start and choose Terminal (Admin) or Command Prompt (Admin). Run sfc /scannow and wait for it to finish, then run DISM /Online /Cleanup-Image /RestoreHealth. These tools replace damaged or missing Windows system files, including DLLs in System32 and SysWOW64. Restart the PC when they complete and test the program again.
5. Reinstall the program that shows the error. Open Settings, go to Apps, then Installed apps, and uninstall the program that shows the error. Delete any leftover folder for it in Program Files or Program Files (x86) only if you are sure it belongs to that program, then download the latest installer from the official source, right-click it, choose Run as administrator, and reinstall. A fresh install restores the program's own DLLs and re-registers the runtimes it needs.
6. Scan for malware and check for a bad antivirus quarantine. Run a full scan with Windows Security, because some malware deletes or replaces DLL files, and a damaged file can be reported as missing. Also open your antivirus quarantine or protection history: security software sometimes quarantines a legitimate DLL after a false positive, and restoring that file fixes the program immediately. If the error started right after a Windows update, open Settings, go to Windows Update, then Update history, then Uninstall updates, and remove the most recent update as a test.

Did this fix it? Quick checklist

• The program launches without the 0xC0000135 popup
• The same program also opens after a full restart
• Other programs that use the same runtimes start normally
• Event Viewer shows no new application errors for the program

If one program still refuses to start, try installing it on a fresh Windows user account as a test — a damaged user profile can occasionally interfere with how libraries load. Also check whether the program ships its own DLLs in its installation folder: if a single file there is dated much older or newer than its neighbors, an old patch may have left a stale copy behind, and a clean reinstall (with the leftover folder removed first) is the reliable way to clear it.