How to Fix Missing Runtime Libraries in Windows 11 [2025 Guide]
8 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Runtime libraries are essential code files (usually DLLs) that many Windows 11 programs need to run. Most apps rely on Microsoft Visual C++ Redistributables to function. If the right version isn’t installed, the program may fail to launch and show a missing DLL error.
Windows 11 doesn’t always include these libraries by default. On clean installs, apps may not find the runtime files they need. Some developers even advise users to manually install the correct Visual C++ package, like the 2015–2022 redistributable.
In this guide, we’ll explain common causes and symptoms of missing runtime libraries in Windows 11 and give step-by-step fixes (with easy instructions) so even beginners can resolve these errors.
Common causes of missing runtime libraries
Runtime errors often happen because Windows or the applications are missing needed files. Common causes include:
- Missing or corrupted files: DLLs like MSVCP140.dll or vcruntime140.dll aren’t installed or have become damaged.
- Wrong version installed: The app may require a specific version (or 32-bit vs 64-bit) of the Visual C++ runtime that isn’t present.
- Broken installations: Failed installs, registry issues, or Windows updates can leave runtimes incomplete or unusable.
- Outdated system: Missing system updates can lead to incompatibility with newer software or runtime requirements.
- Conflicts or bugs: In rare cases, the app itself or another program can interfere with runtime detection.
In summary, missing runtime errors usually mean Windows lacks some needed library files (especially Visual C++ libraries). It could be because the app didn’t install them, they got corrupted, or Windows hasn’t been updated to include them.
Step-by-step solutions to fix missing runtime libraries in Windows 11
Below are practical steps to fix missing runtime libraries. You can try them in order until the problem is resolved. Each step includes simple instructions:
1. Install or repair Visual C++ Redistributables
- Open Control Panel and go to Programs and Features (or Settings → Apps in Windows 11). Look for any entries named Microsoft Visual C++ Redistributable (different years, like 2012, 2013, 2015–2022, etc.).
- For each one, try clicking Modify (or double-click) and choose Repair. This fixes corrupt files in that runtime. If that’s not available or doesn’t work:
- Uninstall all versions of the Visual C++ runtimes listed. Then reboot.
- Go to the Microsoft Visual C++ Downloads page (as linked by Microsoft). Download the latest Visual C++ redistributable (for example, “Visual C++ 2015-2022”) in both x86 and x64 versions (download links provided there). Run each installer to install fresh copies of the runtime libraries.
- If you saw a specific DLL missing (e.g. vcruntime140.dll), make sure you match the Visual Studio version (e.g. Visual C++ 2015 or 2019) to that file. In most cases, installing the latest “Microsoft Visual C++ Redistributable (2015-2022)” will cover it. This process ensures the correct runtime libraries are present.
2. Run System File Checker (SFC)
Windows has a built-in tool to fix corrupted system files. To use it:
- Click Start, type cmd, right-click on “Command Prompt,” and choose Run as administrator. In the command window, type:
sfc /scannow
and press Enter. This scans Windows system files (including some runtime DLLs) and automatically repairs any issues.
It may take a few minutes. When it finishes, reboot and check if the error is gone. This can restore missing or damaged libraries that are part of Windows. It should be noted that running sfc /scannow will automatically repair any corrupted Windows system files, including the missing runtime files.
3. Use DISM to repair the Windows image
If System File Checker (SFC) didn’t fix it, try the Deployment Image Servicing and Management tool:
- Open Command Prompt as an administrator again.
- Run these commands one by one (wait for each to complete):
DISM
/Online
/Cleanup-Image
/RestoreHealth
. - After it completes (it may take several minutes), reboot. DISM will check the Windows image for corruption and replace bad files from Windows Update. This can fix deeper issues that SFC can’t. The above command will check for system corruption and automatically repair any issues it finds.
4. Run Windows Update
Missing libraries can sometimes be fixed by installing the latest Windows updates, which may include updated runtimes. To update:
- Open Settings → Windows Update and click Check for updates.
- Install any available updates, then reboot. Keeping Windows current ensures you have the newest system files and libraries. In particular, Microsoft often delivers updated Visual C++ runtime patches via Windows Update.
5. Update graphics and other drivers (for games/apps)
If the error happens with a game or graphics-heavy app, updating your graphics driver can help. Outdated GPU drivers sometimes conflict with C++ runtimes.
First, Open Device Manager (right-click Start), expand Display Adapters, right-click your GPU, and choose Update driver → Search automatically. Install any found updates. Then reboot and try again.
6. Reinstall the affected program
If only one specific program is failing, try uninstalling and then reinstalling it. This ensures it installs any needed components properly. For many games and apps, the installer includes prerequisites (Visual C++, DirectX, etc.). After uninstalling, reboot, then reinstall the program. Also, temporarily disable antivirus during install in case it blocks runtime files. DiskGenius suggests that reinstalling the app can fix missing-file errors.
7. Other checks
- If an error names a specific file (e.g. api-ms-win-crt-runtime-l1-1-0.dll), sometimes installing the Universal C Runtime Update or the Visual C++ 2015-2019 Redistributable fixes it. Microsoft’s site has specific updates for older OS versions if needed.
- Try launching the program as Administrator (right-click → Run as administrator). Some apps need higher privileges to access certain libraries.
- In rare cases, use the System Restore utility to roll Windows back to a point before the errors started (if such a point exists).
By following the above steps – repairing/reinstalling runtimes, scanning for corrupt files, and updating Windows – you should replace the missing libraries and allow programs to run again. Many users find that simply installing the latest Visual C++ Redistributables (step 1) fixes the missing DLL errors immediately.
Identifying missing libraries (symptoms and error messages)
When a runtime library is missing, you’ll typically see an error when opening the program. Common symptoms include:
- An error pop-up like “MSVCP.dll is missing” or “VCRUNTIME.dll not found”. The exact filename (e.g. MSVCP140.dll, MSVCR120.dll, etc.) tells you which runtime component is missing. For example:
“The program can’t start because MSVCP120.dll is missing from your computer.” - A message “The application was unable to start correctly (0xc000007b)”. This can also indicate a missing or mismatched runtime library.
- Errors about “side-by-side configuration” or a manifest failure. This often happens with .NET or C++ apps when their runtime dependencies aren’t installed.
- The program simply refuses to open or crashes immediately with no obvious message. Often, the Event Viewer or error log will mention a missing DLL or Visual C++ runtime.
- Sometimes, you might see “Visual C++ Runtime Library” errors in the taskbar when a program crashes (usually saying it needs a specific version of the runtime).
To pinpoint the issue, note the exact error text. If it names a DLL (like MSVCP140.dll), you know which Visual C++ redistributable to install. If it’s the 0xc000007b error, try checking your app’s bitness (32/64-bit) and whether the corresponding runtimes are installed.
Also check in Control Panel → Programs & Features for entries like “Microsoft Visual C++ 2015 Redistributable” – missing ones point to what needs installing.
Prevention tips
To avoid missing runtime errors in the future, keep these practices in mind:
- Keep Windows updated: Regularly run Windows Update so that system files and runtimes stay current.
- Install needed runtimes during setup: When installing new software or games, ensure you also install any prompts for “redistributables” or prerequisites. Many modern installers will do this automatically, but if not, manually install the Visual C++ packages they require.
- Use reputable sources: Download software only from trusted websites. Corrupt downloads can lead to missing or bad runtime files.
- Maintain your system: Run occasional scans like sfc /scannow and DISM /RestoreHealth as part of routine maintenance to catch file corruption early.
- Avoid deleting DLLs: Don’t delete or move DLLs from the Windows folder. If cleanup is needed, use official uninstallers or tools rather than manual file deletion.
- Balance bitness: On a 64-bit Windows 11, install both x64 and x86 redistributables if you run 32-bit applications, to prevent architecture mismatch errors.
By keeping your system clean, updated, and having the correct redistributables installed, you greatly reduce the chance of runtime library errors on Windows 11.
Conclusion
Missing runtime libraries in Windows 11 often cause frustrating “cannot start” errors, but they have straightforward fixes. In most cases, simply installing or repairing the Visual C++ Redistributable packages and running Windows repair tools will resolve the issue.
The key is to identify the missing component (often by its DLL name) and make sure the matching runtime package is present. Following the steps above – repairing runtimes, scanning system files, updating Windows, and reinstalling any problematic apps – will restore the needed libraries and allow your programs to run normally.
Once everything is updated and correct, you should be able to use Windows 11 without those startup errors.
User forum
0 messages