You’re halfway through a reply when the screen goes white. “Microsoft Outlook is not responding.” You wait, it comes back, you keep typing — and twenty minutes later it happens again. By the third crash of the morning you’re saving every draft in Notepad first, and your actual work is now scheduled around restarting Outlook.
The good news: repeated Outlook crashes almost always trace back to one of a handful of causes, and there’s a sensible order to check them in. Here’s the checklist we run.
First: which Outlook are you running?
Microsoft currently ships two different Outlooks. If your title bar or the toggle in the top corner says “New Outlook”, you’re on the newer app, and most classic troubleshooting advice doesn’t apply to it. This post is about classic Outlook — the desktop program most businesses still run, and the one with a decade of accumulated ways to misbehave.
1. Install updates before anything else
A surprising share of crash complaints are known bugs that Microsoft has already fixed. In Outlook, go to File → Office Account → Update Options → Update Now and let it finish. If Outlook won’t stay open long enough, update from another Office app like Word — they share the update.
If the crashing started right after an update rather than before one, that’s worth knowing too — occasionally a bad patch is the cause, and Microsoft usually fixes those within days. Either way, be current before you troubleshoot anything else.
2. Test in safe mode — it’s usually an add-in
Add-ins are the single most common cause of repeated Outlook crashes — the little helpers that hook into Outlook for your phone system, CRM, meeting scheduler, or PDF tool.
Close Outlook, press Windows key + R, type outlook.exe /safe, and press Enter. Safe mode loads Outlook without add-ins. Use it for a while. If the crashing stops, you’ve found your category: go to File → Options → Add-ins, choose COM Add-ins → Go, untick everything, then re-enable add-ins one at a time — restarting Outlook after each — until the crash comes back. The last one you enabled is your culprit. This is Microsoft’s own first stop for Outlook crashes, and in our experience it ends the hunt more than half the time.
3. Repair Office
If safe mode still crashes, the Office installation itself may be damaged. Close all Office apps, open Settings → Apps → Installed apps, find Microsoft 365, choose Modify, and run a repair. Try Quick Repair first — it takes a few minutes and fixes corrupted files locally. If that doesn’t help, run Online Repair, which reinstalls Office properly. Plan for that one to take a while.
4. Rebuild the local mailbox file
Classic Outlook keeps a local copy of your mailbox in an OST file, and a corrupted OST causes exactly this kind of repeated crashing. If your email is in Microsoft 365, the file is safely rebuilt from the server: close Outlook, open File Explorer, paste %localappdata%\Microsoft\Outlook into the address bar, and rename the .ost file (add .old to the end). Reopen Outlook and it downloads a fresh copy. On a large mailbox this can take a few hours to fully re-sync, so do it at the end of the day, not before an important send.
5. Create a new Outlook profile
Your profile holds the account setup and settings, and it can quietly corrupt after a failed update or a hard shutdown. Open Control Panel → Mail → Show Profiles → Add, set up your account in the new profile, and set it as the default. If Outlook runs cleanly there, delete the old profile and move on with your life.
A note about the old advice
If you’re following an older guide that says “download Microsoft’s Support and Recovery Assistant (SaRA)” — that tool is gone. Microsoft retired SaRA in March 2026 and folded its diagnostics into the Get Help app built into Windows. If a guide’s screenshots show SaRA, the rest of its advice may be dated too.
When it’s not really Outlook
If you’ve run the whole list and Outlook still crashes, the problem is usually bigger than Outlook: a machine that’s struggling generally, a drive that’s failing, or a mailbox that’s grown past what the machine can comfortably cache. Those are worth diagnosing properly rather than patching around.
And if you’d simply rather hand this off — this is a common call we get, and it’s usually an afternoon to fix, not a project lasting days. Book a call and we’ll take it from there.
