Troubleshooting

Use the failing action to distinguish file association, app package, COM registration, or system damage; protect inaccessible files before broad repairs. The workflow protects the best source and verifies the result before normal work resumes.

Keep the unsaved Excel session open, create a safe copy, isolate the failed path or format, and recover a lost workbook only after other copies fail.

Separate file, application, policy, mailbox, and cloud-link failures; preserve the original message, apply the smallest fix, and recover a genuinely deleted local attachment safely.

Treat the WHEA stop code as hardware evidence, protect accessible files before firmware or component changes, recover crash-related losses only from stable storage, and verify every later test.

Interpret the crash evidence, protect accessible files, separate hardware and storage symptoms, recover missing data only from stable media, and verify the system after testing one variable at a time.

Compare application architecture, official runtimes and event evidence, then protect projects or saves before reinstalling software or repairing Windows.

Build a crash timeline, isolate drivers, memory and peripherals, protect local data, and verify stability before considering reset or reinstall.

Restore the Microsoft runtime through official installers, test application scope, and preserve local projects before reinstalling or cleaning the app.

Use task progress, workbook location and recovery copies to decide whether to wait or close Excel, then isolate the cause without losing work.

Separate boot-order trouble from an absent or failing drive, preserve recoverable files, and postpone reset or replacement until the storage state is clear.