BlueByte
Cannot open the Outlook windowFixed

Outlook: Cannot start Microsoft Outlook. Cannot open the Outlook window

By Haneul SeoUpdated August 21, 20263 min

Hi, it's BlueByte. When Outlook refuses to open its window, it is tempting to rebuild everything — but usually a one-line reset fixes it and your mail is never at risk. Let's work through the causes cheapest-first, so you do not rebuild a profile when resetting the pane would have done it.

What the error means

Outlook fails to launch with:

Cannot start Microsoft Outlook. Cannot open the Outlook window.
The set of folders cannot be opened.

The wording varies — sometimes "The set of folders cannot be opened", sometimes a reference to the data file — but the outcome is the same: Outlook cannot build its main window. A few reasons are likely, and the order you try them in matters.

Why Outlook can't build its window

  • Corrupt navigation pane settings. Outlook stores the left pane's state in a settings file; if it is corrupt (often after a crash) Outlook cannot draw the window.
  • A damaged mail profile — the container that holds your accounts and points at your data files.
  • A corrupt data file (.pst/.ost) that Outlook cannot open.
  • A misbehaving add-in loading at startup.

First, rule out add-ins with safe mode

Start Outlook in safe mode to take add-ins out of the picture — nothing here changes your mail:

outlook.exe /safe

If it opens in safe mode, an add-in is the cause. If it still fails, the problem is the pane, profile, or data file, which the fixes below address in order. You can narrow the data file too: if only one account fails to load while others open, that account's .ost is the suspect.

Work the fixes cheapest-first

  1. Reset the navigation pane. Close Outlook, press Win+R, and run:
outlook.exe /resetnavpane

This rebuilds the pane settings and clears the most common cause. It does not touch your mail.

  1. Rebuild the profile. Open Control Panel → Mail → Show Profiles, add a new profile, set it as default, and start Outlook on it. For Exchange/Microsoft 365 the mailbox lives on the server and re-downloads; for POP, back up the .pst first.

  2. Repair the data file. Run the built-in Inbox Repair tool, SCANPST.EXE, against the .pst/.ost before reusing it.

Outlook crashed during a large search and now refuses to open with "The set of folders cannot be opened." You try outlook.exe /safe and it still fails, ruling out an add-in. outlook.exe /resetnavpane also does not help, so the profile or data file is suspect. You create a fresh profile in Control Panel → Mail, set it as default, and start Outlook — because the account is Microsoft 365, the mailbox re-downloads from the server and Outlook opens normally. The old profile was the culprit; no mail was lost because it lived on the server.

Confirm it's actually healthy

Start Outlook normally. It should open to your inbox with folders visible. Send yourself a test message and confirm it arrives — that proves the profile and data file are healthy, not just that the window opened.

Keep it from recurring

Let Outlook close cleanly rather than killing it, keep add-ins to the ones you actually use, and on Exchange/Microsoft 365 accounts prefer server-side mailboxes so a damaged local file is never the single point of failure.

How this differs from a send/receive error

This is a startup failure, not a send/receive error like 0x800CCC0E (a connection problem) — those happen after Outlook is already open. If Outlook opens but a specific account fails, that is an account or connectivity issue, not this window-creation failure. When the window itself won't open, start at /resetnavpane.

Related questions

Will /resetnavpane delete my emails or accounts?

No. It only rebuilds the navigation pane layout. Your accounts and messages are not affected.

A new profile did not help. What next?

Run SCANPST.EXE on the data file to repair corruption, and confirm safe mode (outlook.exe /safe) to rule out an add-in.

It opens in safe mode but not normally.

An add-in loaded at startup is the culprit. Disable add-ins (File → Options → Add-ins → Manage COM Add-ins) and re-enable them one at a time to find it.

Where is SCANPST.EXE?

It ships with Office, in the Office install folder (the exact path depends on your Office version and 32/64-bit). Search the Program Files Microsoft Office folders for SCANPST.EXE.

Only one account fails to load. Do I rebuild everything?

