Windows  ·  medium  ·  Applications & Microsoft 365

Teams will not load, shows a white screen, or is stuck signing in

The local cache or the token it holds has become inconsistent. Teams has no repair path, so the cache is cleared instead.

What you see

A white or blank window, a permanent loading spinner, or a sign-in loop that never completes. Chats may be missing or out of date.

What is actually wrong

A corrupt cache after an interrupted update, a token issued before a conditional access policy changed, or a WebView2 runtime that has been damaged or removed.

Codes and articles

Teams white screencaa20004caa700040xCAA20003We're sorry—we've run into an issue

Fixes (2)

Reset the new Teams and its WebView2 runtime
PowerShell as the affected user25 minutesmedium riskreversible

The Store-based Teams. It is a packaged app, so it resets differently from the old one.

  1. Close Teams completely.

    PowerShell
    Get-Process ms-teams,msedgewebview2 -ErrorAction SilentlyContinue | Stop-Process -Force

  2. Confirm which package is installed.

    PowerShell
    Get-AppxPackage -Name MSTeams | Format-List Name,Version,InstallLocation,Status

  3. Reset the package, which clears its cache without uninstalling it.

    PowerShell
    Get-AppxPackage -Name MSTeams | Reset-AppxPackage

    Reset-AppxPackage is the supported way to clear a packaged app's state. Deleting folders under Packages by hand can leave the package registered but broken, which is much harder to recover from.

  4. Check the WebView2 runtime is present and current — the new Teams is drawn entirely by it.

    PowerShell
    Get-ItemProperty HKLM:\Software\WOW6432Node\Microsoft\EdgeUpdate\Clients\* -ErrorAction SilentlyContinue |  Where-Object pv -and $_.name -like '*WebView*' | Format-List name,pv

  5. Reinstall the Evergreen WebView2 runtime from Microsoft if it is missing or the version is old.

Confirm it workedTeams opens to the chat list and the account is signed in.
If you need to undo itA reset returns the app to a clean state; chat history is stored in the service, not locally.
Clear the classic Teams cache
PowerShell as the affected user20 minutesmedium riskreversible

Classic Teams, which stores its cache in the user profile.

  1. Close Teams from the notification area and confirm no process remains.

    PowerShell
    Get-Process Teams -ErrorAction SilentlyContinue | Stop-Process -Force

  2. Clear the cache directories.

    PowerShell
    $t = "$env:APPDATA\Microsoft\Teams"'blob_storage','Cache','Code Cache','databases','GPUCache','IndexedDB','Local Storage','tmp' |  ForEach-Object { Remove-Item "$t\$_" -Recurse -Force -ErrorAction SilentlyContinue }

    These are the directories that hold the rendered state and the local database. Deleting the whole Teams folder also removes the settings and the desktop configuration, which is more disruptive than necessary.

  3. Clear the Teams credential entries.

    PowerShell
    cmdkey /list | ForEach-Object { if ($_ -match 'Target:\s*(\S*[Tt]eams\S*)') { cmdkey /delete:$($Matches[1]) } }

  4. Start Teams and sign in. The first start after a cache clear is slow.

Confirm it workedTeams loads to the chat list within a minute or two and stays signed in after a restart.
If you need to undo itThe cache rebuilds itself. Nothing that only exists locally is lost.

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.