The new Outlook is supposed to be lighter and faster than classic Outlook — but on your Arm laptop it crashes on launch, freezes when you switch folders, or refuses to sync new mail. Email is the one app you cannot avoid for a day, so every glitch costs real time. It stings more on a brand-new AI PC, where everything else feels snappy and this one essential app will not behave.

The new Outlook is a WebView2-based app: its interface is rendered by the same shared web component that powers Teams, Copilot, and Loop. On Arm machines there is an extra wrinkle — you need the native Arm64 build, because the emulated x64 build leans on a translation layer that magnifies every small fault. Most failures trace back to three things: the wrong architecture build, a damaged WebView2 runtime, or corrupted local sync data. Your mailbox itself is fine on the server.

Fixes below run from diagnosis to deep repair. The verify-first pattern also steadies other Arm app troubles, whether that is VLC stuttering on Arm64 Windows or GitHub Desktop misbehaving on an Arm machine . And when app weirdness arrives alongside hardware symptoms — say a MIPI camera driver error on your AI laptop — treat the driver layer as a suspect too, since broken drivers can destabilize dependent apps.

Why this happens

  • Emulated instead of native build: an x64 Outlook under emulation is slower and crash-prone on Arm.
  • Damaged WebView2 runtime: the shared renderer behind Outlook’s UI is corrupted or outdated.
  • Corrupted local cache: bad sync state for one folder freezes or crashes the whole app.
  • Oversized mailbox cache: very large cached mailboxes exhaust the app’s memory on first sync.
  • Authentication drift: expired tokens or changed passwords break sync silently.
  • Conflicting policies or add-ins: work tenant policies or leftover add-ins block the new client.
  • Windows update mismatch: missing cumulative updates leave system components the app expects.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm you are running the native Arm64 build

Open Task Manager while Outlook runs, find the Outlook process, and check its architecture column. If it shows x64 on an Arm laptop, you are running the emulated build — uninstall it and reinstall from the Microsoft Store, which serves the native Arm64 package. The native build starts faster, uses less battery, and crashes far less.

  1. Open Task Manager with Ctrl+Shift+Esc and go to Details.
  2. Find the Outlook process and check the Architecture column.
  3. If it shows x64, uninstall Outlook and reinstall from the Microsoft Store.
  4. Verify the fresh install shows Arm64 in Task Manager.

Fix 2: Re-authenticate your accounts

Sync failures that look like app bugs are often just expired credentials. In Outlook settings, open Accounts and check each account’s sync status. Remove and re-add any account showing errors — this forces a fresh token and a clean sync handshake. If your organization recently enforced a password change, every account may need this at once.

  1. In new Outlook, open Settings, then Accounts.
  2. Note any account showing a sync error or warning.
  3. Remove the problem account, then re-add it with current credentials.
  4. Wait for the initial sync to complete before judging.

Fix 3: Repair or reset the Outlook app

When the app crashes on launch or freezes constantly, its local data is the prime suspect. Windows offers Repair (keeps your data) or Reset (wipes local cache and settings, resyncs from the server). Since mail lives on the server, Reset is safe — just send offline drafts first. Reset is the most reliable cure for crash-on-startup. The official support hub documents these Store app repair steps.

  1. Open Settings, then Apps, then Installed apps.
  2. Find Outlook (new), open its menu, and choose Advanced options.
  3. Click Repair, wait, and test the app.
  4. If crashes persist, click Reset, confirm, reopen, and sign in.

Fix 4: Reinstall the WebView2 runtime

The new Outlook draws its entire interface through WebView2. A damaged runtime produces blank panes, white flashes, and hard freezes when switching folders. If Teams or Copilot show similar rendering glitches, WebView2 is almost certainly the shared cause. Uninstall the runtime and install the Evergreen Standalone version from Microsoft, then restart.

  1. In Installed apps, uninstall Microsoft Edge WebView2 Runtime.
  2. Download the Evergreen Standalone Installer from Microsoft’s official site.
  3. Run the installer and restart your laptop.
  4. Open Outlook and test folder switching and composing.

Fix 5: Shrink the sync load and check for policy blocks

If Outlook works but is painfully slow, reduce what it must chew through. In settings, shorten the mail sync window to the last few months so the initial sync finishes quickly. On work machines, ask IT whether a tenant policy restricts the new Outlook — some organizations block it until migration testing finishes, which no local fix can overcome. Disable nonessential add-ins while testing.

  1. In Outlook settings, find the sync or offline settings.
  2. Reduce the mail download window to recent months.
  3. Disable add-ins you do not recognize or need.
  4. Ask IT whether the new Outlook is approved for your tenant.

Fix 6: Clean reinstall plus Windows Update

As the last resort, fully uninstall Outlook, restart the laptop to release locked cache files, reinstall from the Store, and run Windows Update to bring system components current. On Arm laptops, also check the manufacturer’s support page for chipset or firmware updates. After reinstalling, add one account at a time and confirm each syncs before adding the next.

  1. Uninstall Outlook (new) from Installed apps and restart the laptop.
  2. Reinstall from the Microsoft Store.
  3. Run Windows Update and install everything pending.
  4. Add accounts one at a time, verifying each syncs.

Closing

New Outlook on Arm is a good app running on a demanding stack: native Arm64 build, healthy WebView2, clean sync data. Get those three right and the crashes and freezes almost always stop. Keep the Store’s auto-updates enabled so the app and its components stay current together, and remember the classic Outlook toggle as your safety net — there is no shame in using it while a stubborn issue gets sorted. If a clean reinstall on a fully updated system still fails, involve Microsoft support with crash timestamps in hand.

Frequently asked questions

Is there a native Arm64 version of the new Outlook?
Yes. The new Outlook ships as a native Arm64 app through the Microsoft Store, which should install automatically on Snapdragon laptops. Problems arise when an emulated x64 build gets installed instead, or when WebView2 is damaged. Checking which architecture you run is a worthwhile early step.
Why does new Outlook freeze when I switch folders?
Folder-switch freezes are usually sync or rendering stalls. A mailbox with a huge cache, a stuck sync on one folder, or a damaged WebView2 runtime can each freeze the UI for seconds. Clearing the app cache and repairing WebView2 resolve most of these pauses.
Can I go back to classic Outlook if the new one keeps failing?
Yes, the toggle in the new Outlook switches back to classic Outlook, provided classic Outlook is installed with your Microsoft 365 subscription. This is a legitimate fallback while you troubleshoot, not a defeat. Many IT departments keep both available during the transition.
Will resetting the app delete my emails?
No. New Outlook is a window onto your mailbox, which lives on the server. Resetting only removes local cache and settings; emails, calendar, and contacts resync afterward. Offline-only drafts are the one exception, so send or save those first.