Error 0xC0000142 | Fix Startup Failures Fast

You click an app icon and get “The application was unable to start correctly (0xc0000142).” That code is Windows telling you the app failed during its first load phase. It can happen with games, Office apps, admin tools, and even system utilities.

The fix is rarely one magic switch. You want to narrow the scope, then repair the pieces Windows uses to start programs: system files, runtimes, and startup hooks from other software.

This guide walks you through a clean order of checks, then deeper repairs, with clear stop points so you don’t keep changing things after the issue is already gone.

What Error 0xC0000142 Means In Plain Terms

Error 0xC0000142 is tied to a startup initialization failure. Windows loads the app, then loads required libraries, then runs the app’s entry point. If a required DLL fails to initialize, or the process can’t load what it needs, Windows stops it and shows the code.

You’ll often see it with one of these patterns:

• App starts then closes — You may see a cursor spin, then nothing.
• Error appears right away — A dialog shows the code and an OK button.
• Only admin tools fail — Command Prompt, PowerShell, SFC, or DISM won’t open.

The right fix depends on which pattern you have. Your first job is to spot whether this is a single-app problem or a wider Windows problem.

Error 0xC0000142 Checks You Can Do In 5 Minutes

Start with checks that don’t change much on your system. Each one answers a question that guides the next step.

1. Restart the PC — A stuck update, hung service, or half-loaded driver can trigger this. A full restart clears a lot of one-off launch failures.
2. Try a different user account — If it works there, the issue is tied to your profile settings or startup items, not Windows core files.
3. Run the app as admin — Right-click the app, choose Run as administrator. If it works only as admin, permissions or an install path can be involved.
4. Check whether it’s one app or many — Open two unrelated apps, like Notepad and your browser. If both fail, jump to the system repair section.
5. Look for a recent change — A new driver, security tool, overlay, or Windows update can be the trigger. You’re not rolling back yet; you’re just building a short list.

If the error still hits, use the table below to match what you’re seeing to a smart next move.

Fixing Error 0xC0000142 On Windows 11 And 10

This section is the core path when multiple apps fail, or when you can’t pin it to a single install. Do the steps in order. After each step, try launching the app again so you know which change did it.

Repair Windows system files with DISM and SFC

Windows includes two tools that check and repair system files. Microsoft’s own guidance is to run DISM first, then SFC. You can follow Microsoft’s steps here: System file repair steps.

1. Open Windows Terminal as admin — Right-click Start, choose Terminal (Admin).
2. Run DISM RestoreHealth — Type DISM /Online /Cleanup-Image /RestoreHealth, then press Enter.
3. Run SFC — After DISM finishes, type sfc /scannow, then press Enter.
4. Restart Windows — Reboot, then test the failing app again.

If SFC reports it fixed files, test right after the restart. If it reports it could not fix some files, run the two commands one more time after the reboot.

Update Windows and reboot once more

After system repairs, run Windows Update and install pending patches, then restart. Some fixes land as part of servicing updates and only take effect after a reboot.

Use a clean boot to find software conflicts

Launch failures often come from background software that injects into apps at startup. A clean boot starts Windows with a minimal set of startup items so you can spot the conflict. Microsoft’s step-by-step page is here: Clean boot instructions.

1. Open System Configuration — Press Windows+R, type msconfig, press Enter.
2. Hide Microsoft services — In Services, tick Hide all Microsoft services, then click Disable all.
3. Disable startup apps — Open Task Manager, disable non-Windows startup entries.
4. Restart and test — If the app launches now, re-enable items in small groups to find the trigger.

Common triggers include overlays, screen recorders, RGB tools, third-party antivirus suites, and “tuning” utilities. Once you find the culprit, uninstall it or update it to a version that plays nice with your apps.

Reinstall Visual C++ runtimes when the app is built on them

Many Windows apps depend on Microsoft Visual C++ Redistributable packages. If they’re missing or damaged, apps can fail at startup. Microsoft maintains the latest downloads here: Latest Visual C++ Redistributable downloads.

1. Install both x64 and x86 packages — Many PCs run 64-bit Windows, but some apps still need the 32-bit runtime.
2. Restart after installs — A reboot makes sure the runtime is registered and ready.
3. Try the app again — If it launches now, the runtime chain was the issue.

