Fix 0xc0000142 Error: App Won’t Start

This guide walks you through fixing the “The application was unable to start correctly (0xc0000142)” error on Windows. This error typically appears when a program can’t initialize its graphical interface or a required system component, and it can affect both older and newer software. The fixes below are ordered from the quickest and safest to the more involved, so start at the top and work your way down.

What You’ll Need

Administrator access to the Windows user account (to install updates and run system tools).
Your Windows product key or Microsoft account credentials, in case a system file repair requires re-authentication.
A stable internet connection for downloading updates and reinstallers.

Step-by-Step

Restart your computer. This clears temporary memory glitches that can cause the error. Save any open work, then select Start > Power > Restart. After the restart, try launching the application again.
Run the program as an administrator. Right-click the application’s shortcut or executable file and choose Run as administrator. If it works, the issue is likely a permission problem. To make this permanent, right-click the shortcut, select Properties > Compatibility, check Run this program as an administrator, and click OK.
Run Windows Update. Open Settings > Windows Update and click Check for updates. Install all pending updates, including optional ones, then restart your PC. Missing system files or outdated graphics drivers are a common cause of error 0xc0000142.
Update your graphics drivers. Press Win + X and select Device Manager. Expand Display adapters, right-click your graphics card, and choose Update driver > Search automatically for drivers. If no update is found, visit the manufacturer’s website (NVIDIA, AMD, or Intel) for the latest driver for your model.
Run the System File Checker (SFC). Open Command Prompt as administrator (search for “cmd”, right-click it, and select Run as administrator). Type sfc /scannow and press Enter. Wait for the scan to finish — this can take 10–20 minutes. If it finds and repairs corrupted files, restart and test the app.
Run DISM to repair the system image. If SFC doesn’t fix it, in the same Command Prompt window, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This can take up to 30 minutes. After it completes, run sfc /scannow again, then restart.
Reinstall the affected application. Uninstall the program via Settings > Apps > Installed apps, then download the latest version from the official website and install it. This replaces any corrupted program files.
Install the latest Visual C++ Redistributables. Many Windows apps depend on these runtime libraries. Download the “Visual C++ Redistributable for Visual Studio 2015-2022” package from Microsoft’s official site (both x86 and x64 versions), run both installers, and restart.
Check for .NET Framework issues. Open Settings > Apps > Optional features (or Programs and Features in older Windows), and ensure “.NET Framework 3.5” and “.NET Framework 4.8” are enabled. If not, enable them and restart.
Perform a Clean Boot. This starts Windows with only essential drivers and services, isolating conflicts. Press Win + R, type msconfig, and go to the Services tab. Check Hide all Microsoft services, then click Disable all. Go to the Startup tab and click Open Task Manager. Disable all startup items there. Restart and try the app. If it works, re-enable services one by one to find the culprit.
Run a malware scan. Use Windows Security (built-in) by going to Windows Security > Virus & threat protection > Scan options and selecting Full scan. Malware can corrupt system files and trigger this error.
Check the Windows Event Viewer for details. Press Win + X and select Event Viewer. Go to Windows Logs > Application, look for Error entries dated at the time the app failed, and read the “Faulting module” name. This often identifies the exact DLL causing the problem, which you can then search for a specific fix.

Common Mistakes

Skipping the restart. Many 0xc0000142 errors are transient and a simple reboot clears them. Don’t jump to complex fixes first.
Only running SFC without DISM. SFC can fail to repair files if the underlying system image is corrupted. Always run DISM first, then SFC again.
Installing only one Visual C++ version. Some apps need the x86 (32-bit) runtime even on 64-bit Windows. Install both x86 and x64 packages.
Forgetting to restart after driver or runtime updates. Changes don’t take effect until Windows restarts.
Assuming it’s always a system file issue. The error can also come from a specific app’s corrupted installation, so reinstalling the app is a valid early step, not a last resort.

Tips

Create a restore point before major changes. Search for “Create a restore point” in the Start menu, select your system drive, and click Create. This lets you roll back if a fix causes other problems.
Check the application’s official support forum. If the error appears only with one specific program (like a game or niche tool), the developer may have a known fix or a beta patch.
Use the “Program Compatibility Troubleshooter”. Right-click the app’s executable, choose Troubleshoot compatibility, and let Windows try recommended settings. This can fix issues with older software on newer Windows versions.
Keep your system clean. Regularly run Disk Cleanup and uninstall unused programs to reduce the chance of DLL conflicts.

Troubleshooting

If the error persists after trying all the steps above, consider the following:

Check if the error occurs with all applications or just one. If it’s only one app, the problem is almost certainly that app’s installation or its specific dependencies. Focus on reinstalling it and its required runtimes.
Look for a “Faulting module” in Event Viewer. If it names a file like d3d9.dll or msvcp140.dll, search for that file name plus “0xc0000142” to find targeted advice.
Try the app in a different user account. Create a new local user account (Settings > Accounts > Family & other users) and try running the app there. If it works, your main user profile is corrupted — you may need to migrate your files to the new account.
Use System Restore. If you have a restore point from before the error started, boot into Safe Mode (hold Shift while selecting Restart, then choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4) and run System Restore from there.
Repair Windows with an in-place upgrade. Download the Windows Media Creation Tool from Microsoft’s official site, run it, and choose “Upgrade this PC now”. This reinstalls Windows while keeping your files and apps. It’s a more thorough fix than SFC/DISM but less drastic than a full reset.
As a last resort, reset your PC. Go to Settings > System > Recovery > Reset this PC and choose “Keep my files”. This reinstalls Windows and removes apps, but preserves your personal documents and photos. Back up important data first.

Frequently Asked Questions

Q: What exactly causes error 0xc0000142?
A: It means Windows couldn’t initialize the application’s graphical interface. Common causes include corrupted system DLLs, missing Visual C++ runtimes, outdated graphics drivers, or a damaged application installation.

Q: Is this error dangerous or a sign of malware?
A: Not usually. It’s a software initialization failure, not a security warning. However, if it appears suddenly across many programs, a malware scan is a reasonable precaution.

Q: Will I lose my files if I run SFC or DISM?
A: No. Both tools only repair Windows system files. Your personal documents, photos, and installed apps are untouched.

Q: Can I fix this error without administrator access?
A: Most fixes require admin rights. If you’re on a work or school computer, contact your IT department. On a personal PC, ensure your account is set as Administrator in Settings > Accounts > Your info.

Q: How long does the DISM command take?
A: Typically 10–30 minutes depending on your drive speed and system health. It may appear stuck at 20% or 40% for a while — that’s normal. Don’t close the Command Prompt window.

Q: Why does reinstalling the app work when Windows files are fine?
A: The application’s own files (its DLLs, config files, or registry entries) can be corrupted or incompatible. A fresh install replaces all of those, which resolves the error without touching the operating system.

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 →