Meaning of the symptom
If an app launches and dies quickly, the real issue is usually inside startup dependencies, runtime configuration, or user profile state.
Safe sequence
- Decide whether the failure is one-user or system-wide.
- Read the nearest crash or event evidence.
- Check config and runtime prerequisites.
- Repair one layer at a time.
Common branch decisions
- If one user is affected, focus on profile, cache, or per-user config.
- If all users are affected, focus on package, runtime, or shared dependency state.
- If the app fails only after an update, compare what changed in the runtime path.