The Application was unable to start correctly 0xc0000142

Contents

    The error 0xc0000142 is shown on your computer when you try to launch a program. This error code is shown a long with the message that says

    The application was unable to start correctly (0xc0000142).

    Below is the simple fix, that I was able to

    Fix.

    Running the application in compatibility mode solves many issues. Here are the steps to enable compatibility mode.

    1. For this purpose you have to right-click the application.
    2. Head over to the properties. Go to the compatibility tab.
    3. From there you can enable the compatibility option and select the windows type.
    4. Apply the changes and check whether the problem has resolved or not.

     

    Updated on April 26, 2018
    Was this article helpful?

    24 responses to “The Application was unable to start correctly 0xc0000142”

    1. Jgscvoica Avatar

      Great detail here. Would you add a note about recovery if the step fails?

    2. This is refreshingly practical—what’s your preferred validation command?

    3. fleerehar Avatar

      Solid explanation. Could a baseline capture make future incidents quicker?

    4. aussjay Avatar

      That edge case is easy to miss. How do you verify the service state afterward?

    5. Tulleycle Avatar

      Useful walkthrough—would you compare these results across versions?

    6. spunky game Avatar

      Thanks for spelling this out. Which warning sign should prompt a pause?

    7. 789taya Avatar

      Nice troubleshooting angle. Is there a lightweight way to automate this check?

    8. 789taya Avatar

      The example helps a lot—what would you inspect if the symptom returned?

    9. 789taya Avatar

      This is a great checklist. Would testing on a spare host change the order?

    10. 789taya Avatar

      Clear and actionable. What common misconfiguration should readers rule out first?

    11. 789taya Avatar

      I like the direct approach—would you document the rollback step as well?

    12. 789taya Avatar

      Good reminder to verify assumptions. Which variable matters most here?

    13. 789taya Avatar

      This is a crisp explanation; how would you adapt it for a remote session?

    14. 789taya Avatar

      A useful distinction. What result would confirm that the fix actually worked?

    15. winph99 Avatar

      Helpful context—would you collect a fresh event log before changing anything?

    16. winph99 Avatar

      The troubleshooting path is nicely ordered. Which step is easiest to overlook?

    17. Casey Wu Avatar

      Could a minimal reproduction narrow this down, or is the full environment required?

    18. winph99 Avatar

      Appreciate the clarity here—what’s the quickest sanity check after applying this?

    19. phlwinapp Avatar

      This makes the failure mode much clearer. Have you seen logs point elsewhere?

    20. phlwinapp Avatar

      Strong practical tip—where would you add a safety check before rebooting?

    21. phlwinapp Avatar

      Nice overview. Which diagnostic step tends to reveal the root cause fastest?

    22. Morgan Reed Avatar

      The pacing here is excellent—what would you monitor first if the rollout stalled?

    23. Taylor Chen Avatar

      Would you compare the before-and-after results on a test machine?

    24. Jordan Lee Avatar

      A concise breakdown—would you test this with a clean profile first?

    Leave a Reply

    Your email address will not be published. Required fields are marked *