How to Fix ‘We’re Sorry—We’ve Run into an Issue’ in Microsoft Teams

Launching the Microsoft Teams desktop client on Windows 11 is designed to connect seamlessly to your corporate or educational tenant. However, users frequently encounter an immediate application startup crash displaying a white splash window and the error: ‘We’re sorry—we’ve run into an issue’, accompanied by a Restart button and an option to Sign out. Clicking Restart simply reloads the same error loop, while signing out and back in fails to break the cycle. This persistent problem occurs due to damaged Web Account Manager (WAM) authentication tokens, corrupted Edge WebView2 runtime data, or stale local configuration caches.

Why Does Microsoft Teams Crash with ‘We’ve Run into an Issue’?

Modern Microsoft Teams (built on WebView2 and React) relies on Windows identity subsystems for single sign-on (SSO). The crash loop typically stems from:

  • Corrupted Web Account Manager (WAM) Tokens: Damaged authentication tokens stored in the Windows Identity repository preventing Teams from completing background OAuth handshakes.
  • Stale Local AppData Cache: Corrupted JSON configuration files or damaged IndexedDB records inside the local Teams application directory.
  • Corrupted Microsoft Edge WebView2 Runtime: Teams uses the WebView2 engine to render its entire interface; damaged WebView2 user profiles prevent UI rendering.
  • Workplace / School Account Disconnects: A password change or multi-factor authentication (MFA) reset on Microsoft 365 leaving Windows with invalid cached credentials.
  • Conflicting VPN or TLS Proxy Filters: Enterprise security software or proxy filters intercepting internal authentication certificates.

Step 1: End All Running Teams Processes in Task Manager

Background Teams helper processes often remain stuck in memory, preventing clean restarts.

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. In the Processes tab, look for Microsoft Teams.
  3. Right-click Microsoft Teams and select End task.
  4. Scroll down to the Background processes section and ensure no lingering instances of ms-teams.exe or Teams.exe are active.

Step 2: Reset and Repair the New Microsoft Teams App in Windows 11

For the New Teams app distributed via the Microsoft Store / MSIX package, Windows 11 provides a built-in repair utility that clears corrupt local runtime data.

  1. Press Windows Key + I to open Settings.
  2. Navigate to Apps > Installed apps.
  3. In the search box, type Microsoft Teams.
  4. Click the three horizontal dots next to Microsoft Teams (or Microsoft Teams (work or school)) and choose Advanced options.
  5. Scroll down to the Reset section and click the Repair button first. Wait for the tick mark.
  6. If the issue persists upon launching Teams, return to this menu and click the Reset button. Resetting wipes local cached session data without deleting your chat history or files stored on SharePoint and OneDrive.

Step 3: Manually Purge the Teams AppData Cache

If using classic Teams or if the New Teams client continues to display the error, deleting the local cache directory forces a fresh configuration rebuild.

  1. Ensure Microsoft Teams is fully closed.
  2. Press Windows Key + R to open the Run dialogue.
  3. For the New Teams app, type the following path and press Enter:
    %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache
  4. Delete all files and folders inside the LocalCache directory.
  5. For Classic Teams, type:
    %appdata%\Microsoft\Teams
  6. Select all folders (including blob_storage, Cache, databases, GPUCache, IndexedDB, Local Storage, and tmp) and press Delete.
  7. Relaunch Teams and sign in with your credentials.

Step 4: Disconnect and Reconnect Your Work or School Account

Refreshing the Windows single sign-on profile resolves stale token handshakes across Microsoft 365 apps.

  1. Open Settings > Accounts > Access work or school.
  2. Locate your organisation email account listed under the active connections.
  3. Click on your account and select Disconnect. Confirm the prompt.
  4. Reboot Windows 11.
  5. Return to Settings > Accounts > Access work or school, click Connect, and enter your corporate or school login details.
  6. Launch Microsoft Teams. The client will authenticate automatically using the refreshed Windows credentials.

Step 5: Reinstall Microsoft Edge WebView2 Runtime

If the underlying rendering engine is damaged, reinstalling WebView2 restores client stability.

  1. Open your browser and navigate to the official Microsoft Edge WebView2 download portal.
  2. Download the Evergreen Bootstrapper installer.
  3. Right-click the downloaded file and select Run as administrator.
  4. The installer will verify and repair corrupted WebView2 binaries automatically.
  5. Reboot your computer and launch Teams.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.