DEV Community

Daylongs
Daylongs

Posted on Originally published at daylongs.com

Outlook not working? Test the server before you touch your PC

When Outlook stops working, the most useful question is whether the problem belongs to Microsoft or to your computer. You can answer it in about two minutes, and the answer decides every step after it.

Open the same mailbox in a browser. If webmail fails too, you are looking at a service incident, a sign-in problem or an account issue. If webmail loads while the desktop app does not, the fault is almost always on the machine.

Split the problem before you fix anything

Most wasted afternoons begin with skipping that split. Someone reinstalls Office on a day when the servers are down, or waits for an outage that turns out to be one broken add-in on one laptop. The browser test costs nothing, and it points you down the right branch.

Read the results like this:

  • Webmail fails and coworkers fail too: a service or tenant problem.
  • Webmail works, desktop fails: suspect add-ins, the profile or cached sign-in data.
  • Phone app works, PC fails: the computer is the problem, not the account.
  • Only you are affected: start with your device and your account.

Laptop on an office desk with an email inbox open on the screen

the fix checklist. See

Check whether Microsoft is actually having a problem

Admins get the authoritative view from the Service health page in the Microsoft 365 admin center, which lists active incidents and recent history. Regular users have to work from Microsoft's public status page, a crowd-report site and a quick message to a coworker, roughly in that order of trust.

Crowd-report sites are useful but easy to over-read. A spike means many people clicked ”I have a problem.” It does not mean Microsoft has confirmed anything, and a flat graph does not rule out a problem limited to your tenant. Treat the report site as a clue and the official dashboard as the verdict.

Something similar was reported in mid-November 2026. News coverage described a large Outlook and Exchange Online disruption around November 12 and 13. The accounts disagree on the cause and on when service fully returned, and I could not find an official post-incident review, so treat any specific claim about that event as reported rather than confirmed.

A flaky home connection can make a healthy app look broken, so check your network if the browser test gives mixed results.

Faster navigation while you fix it:

The practical move is to match the headline against your own symptoms: when it started, the exact error text, and how many people you can see affected. Those three facts tell you far more than a news story does.

Frustrated person looking at a laptop

WiFi speed fixes. See

Know which Outlook you are running

Classic Outlook and new Outlook share a name and not much else. Safe Mode, COM add-ins, mail profiles and Office repair belong to the classic app and generally do not apply to the new one. Before you follow any troubleshooting guide, confirm which version is open. Builds differ, so look for a ”Try the new Outlook” toggle or a switch-back option in the menus.

Once you know the version, the usual suspects are predictable. Add-ins are the most common reason an app hangs at startup while webmail works, especially video-conferencing connectors, CRM plug-ins and translators. Profile or data-file damage tends to follow a crash or a nearly full disk. Stuck credentials show up after a password change or when multi-factor sign-in gets switched on. Update fallout is the last suspect: it was fine yesterday and is slow today.

Always work from the lightest fix to the heaviest, and retest after each step so you know what actually helped. The Outlook fix checklist in the original post sets out that order and the point where you should stop and ask for help.

If the whole machine is sluggish, Outlook may be a symptom rather than the cause, so a general slow-computer checklist can save more time than any mail-specific tweak.

Server racks with blinking status lights

slow computer fix. See

Protect your mail before you repair anything

Whether a repair can cost you mail depends on the account type. For a Microsoft 365 or Exchange account, the local OST file is a cache of what lives on the server, so rebuilding it is normally safe, although large mailboxes take a while to resync. For POP accounts and PST files, the mail may exist only on your disk. Back up the file before you touch it, and rename rather than delete.

While the service is down, use the routes that still work. Webmail is the first choice when it is up, the phone app is a second route if the fault sits on your device, and a call or chat is the right channel for anything that cannot wait. Mail sent during an incident can be delayed or bounced, so confirm important messages arrived.

Read bounce messages carefully. The error code separates a bad address from a full mailbox and from a temporary server problem, and each one calls for a different response. After recovery, delayed messages often arrive in a burst, so sort by received time and skim for anything urgent.

Before you contact IT or Microsoft support, gather five things: whether webmail works, which Outlook you run and its version, the exact error text, when it started and what changed just before, and how many other people see the same problem. That short list usually separates a service incident from a single-device issue in one exchange.

Reinstalling Office is the last card you play, not the first. The browser test, the version check and a safe launch settle most cases without it.

Menus and policy pages change, so if your screen differs from this description, check Microsoft's current documentation before you change profiles or data files.

Outlook checklist: which of the five repairs to run first, and when to stop:

See the Outlook fix checklist on daylongs.com

See the Outlook fix checklist on daylongs.com

Faster navigation while you fix it: Also read: 50 Keyboard

Top comments (0)