A program that worked yesterday but closes immediately after an update may be failing to load an extension, old configuration, graphics component or shared dependency. Reinstallation sometimes leaves user data intact and sometimes does not. A better approach is to identify whether the crash follows the executable or follows a particular user profile or document.
Symptoms: what this problem looks like
- The app splash screen appears, then closes without a useful dialog.
- A new update or plugin coincides with startup crashes.
- A second user profile or a blank document opens normally.
Why it happens
- An incompatible extension or plugin loads during startup.
- A corrupted preference file or profile contains outdated settings.
- A graphics, runtime or driver mismatch was exposed by the new release.
Before making changes
Close the application before backing up its profile, settings and autosave locations. Do not delete hidden profile folders or download unofficial DLL bundles. Keep installer/version information available for a controlled rollback if the vendor supports one.
Start with the least disruptive checks, and stop when the original problem is resolved. The Beginner tab below describes the recommended diagnostic sequence. The Advanced tab helps authorized support teams collect evidence without introducing unrelated changes.
Step-by-Step Troubleshooting
Work through the following steps in order. Check the result after each action and preserve a rollback path for any configuration changes.
Identify version, crash window and affected user
Record the exact product, current build, operating system and crash timestamp. Confirm whether startup fails with every document or only a specific project. Check the vendor’s release notes for a documented migration requirement or regression.
Inspect OS and application crash records
On Windows, use Reliability Monitor or Event Viewer; on macOS review the app crash report. Note faulting module and error code without pasting sensitive document paths publicly. A repeated plugin module or graphics library narrows the investigation.
Start in vendor-supported safe mode
If the application provides a safe-mode or no-plugins launch option, use it without deleting user data. A successful safe-mode start suggests an add-on, preference or acceleration setting rather than a total installation failure. Re-enable add-ons one by one after testing.
Back up and test a clean profile
Copy the supported preferences/profile directory to a safe location, then create a new app profile or use a different operating-system account if supported. If a clean profile launches, compare only the relevant configuration files and avoid importing the entire potentially corrupted profile at once.
Check hardware acceleration and graphics drivers
Where the vendor documents an option, test software rendering or disable acceleration for one controlled launch. Review graphics-driver update history; use only manufacturer-supported drivers and documented rollback mechanisms. Avoid changing device-wide graphics settings based on guesswork.
Repair or reinstall the exact trusted build
Use the original vendor installer, repair function or package manager. Confirm licensing and data backup before uninstalling; some uninstallers offer to remove user settings. If a known-good older build is required, follow the vendor’s supported compatibility and security guidance.
Confirm add-ons and project files after recovery
Open a sample project, then the previously failing document. Restore approved extensions in small groups and watch for crash recurrence. Record the component that reintroduces the problem; do not immediately restore an unverified corrupted profile wholesale.
Correlate the original symptom
Compare the earliest reliable error time with the documented indicators: The app splash screen appears, then closes without a useful dialog. Collect only masked diagnostic data, and do not infer causation solely from recent changes.
Validate the strongest suspected cause
Focus the authorized test on this possible failure: A corrupted preference file or profile contains outdated settings. Use staging or a secondary test account when feasible and document the exact rollback before any production configuration edit.
Confirm fix and watch for regressions
Launch the app three times, open and save a noncritical test file, then check that required plugins and original projects work. No crash events should recur during the observation window. Preserve test evidence and route unresolved issues to the responsible vendor or system owner rather than broadening permissions or disabling protection.
Interpret the results
Use the results of your tests to choose the next action instead of repeating a reset. For this specific issue, compare the following observations with the suspected causes:
- Observation A: The app splash screen appears, then closes without a useful dialog. This supports checking: An incompatible extension or plugin loads during startup. Confirm it with a reversible test before making a lasting change.
- Observation B: A new update or plugin coincides with startup crashes. Compare the affected environment with a known-good case and investigate: A corrupted preference file or profile contains outdated settings.
- Observation C: A second user profile or a blank document opens normally. If the earlier checks do not change the result, gather stronger evidence around: A graphics, runtime or driver mismatch was exposed by the new release.
How to verify the fix
Launch the app three times, open and save a noncritical test file, then check that required plugins and original projects work. No crash events should recur during the observation window.
Common mistakes to avoid
- Deleting the entire application profile before taking a backup.
- Installing DLL files from an unofficial mirror to repair a vague crash.
- Assuming reinstalling the program also repairs incompatible plugins or user preferences.
If the problem is still there
Provide the vendor with the application/build, OS, redacted crash report, faulting module and whether clean-profile or safe-mode launch succeeds. Include a minimal nonconfidential reproduction file when permitted.
Include the specific step that changed the outcome, what you expected, and what actually happened. This allows the next person to continue from evidence instead of repeating the same unsuccessful tests.
Solution Checklist
Official reference
For up-to-date menus, compatibility rules and product-specific support paths, see Microsoft: Windows app troubleshooting. Product menus and support options can change with software versions and regions.
Editorial note: Follow these instructions only for systems and accounts you are authorized to manage. Verify each result before proceeding. This guide does not claim that one fix applies to every configuration.