No — that points at that account's .ost file. Close Outlook, rename the .ost so Outlook rebuilds it from the server, then reopen. The other accounts are fine.

References

Haneul Seo

Infrastructure engineer · 10+ years running Linux fleets

More in this category

5.7.26Fixed

Gmail rejects your mail with 550-5.7.26: unauthenticated email is not accepted due to the domain's DMARC policy

Gmail enforced the DMARC policy your own domain publishes: the message failed both SPF and DKIM alignment against the header From: domain, so a p=quarantine or p=reject policy turned it into a hard bounce. The Authentication-Results header names the failing check, and three dig queries against your SPF, DMARC and DKIM records name the cause. A near-identical bounce about authenticating with SPF or DKIM is a different problem — Gmail's baseline sender requirements, not your policy.

Gmail / Google Workspace
AADSTS50011Fixed

Microsoft Entra ID: AADSTS50011, the redirect URI specified in the request does not match the redirect URIs configured for the application

Sign-in completes and then Entra ID refuses the last hop, because the redirect_uri your app sent is not a byte-for-byte match for any URI registered on the app. The match is case-sensitive, counts the trailing slash, requires https outside localhost, and treats the port as significant everywhere except localhost. It also splits by platform: web, spa and publicClient are three separate lists, and URIs added to the service principal instead of the application object can disappear. Read the URI and the app ID out of the error, compare them with az ad app show, add the exact string with az ad app update or a Graph PATCH, then wait three to five minutes.

Microsoft Entra ID
535 5.7.139Workaround

Exchange Online: 535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled

A scanner, script or app that sends through smtp.office365.com gets 535 5.7.139 because the SMTP AUTH protocol is switched off for the tenant, for that mailbox, or by an authentication policy or security defaults that block Basic authentication. Read the wording (Tenant, Mailbox, or 'did not meet the criteria'), confirm with Get-TransportConfig, Get-CASMailbox and Get-AuthenticationPolicy, then open SMTP AUTH on the one mailbox that needs it rather than tenant-wide. Treat Basic SMTP AUTH as a bridge: Microsoft disables it by default for existing tenants at the end of December 2026, so move the sender to OAuth, High Volume Email or a relay connector.

Exchange Online (Microsoft 365)
Error code: 5003Fixed

Zoom: "Unable to connect" error code 5003 — the desktop app can't reach Zoom while the browser can

Error 5003 is the Zoom desktop app failing to complete its connection to Zoom's servers while the web client on the same machine joins fine. The app needs more than a browser does: Zoom's firewall article lists TCP 443/8801/8802 and UDP 3478/3479/8801–8810 for meetings, a set of CA hosts for certificate validation, and it asks that zoom.us and *.zoom.us be exempted from proxy or SSL inspection. A port test, a curl issuer check, and the app's built-in Network Connectivity Tool (Ctrl+Alt+Shift+D / Cmd+Option+Shift+D) show which of those is cut; fix that layer, and reinstall only when a single machine fails while its neighbours join.

Zoom
Slack cannot connect. / Last updated less than a minute ago…Fixed

Slack: "Slack cannot connect" and the grey "Last updated…" banner behind a corporate proxy

Slack loads channels over ordinary HTTPS but delivers new messages over a persistent WebSocket on port 443 to the three wss-*.slack.com hosts Slack names (primary, backup, mobile). When a proxy or firewall passes the HTTP side and blocks the upgrade — most often because SSL decryption is on for the wss hosts, or the allowlist stops at slack.com — the app shows the grey "Last updated…" banner or "Slack cannot connect." while the browser seems fine. Two curl probes from the affected machine show which layer is blocked; exempt the three wss hosts from decryption, allow every domain on my.slack.com/help/urls, and confirm with my.slack.com/help/test.

Slack
locked for editingFixed

Word: "The document is locked for editing by another user"

Word found a lock — an owner file — for the document and assumed someone else has it open, so it offers only a read-only copy. Usually no one does: a crash left the lock behind, or a hidden Word process is still holding the file. Confirm which, close every Word instance, delete the stale ~$ owner file, and the document opens for editing again.

Microsoft Word