Error 0xC00142 | Start Apps Without Crash Loops

You click an app icon. A splash screen flashes. Then the window closes or never shows up. When the same short code keeps coming back, the app is failing before it can finish its startup routine. That routine leans on Windows system files, app add-ins, and shared runtimes that many programs use.

This guide walks you through a practical fix order that works for most cases. It also helps you spot the “wrong code” problem, since people often mix up this code with a similar Windows launch error that looks almost the same at a glance.

What This Code Usually Means

On many PCs, this code shows up when an app tries to load a dependency and Windows blocks the load, can’t find the file, or finds a file that fails validation. You might see it after an update, after installing a new plug-in, or after a security tool quarantines a DLL.

There are two common patterns:

• One app fails, others work — This points to app files, add-ins, or that app’s runtimes.
• Many apps fail at once — This points to Windows files, system-wide runtimes, or a startup service.

There’s also a naming trap. Many people mean the Windows dialog that reads “The application was unable to start correctly” with code 0xc0000142. That one is widely documented and can share fixes with this topic, but it is not the same string as the keyword in this article. The steps below still help in either case, since both failure types can be caused by file damage, blocked modules, or broken runtimes.

Fast Triage Before You Change Anything

Before you run scans or reinstall tools, spend five minutes collecting two clues. These clues keep you from chasing the wrong fix path.

• Note the exact message text — Copy the full line from the popup or Event Viewer so you don’t mix codes.
• Check which apps fail — Try one built-in app (Notepad) and one third-party app to see if the break is system-wide.
• Confirm your Windows build — Open Settings, then System, then About, and write down the edition and build.

If you want a quick first move, use the table below. It matches what you see to a low-risk first action.

Error 0xC00142 On Windows 11 And 10 Fix Order

This is the fix order that tends to clear the issue with the least disruption. Start at Step 1 and move down until the app launches.

Step 1: Clear the easy blockers

1. Restart the PC — A real restart clears locked files that a shutdown can leave behind with fast startup.
2. Run the app as admin — Right-click the shortcut, choose Run as administrator, and test a launch.
3. Disconnect extra devices — Unplug USB hubs, audio interfaces, and older printers, then test again.

Step 2: Try a clean boot to rule out conflicts

A clean boot starts Windows with a slim set of services. It’s one of the fastest ways to prove that a background tool is blocking the launch.

1. Open System Configuration — Press Win + R, type msconfig, then press Enter.
2. Hide Microsoft services — On the Services tab, tick Hide all Microsoft services.
3. Disable remaining services — Click Disable all, then Apply.
4. Disable startup apps — Open Task Manager, go to Startup, disable non-needed entries.
5. Restart and test — Launch the failing app again.

If the app launches in a clean boot, re-enable items in small groups until the failure returns. The last group you enabled contains the conflict.

Step 3: Repair Windows system files

System file damage can block app loads in ways that look like an app bug. These scans are built into Windows and are safe to run.

1. Open Terminal as admin — Right-click Start, choose Windows Terminal (Admin).
2. Run SFC — Type sfc /scannow and press Enter, then wait for it to finish.
3. Run DISM health restore — Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
4. Restart and retest — Try the app again after the reboot.

Step 4: Repair the app install

If only one app is failing, repair that app before you jump to a full reinstall.

1. Use Apps settings repair — Settings, Apps, Installed apps, pick the app, choose Modify or Repair if offered.
2. Reset only if repair fails — Reset can wipe app data, so save local settings first when you can.
3. Reinstall as a last app-only step — Uninstall, restart, then install the latest build from the vendor.

Step 5: Reinstall shared runtimes many apps rely on

Many desktop apps rely on Microsoft Visual C++ Redistributable packages. A damaged install can cause a launch crash without a clean error message.

1. Open Installed apps — Search “Installed apps” in Settings.
2. Remove duplicate broken entries — Uninstall older C++ packages only if they show install errors or failed updates.
3. Install current redistributables — Download fresh packages from Microsoft’s official download pages and install both x64 and x86 where offered.
4. Restart and test — Launch the app again.

Fixes When The Error Hits Office, Outlook, Or Excel

Office apps have two extra failure points: add-ins and licensing components. A bad add-in can break the launch long before you get an error that explains what happened.

Start Office in safe mode to rule out add-ins

1. Open the Run box — Press Win + R.
2. Launch safe mode — Type excel /safe or outlook /safe, then press Enter.
3. Disable add-ins — In the app, open Options, then Add-ins, then manage COM Add-ins and untick them.
4. Restart the app normally — Close safe mode and launch the usual way.

Run an Office repair

1. Open Apps settings — Settings, Apps, Installed apps.
2. Select Microsoft 365 or Office — Choose Modify.
3. Run Quick Repair first — It’s faster and often fixes broken binaries.
4. Run Online Repair if needed — This takes longer and refreshes more files.

After repair, launch the app again. If the same popup still appears, test a new Windows user profile. A corrupted profile can break app startup through damaged cache folders.

1. Create a new local user — Settings, Accounts, Other users, Add account.
2. Sign in to the new account — Then try opening the app.
3. Migrate only what you need — Move Documents and required settings if the new profile works.

When This Code Appears In Developer Tools Or SSIS

If you see this error while opening SSIS packages in Visual Studio, the culprit is often a version mismatch between Visual Studio extensions, SQL Server client components, or installed SSMS builds. The fix path is more about keeping your toolchain aligned than about Windows repair.

Start by lining up SSIS components

1. Update the SSIS Projects extension — Use the Visual Studio Installer to update the Integration Services Projects extension.
2. Check SSMS version conflicts — Newer SSMS builds can clash with older SSIS components on some setups.
3. Reboot after updates — Tooling updates often swap shared DLLs that stay locked until restart.

Verify package target and runtime

1. Confirm the project target — Check the SSIS project target server version and keep it aligned with your SQL Server.
2. Review connection managers — Older providers can fail to load in newer environments.
3. Test with a blank package — Create a new package and open it to see if the issue is global or package-specific.

If Visual Studio launches fine but packages fail to open, the issue is more likely a package dependency than a Windows launch block.

Keep It From Coming Back

Once you get a clean launch, a few habits reduce the odds of seeing the same crash loop again. These are small steps that keep shared components stable.

1. Keep Windows updates current — Security and servicing updates often patch loader issues and shared runtime bugs.
2. Limit add-ins to what you use — Add-ins hook into startup, so each extra one adds a failure point.
3. Install runtimes from official sources — Third-party “driver packs” can swap DLLs in messy ways.
4. Use one antivirus engine — Running two real-time scanners can cause file locks during app launch.
5. Back up before major tool upgrades — A restore point before Office or Visual Studio updates makes rollback simple.

If you still hit error 0xC00142 after all steps, the fastest next move is to capture a crash entry from Event Viewer and match the “faulting module” name to the failing app. That module name is often the missing piece that tells you whether the break is a plugin, a runtime DLL, or a driver layer.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback