"Excel closes every time I open it." "Word says it has stopped working." Office apps crashing is one of the most common desktop tickets, and one of the easiest to over-fix. It's tempting to go straight to a full reinstall, but Microsoft's own troubleshooting puts a two-minute test first: does the app open in Office Safe Mode? The answer tells you whether you're looking at an add-in, the user's file, or the Office installation itself.
These are my study notes on how I would work an "Office keeps crashing" ticket, written as a guide and "what I learned," with each step checked against Microsoft's documentation. It follows the same troubleshooting ladder I use for other Microsoft 365 tickets: find which layer is failing, change one thing at a time, and write down what changed.
First questions
- Which app, and what exactly happens? Crashes at startup, freezes ("Not Responding"), or closes while doing one specific thing (opening a file, printing, saving)? Write down the exact error text.
- Every file or one file? If Excel only crashes on one workbook, I test with a new blank workbook before touching the installation.
- One user, one PC, or many? Many users at once after an update points to something bigger than one PC, so I check for a known issue and tell my lead early.
- What changed? A new add-in, a new PC, a Windows or Office update, a new docking station or printer driver.
- Is Office up to date? Microsoft says to install Office updates before trying anything else: File > Account > Update Options > Update Now [1].
Step 1: Office Safe Mode, the dividing line
Office Safe Mode starts the app without add-ins and customizations [2]. It is not the same as Windows safe mode; only the Office app is affected [2]. Two ways to start it [2]:
- Hold Ctrl and open the app's shortcut, then choose Yes when asked about Safe Mode.
- Press Windows + R and type one of these:
winword /safe,excel /safe,powerpnt /safe, oroutlook /safe.
Check the title bar: it should say something like "Microsoft Excel (Safe Mode)" [1]. If you get a "can't find" error, check that there's a space before /safe [1]. To leave Safe Mode, close the app and open it normally [2].
How I read the result, based on Microsoft's article [1]:
- Opens in Safe Mode, crashes normally: most likely an add-in. Go to Step 2.
- Doesn't open even in Safe Mode: the problem isn't add-ins. Go to Step 3 (repair).
Step 2: Find the add-in, one at a time
Microsoft's process [1]:
- With the app still in Safe Mode, go to File > Options > Add-ins.
- In the Manage list, pick the app's own add-ins (for example Excel Add-ins) and select Go. If there isn't one, pick COM Add-ins.
- Uncheck one add-in and select OK.
- Restart the app normally.
- If it starts, the add-in you unchecked is the suspect. If not, repeat with the next one, then do the same for the COM Add-ins list.
When the culprit is found, Microsoft suggests checking the add-in vendor for an update, or leaving it disabled if the user doesn't need it [1]. Some older add-ins are known to cause these crashes; Microsoft names older versions of ABBYY FineReader and Dragon NaturallySpeaking [1].
Two notes I keep for real tickets:
- Office may have already disabled something. When an app can't start because of an add-in or a damaged file, Office's automated safe mode can offer to disable it. Those items show up under File > Options > Add-ins > Manage: Disabled Items [2]. I check this list before I assume nothing changed.
- A business add-in is not mine to remove. If the suspect is the CRM, e-signature, or document-management add-in the whole team uses, I leave it disabled for the test only, write down its name and version, and escalate. Turning it off for good can break a workflow for that user.
Step 3: Repair Office (quick first, then online)
If the app won't start even in Safe Mode, Microsoft's next step is to repair Office [1]:
- Close all Office apps.
- Right-click Start > Installed apps, find the Microsoft 365 or Office entry, select the ... menu, and choose Modify [3].
- For the common Click-to-Run install, choose Quick Repair first. It's faster and only finds and replaces damaged files. If that doesn't help, run Online Repair, which takes longer and needs an internet connection [1][3].
Two things I tell the user before starting:
- The repair covers the whole Office suite, even if only Excel is broken [3]. Every Office app has to be closed.
- A restart may be needed afterwards [3].
On a managed PC I check first whether repairs are allowed for my role, and whether Office is deployed in a way that the team wants handled centrally (for example, a packaged install). A full uninstall and reinstall is Microsoft's last step [1], and on a company PC I treat that as a decision for Tier 2, not something I start on my own.
Step 4: Drivers and updates
If repair doesn't fix it, Microsoft points at device drivers: run Windows Update, then make sure the video card, printer, mouse, and keyboard drivers are current, and check the laptop maker's site for updates [1]. Microsoft even names a known issue with an older DisplayLink user-mode driver used with some laptops and docks [1]. That's a useful clue when "Excel crashes" started the same week a user got a new USB dock.
Evidence for the escalation: Reliability Monitor and Event Viewer
Before escalating, I collect a crash record instead of writing "Excel keeps crashing":
- Reliability Monitor: run
perfmon /relto see a timeline of application failures. It shows quickly how often the crash happens and since when. - Event Viewer: Windows Logs > Application, filtered for Event ID 1000 (source Application Error). That event records the faulting application, the faulting module, the exception code, and the module path [4].
The faulting module is a clue, not proof. Microsoft notes that core Windows modules such as ntdll.dll or kernelbase.dll often show up as the faulting module even when another component caused the problem [4]. A third-party DLL in the module path, though, is a strong hint to check that add-in or driver first.
What about Outlook?
Classic Outlook follows the same idea with its own steps. Microsoft's article for crashes and hangs starts with outlook /safe, then disabling COM add-ins one at a time [5]. Outlook also has extra suspects, such as the Outlook data file and the mail profile, and a stuck "Processing" screen that a Safe Mode start can clear [6]. The classic Outlook advanced diagnostic troubleshooter doesn't apply to the new Outlook for Windows [5], so I confirm which Outlook the user has first, the same question I start with for Outlook search tickets.
What I would not do
- Reinstall Office as step one. Safe Mode and a Quick Repair take minutes and keep the user's settings.
- Turn off antivirus or security add-ins "to test." That goes to the security team with evidence.
- Remove a line-of-business add-in for good without the app owner or Tier 2.
- Edit the registry because a forum post said so. On managed PCs, policy and packaging control a lot of Office behavior.
The ticket note
Symptom: Excel (Microsoft 365 Apps) closes within 5 seconds of opening,
any file and new blank workbook. Started Mon after a new USB dock.
Scope: 1 user, 1 PC (Windows 11). Word/PowerPoint OK.
Checks: Office updated (File > Account > Update Now). excel /safe opens
normally. File > Options > Add-ins: unchecked "Example PDF Add-in"
(COM), Excel starts normally. Disabled Items list empty.
Evidence: Event ID 1000, faulting app EXCEL.EXE, faulting module path
under the add-in's program folder. Reliability Monitor: 6 Excel
failures since Monday.
Action: Left add-in disabled with user's OK; user confirmed Excel works.
Next: Add-in is used by Finance; escalated to Tier 2 / app owner for an
updated version. Not removed.
(Example ticket, not from a real case.)
What I learned
- Safe Mode is the dividing line. If the app opens there, look at add-ins. If it doesn't, look at the installation.
- One add-in at a time. Turning them all off fixes the symptom but doesn't tell you which one caused it.
- Check Disabled Items. Office may have already switched something off, and the user won't know.
- Quick Repair before Online Repair, and both before a reinstall. The repair is suite-wide, so every Office app must be closed.
- Drivers matter. Video, printer and dock drivers can crash Office, so "what changed?" is a real question, not small talk.
- Bring evidence. Event ID 1000 and Reliability Monitor turn "it keeps crashing" into something Tier 2 can act on.
Sources
- Microsoft Support, I get a "stopped working" error when I start Office applications on my PC: https://support.microsoft.com/en-us/office/lifecycle/i-get-a-stopped-working-error-when-i-start-office-applications-on-my-pc
- Microsoft Support, Open Office apps in safe mode on a Windows PC: https://support.microsoft.com/en-us/office/lifecycle/open-office-apps-in-safe-mode-on-a-windows-pc
- Microsoft Support, Repair an Office application: https://support.microsoft.com/en-us/office/lifecycle/repair-an-office-application
- Microsoft Learn, The application or service crashing behavior troubleshooting guidance: https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-application-service-crashing-behavior
- Microsoft Support, Outlook crashes or stops responding when used with Office 365: https://support.microsoft.com/en-us/outlook/outlook-crashes-or-stops-responding-when-used-with-office-365
- Microsoft Support, Classic Outlook not responding, stuck at "Processing," stopped working, or freezes: https://support.microsoft.com/en-us/outlook/classic-outlook-not-responding-stuck-at-processing-stopped-working-or-freezes
I'm Rıza Korkusuz, an IT support professional in San Diego. I write these notes to organize what I'm learning about desktop and service desk work. More at rizakorkusuz.com/it-support and github.com/rizakorkusuz.