When New Outlook for Windows gets stuck on the “Opening Outlook” splash screen, the application has stalled during its initial web shell initialization or local data handoff. Unlike classic Outlook, which loads native binary components, New Outlook is built on Microsoft Edge WebView2. If the background process hangs, its local cache corrupts, or token handoff fails, the launch sequence freezes.
Fast Fix
End all background Outlook tasks in Task Manager (
Ctrl + Shift + Esc > olk.exe > End task). Next, go to Windows Settings > Apps > Installed apps > Outlook (New) > Advanced options, and click Reset. Relaunch the app to build a fresh runtime cache.
Diagnostic Snapshot
| Property | Details |
|---|---|
| Symptom | Blue splash screen displays “Opening Outlook” with an infinite spinner or blank frame |
| Underlying Architecture | Microsoft Edge WebView2 runtime and local AppData service worker storage |
| Common Causes | Orphaned olk.exe processes, corrupted WebView2 cache, or stale identity tokens |
| Resolution Time | 3 to 10 minutes |
Why the Launch Sequence Freezes
Classic Outlook loads executable code directly into local memory through OUTLOOK.EXE. New Outlook operates through an execution container called olk.exe, which boots a local instance of the Edge WebView2 engine and connects to the Exchange Online service worker.
The splash screen remains on screen while three distinct operations complete:
- Runtime Verification: The system verifies that the Microsoft Edge WebView2 Evergreen runtime is present, updated, and responding.
- Local Database Handshake: The app reads local IndexedDB storage in your user profile to load cached mail, layout preferences, and offline tokens.
- OAuth Token Refresh: The client acquires a silent authentication token from the Windows Web Account Manager (WAM).
If any of these three stages encounters locked files, corrupt cache partitions, or an authentication timeout, the loader stops responding without producing an explicit error code.
Launch New Outlook (olk.exe)
│
├── 1. Edge WebView2 Boot ──────> Fails if runtime is corrupt or blocked
│
├── 2. IndexedDB Cache Read ────> Fails if %localappdata%\Microsoft\Olk is locked
│
└── 3. WAM Token Handshake ─────> Fails if identity cache/MFA is hung
Progressive Troubleshooting Steps
Step 1: Terminate Orphaned Processes
A background instance of New Outlook that did not close cleanly will lock the local storage database, preventing any new instance from launching.
- Press
Ctrl + Shift + Escto open Task Manager. - Select the Details tab.
- Look for any running instances of:
olk.exemsedgewebview2.exe(specifically instances grouped under Outlook)
- Select each process and click End task.
- Relaunch New Outlook from the Start menu.
Step 2: Repair and Reset the Windows App Package
If terminating background processes does not resolve the freeze, the local app package state may be damaged.
- Right-click the Windows Start button and select Installed apps (or Apps & features).
- Locate Outlook (New) in the application list.
- Click the three dots (…) next to it and select Advanced options.
- Scroll down to the Reset section:
- Click Repair first. This checks system file integrity without clearing your account settings.
- If the app still hangs on launch, return to this screen and click Reset. This deletes local cache data, requiring you to re-authenticate on the next launch.
Step 3: Clear the Local Olk Storage Cache Manually
Sometimes the Windows package manager leaves behind locked or orphaned directories in your user profile. Removing them manually forces the client to download a clean web shell:
- Close all Outlook windows and confirm
olk.exeis terminated in Task Manager. - Press
Win + Rto open the Run dialog. - Enter the following path and press Enter:
%localappdata%\Microsoft\Olk - Press
Ctrl + Ato select all files and folders insideOlk, then pressDelete. - Restart your computer and launch New Outlook.
Note: Deleting this folder does not delete your emails or calendar entries. Your data resides securely in Exchange Online and will resynchronize once the app opens.
Step 4: Verify Edge WebView2 Runtime Health
Because New Outlook relies entirely on WebView2 to render its interface, a broken, blocked, or outdated runtime will halt the boot sequence indefinitely.
- Open Windows Settings > Apps > Installed apps.
- Search for Microsoft Edge WebView2 Runtime.
- If it is missing or showing an update failure:
- Download the Evergreen Bootstrapper directly from Microsoft’s official WebView2 portal.
- Right-click the installer and choose Run as administrator.
- If your system runs third-party endpoint security or application control policies, verify that
olk.exeandmsedgewebview2.exeare not blocked from executing out of%localappdata%.
For a dedicated walkthrough on repairing runtime corruption, see:
Step 5: Clear Broken Identity Tokens
If the splash screen hangs while trying to validate your Microsoft 365 credentials, a corrupted token in the Windows Web Account Manager (WAM) may be holding the process open.
- Open Windows Settings > Accounts > Access work or school.
- Identify the account associated with your New Outlook profile.
- If the account displays an error or an “Attention required” prompt, click it and select Disconnect (or re-authenticate when prompted).
- For deeper credential cache remediation steps, consult:
Hard Stops and Temporary Workaround
If New Outlook continues to hang after resetting the application, clearing the Olk folder, and verifying WebView2, the issue typically points to a machine-wide policy conflict, a managed network proxy blocking required web socket endpoints, or a pending Windows update.
To restore business communications immediately without waiting for a full system audit:
- Access your mailbox via a web browser at
outlook.office.com. - Return to the classic desktop client while diagnosing client machine policies: