Outlook Kept Freezing. The Cause Was a 38 GB Mail File

A real job from summer 2026, anonymised. An office desktop at a local business, an Outlook that kept vanishing mid-work, and a diagnosis made from evidence rather than guesswork.

The Problem

A member of staff at a local business reported Outlook closing unexpectedly, seemingly at random. From the user's side it looked like the application was crashing several times a day, losing whatever they were in the middle of.

Diagnosis

We connected remotely and diagnosed the machine without interrupting the user's work. The Windows event log told a precise story: Outlook was not crashing at all. There were no application crash events in the preceding three weeks. Instead, the log showed hang events, meaning Outlook was becoming unresponsive and being closed. The distinction matters, because the two problems have completely different causes.

The cause of the hangs was on disk. The Outlook offline data file for the user's mailbox had grown to 38 GB. For comparison, another profile on the same machine was under 4 GB. At that size, Outlook blocks on disk access and stops responding, which to the user looks identical to the application closing at random.

The Fix

The recommended fix was a configuration change, not a reinstall: set Outlook's cached mode to keep 12 months of mail offline rather than the entire mailbox, so it rebuilds a much smaller local file. Because the mailbox re-downloads during the rebuild, the work was planned for a time when the machine could be left alone rather than forced on the user mid-week.

The diagnosis also surfaced a second, quieter problem: a local mail file that size usually means the mailbox itself is approaching its Microsoft 365 storage quota. That was flagged for checking before it became a separate and more disruptive failure.

The Outcome

The user got an explanation of what was actually happening instead of living with a mystery, the fix was scheduled around their work, and a looming quota problem was caught early. The machine itself checked out healthy: protection, firewall and updates all in order, and Outlook's add-ins loading normally.

What This Illustrates

The reflex fix for a misbehaving Outlook is to reinstall it, which in this case would have changed nothing: the oversized data file would still have been there afterwards. Reading the event log first turned a vague complaint into a specific, fixable cause in one remote session. If Outlook or Microsoft 365 is misbehaving for you, our Microsoft 365 support service starts the same way: with evidence.