Stick to Microsoft’s download page for these runtimes. It avoids bundles and keeps you on versions that get security updates.

When Only One App Throws The Error

If everything else opens fine and one program fails, keep the fix focused on that program first. You’ll often solve it faster, with fewer system-wide changes.

Repair the app from Windows settings

1. Open installed apps — Settings, then Apps, then Installed apps.
2. Pick the app — Select Advanced options if available.
3. Run Repair or Reset — Repair keeps data when possible; Reset may clear local app data.

Reinstall the app cleanly

If repair does nothing, uninstall, reboot, then install the latest version from the publisher’s site. A reboot between uninstall and reinstall clears locked files and stale registry entries.

Check compatibility mode for older apps

1. Open app properties — Right-click the app’s EXE, choose Properties.
2. Try compatibility settings — In Compatibility, test Windows 8 or Windows 7 mode.
3. Disable full-screen tweaks — Tick Disable fullscreen optimizations for older games.

Remove plugins, mods, and overlays tied to that app

If the app is a game or a tool with add-ons, remove third-party plugins and mods first. Then try launching with a clean config. Overlays from GPU utilities or chat apps can also trip startup routines.

Office-specific note

If this hits Word, Excel, or Outlook, Microsoft has a dedicated fix flow that leans on repair and reinstall steps. Start here: Office startup error steps.

When Command Prompt And PowerShell Also Won’t Open

If Command Prompt or PowerShell throws the same startup code, you lose the easy path to DISM and SFC. In that case, use Windows Recovery tools to get a working command line and repair from there.

Boot into Windows Recovery and use Command Prompt

1. Open recovery options — Hold Shift while clicking Restart.
2. Choose Troubleshoot — Then Advanced options, then Command Prompt.
3. Run DISM and SFC from recovery — You may need to target the Windows drive letter used in recovery.

If you want a real-world example of this pattern, Windows troubleshooting writers have documented cases where cmd.exe and PowerShell fail with the same code and recovery tools are the way back in. One reference is here: 0xc0000142 affecting cmd and PowerShell.

Check event logs for the failing module

When Windows logs an application error, it often records the failing module name. That module can point to a specific DLL, a runtime, or a security tool hook.

1. Open Event Viewer — Search for Event Viewer, then open it.
2. Go to Application logs — Windows Logs, then Application.
3. Filter by Error — Open the newest entries around the time you launched the app.
4. Note the faulting module — Use it to guide the next uninstall, repair, or runtime reinstall.

Prevent The Error From Coming Back

Once you fix the launch issue, lock in a few habits that cut repeat cases. These steps are small, but they stop the common triggers.

1. Keep Windows updated — Install updates, then reboot when Windows asks. Servicing changes often need that reboot to settle.
2. Install runtimes from Microsoft pages — Use the Visual C++ Redistributable page for clean installs and current builds.
3. Avoid “PC booster” tools — Tools that claim to clean registries or speed apps often break shared components.
4. Limit overlays and injectors — If you use overlays, keep only the ones you truly use, and keep them updated.
5. Create a restore point before big changes — Drivers, major updates, and security suite swaps are good moments for a restore point.

If you see Error 0xC0000142 again after a new install, test with a clean boot early. It’s a fast way to confirm whether the new software is clashing with something already on the PC.

Reference Links For Official Steps

These links point to Microsoft pages that describe the same repair tools used in this article:

• System file repair with DISM and SFC — Microsoft guide
• Clean boot procedure — Microsoft guide
• Visual C++ Redistributable downloads — Microsoft Learn page
• Office startup error 0xc0000142 — Microsoft Office steps

If you’ve done the system repairs, tested a clean boot, reinstalled runtimes, and the same program still fails, the next best move is to reinstall the app and its related components from the publisher, then test before adding plugins and overlays.

When the error is tied to a recent Windows build change, checking Microsoft’s Q&A threads can also show whether others hit the same issue and what patch fixed it. One recent thread tied to Start menu search errors is here: Microsoft Q&A thread.

Most cases end up being one of three things: system files that needed repair, a runtime that needed reinstall, or a background app that needed removal. Work the steps in order, test after each change, and you’ll usually get your apps launching again without a full Windows reinstall.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback