my desktop crashes immediately after launch

Patel Vihaan 20 Reputation points
2026-10-09T03:52:02.1133333+00:00

Help please!!

My desktop application on a Windows workstation crashes immediately after launch and cannot be opened normally. The issue started after a recent application component or configuration change. Other applications on the same workstation continue to operate normally. Could you please recommend a way to start the affected application with minimal components or in a diagnostic mode to determine whether a third-party component is causing the crash? How can I identify and disable the problematic component and restore normal application startup?

Windows for business | Windows Server | Devices and deployment | Configure application groups
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Senthil kumar 2,585 Reputation points
    2026-10-09T05:02:10.31+00:00

    Hi @Patel Vihaan

    can you please confirm what you change in component or configuration in the application.

    may be those changes not compatible for the application.

    • Right click your application go to properties then select compatibility -> compatibility mode tick the option and select windows 8 or 7 then click ok and test your application.

    User's image

    • it will not helpful then boot your windows to safe mode and try to open the application.
    • try to open your application then go to Event viewer -> windows logs -> application -> select recent error message click the general details. you will understand what is the issue.

    Thanks.

    Was this answer helpful?

    0 comments
  2. Domic Vo 34,570 Reputation points Independent Advisor
    2026-10-09T04:07:55.8933333+00:00

    Hello,

    Since the issue started after a recent component or configuration change, first try launching the application in its built-in Safe Mode or Diagnostic Mode (if supported). If it opens successfully, a plug-in, add-in, or third-party extension is likely causing the crash.

    If no safe mode is available, perform a Clean Boot using msconfig, disabling all non-Microsoft services and third-party startup items. If the application then starts normally, re-enable components gradually to identify the culprit.

    Also check Event Viewer > Windows Logs > Application and review the crash event for the Faulting Module Name and Exception Code. These often identify the exact DLL or component responsible for the failure.

    For deeper analysis, use Process Monitor (ProcMon) to capture the startup sequence and determine which DLL, plug-in, or configuration file is accessed immediately before the crash. If a recently added component is identified, disable or remove it and retest.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Domic Vo.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.