The Application Was Unable to Start Correctly (0xc0000142)

What 0xc0000142 means

0xC0000142 is NTSTATUS STATUS_DLL_INIT_FAILED. Microsoft’s wording is: initialization of the dynamic link library failed, and the process is terminating abnormally. A DLL began to load, its startup routine failed, and Windows closed the program.

That is a different code from 0xc000007b ( STATUS_INVALID_IMAGE_FORMAT), which is usually a 32-bit file loaded by a 64-bit process, or the reverse. Do not start with the 32-bit vs 64-bit steps unless the dialog actually shows 0xc000007b.

Microsoft’s Windows SDK note lists three situations that produce this dialog: opening many programs at once, starting the program as a different user, and starting it on a different desktop (including from a background service). The failure belongs to that program’s DLLs, not to a random file you download. Background: the application failed to initialize properly (0xc0000142) · NTSTATUS values.

Repair the program, then read the log

1. Close other programs, then start this one from your own signed-in desktop. Do not use Run as a different user.
2. Repair or reinstall the program from its publisher, or use the launcher’s Verify or Repair files action. That restores the program’s own files.
3. If it still fails, open Event Viewer → Windows Logs → Application. Find the Application Error from the same time and write down Faulting application name and Faulting module name.

Use the name in the log

• The module is msvcp140.dll, vcruntime140.dll, or vcruntime140_1.dll: open msvcp140.dll was not found and install the official package that matches the app. Also see the home Visual C++ step .
• The dialog you actually have is 0xc000007b: switch to the 0xc000007b home page and check 32-bit vs 64-bit first.
• The message says the side-by-side configuration is incorrect, with no 0xc0000142: use side-by-side configuration is incorrect.
• Still failing after a clean reinstall: advanced users can trace the launch with Process Monitor and Microsoft’s start-failure guide, looking for a file that is missing or access-denied. Then contact the app’s publisher.

FAQ

Is 0xc0000142 the same as 0xc000007b?

No. 0xC0000142 is STATUS_DLL_INIT_FAILED: a DLL started to load, its initialization failed, and Windows closed the process. 0xc000007b is STATUS_INVALID_IMAGE_FORMAT, usually a 32/64-bit mismatch. Read the code in the dialog before choosing a page.

What should I do first?

Confirm the dialog says 0xc0000142. Close other programs and start the app from your own signed-in desktop, not with Run as a different user. Then repair or reinstall that app from its publisher.

Event Viewer names a DLL. Should I download it?

No. Write down the faulting module name, then restore it by reinstalling the app or, when the name is msvcp140.dll, vcruntime140.dll, or vcruntime140_1.dll, by installing the official Visual C++ Redistributable. Do not copy a loose file into the app folder or System32.

Why do searches show 0xc000142 or 0xc00000142?

Those are common typos. The NTSTATUS value is 0xC0000142.