Teams Stuck on Loading: Diagnosing Where in the Pipeline It’s Failing

Quick answer

When Teams hangs on the loading screen, the right fix depends on where in the sign-in pipeline it’s stuck. There are four points it can stall: before authentication (the loader sits on the splash screen), during authentication (after a sign-in prompt or silently, if it’s using cached credentials), after authentication but before content loads (you see your name but no chats), and after content but with a permanent “reconnecting” state. Each one is a different bug with a different fix, and most online guides skip the diagnostic step entirely.

Before you start

Three things to rule out before any troubleshooting:

Check Microsoft 365 service health. A surprising fraction of “Teams stuck on loading” reports correlate with Microsoft-side outages. Open teams.microsoft.com in a browser. If web Teams is also stuck — and you’re on a different network than your work network — it’s Microsoft’s problem, not yours. The Microsoft 365 Service health dashboard shows current incidents (admin sign-in required) and the public @MSFT365Status feed flags major outages.
Try web Teams. If the desktop client is stuck but the web version loads fine, the desktop client cache or install is the problem. If both are stuck, your account or your network is the problem.
Make sure you have time for this. A full Teams reset on a slow machine can take 20+ minutes. If you have a meeting in five minutes, join it from web Teams and troubleshoot the desktop client later.

Where exactly is Teams stuck?

This is the diagnostic step that determines everything else. Watch what’s actually on the screen and identify which stage it’s stuck at.

Stage	What you see	Most likely cause
Pre-auth	Teams splash screen, no sign-in prompt, no progress	Conditional access blocking, broken WAM plugin, certificate trust issue
Auth	Sign-in prompt that won’t accept credentials, or credentials accepted but the sign-in window won’t close	MFA loop, conditional access, wrong account state
Post-auth, pre-content	Your name and avatar visible, but chats and channels never appear	Modern Auth handshake broken, cache corruption, region routing
Reconnecting / partial load	Some chats load, some don’t; persistent “reconnecting” banner; teams list incomplete	Network instability, proxy interference, presence service down

Take a moment to identify which stage. The wrong fix is just churn; the right fix often takes a single command.

Common causes

Mapped to the stage they affect:

Pre-auth stalls are usually about identity. Conditional access policies that don’t trust the device, WAM plugin corruption, expired certificate chains, or a domain-joined machine that’s lost its Entra ID registration. If you also see error codes CAA50021 or 80090016, that confirms the pre-auth diagnosis and points you at specific fixes.

Auth stalls include MFA prompt loops, conditional access policies that block the device type, or a stale session token where Windows thinks you’re signed in but Teams doesn’t agree.

Post-auth, pre-content stalls are mostly client-side: corrupted local cache, an in-progress mailbox migration, or a tenant in a region that’s having latency issues. Less commonly, it’s a Teams policy assignment that doesn’t have a configuration for your account yet.

Reconnecting stalls are usually network — proxy interference, deep packet inspection breaking WebSocket connections, VPN routing weirdness, or DNS issues that affect the Microsoft 365 endpoints Teams needs.

Fixes to try first

If Teams is stuck pre-auth

This is the case where the splash screen sits there indefinitely with no sign-in prompt.

1. Force-quit Teams and try again. Right-click the Teams system tray icon → Quit. Open Task Manager (Ctrl+Shift+Esc) and end any ms-teams.exe or Teams.exe processes. Wait 10 seconds. Restart Teams. About 20% of pre-auth stalls clear with a clean restart.

2. Check whether sign-in works in Outlook or another Microsoft 365 app. If Outlook can sign in, the WAM plugin is fine and the problem is Teams-specific (skip to step 4 below). If Outlook is also stuck on sign-in, the broker plugin is broken — see the rename-the-WAM-folder fix in our Teams 80090016 guide and apply it here. The fix is the same.

3. Sign out of Windows entirely and back in. A full sign-out (not lock — sign-out) forces Windows to re-establish the account session. This sometimes resolves what looks like a Teams problem but is actually a Windows account state problem.

4. Disconnect and reconnect the work or school account. Open Settings > Accounts > Access work or school. Click your work account → Disconnect. Restart. Sign back in to Teams; let Windows offer to add the account back.

If Teams is stuck at the auth prompt

The sign-in window is open but credentials don’t take, or the window stays after you’ve signed in.

1. Sign in via Outlook or Office.com first. If you can sign in to Microsoft 365 elsewhere, that establishes the session that Teams will then pick up. Open Edge, go to office.com, sign in. Now restart Teams.

2. Use a private browser to test. Open Edge or Chrome in a private window, go to teams.microsoft.com, sign in. If web Teams works, the problem is with the desktop client’s authentication handler — clear its cache (next section).

3. Check for an MFA prompt offscreen. On multi-monitor setups, the MFA prompt sometimes opens on a disconnected monitor. Use Win+Arrow keys to cycle the focused window across monitors. If you find an MFA prompt that’s been waiting, complete it.

4. Clear stored Teams credentials. Open Control Panel > User Accounts > Credential Manager > Windows Credentials. Delete entries starting with MicrosoftAccount:user=, MicrosoftOffice16_Data:, or msteams_*. Restart Teams and sign in fresh.

If Teams is stuck post-auth

You can see your account but content doesn’t load.

1. Clear the Teams cache. This is the fix that works for most post-auth stalls. Quit Teams completely. Open File Explorer and paste this into the address bar:

%LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

Delete the contents of that folder (not the folder itself). Restart Teams. It will redownload the local cache. Note: if that path doesn’t exist, you may be on classic Teams (the older app, deprecated). The classic Teams cache path is %appdata%\Microsoft\teams — but if you’re on classic in 2026 you should also be migrating to new Teams.

2. Reset Teams from Windows Settings. Open Settings > Apps > Installed apps. Find Microsoft Teams, three-dot menu → Advanced options > Reset. This clears all app data and signs you out. You’ll need to sign in again. Heavier than the manual cache delete but more reliable.

3. Check whether your mailbox is being migrated. If your tenant is mid-migration to a different Microsoft 365 region, Teams content can stall for hours. Sign in to outlook.office.com — if you see a banner about a mailbox move, that’s your answer. Wait it out (or work in web Teams meanwhile).

If Teams keeps reconnecting

You can use Teams briefly, then it loses connection. Or it shows “reconnecting” persistently.

1. Test against the Microsoft 365 connectivity test. Microsoft maintains a Network Connectivity Test that specifically checks the endpoints Teams uses. Run it from the affected machine. It will tell you whether your network is interfering with Teams’ connection.

2. Bypass the proxy temporarily. If you’re on a corporate network, your proxy may be doing deep packet inspection that breaks Teams’ WebSocket connections. Try a personal hotspot for two minutes. If Teams works on the hotspot but not the corporate network, the proxy or firewall is the issue — that’s an admin fix, not a user fix.

3. Disable QUIC if your firewall blocks it. Open Edge → edge://flags, search for Experimental QUIC protocol, set to Disabled. Restart Edge. Restart Teams. Same logic applies to Chrome under chrome://flags. If your corporate firewall doesn’t allow QUIC, forcing TCP-only fallback can stabilise Teams.

4. Check VPN behavior. If you’re on a VPN, test off the VPN briefly. Some VPN clients route Microsoft 365 traffic incorrectly and Teams reconnection logic gives up. If Teams works off the VPN, your IT team can split-tunnel Microsoft 365 traffic — there’s a Microsoft documentation page on this that’s worth sharing with them.

Advanced fixes

If none of the above worked, you’re at the reinstall-or-escalate point.

Reinstall Teams. For new Teams (the version you almost certainly have): open Settings > Apps > Installed apps, find Microsoft Teams, three-dot menu → Uninstall. Open the Microsoft Store, search for Microsoft Teams, install. Sign in. Cache is fresh; install is fresh.

Re-register the device with Entra ID. If your machine has lost its Entra ID device registration, conditional access policies will block sign-in. Run this from an elevated command prompt:

dsregcmd /status

Read the output. If “AzureAdJoined” or “DomainJoined” is NO when it should be YES, you need to re-establish the device join. On a managed device, this is usually an admin task.

Reset the network stack. As a last resort for “reconnecting” stalls, run these in an elevated command prompt:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Restart. This clears any corrupted network state. Don’t run these unless connectivity issues persist across multiple Microsoft apps — they affect all networking, not just Teams.

If you are on a work or school device

Most of the fixes above are safe on managed devices. The exceptions:

Disconnecting and reconnecting the work account can break conditional access registration. On a managed device, prefer the cache reset (less disruptive) before account disconnection.
netsh winsock reset may clear corporate VPN client state. Don’t run it without a fallback if you depend on the VPN to access internal resources.
Re-registering with Entra ID typically requires admin rights or a specific Intune-pushed remediation. Open a ticket rather than improvising.

If multiple users in your organization are stuck on the loading screen at the same time, the issue is tenant-side. Conditional access changes, mailbox migration, Intune policy assignments — all of these can cause synchronized symptoms. Stop troubleshooting locally and tell your admin.

If the loading stall correlates with CAA50021, that’s the conditional access flavour — see that article for the policy-side investigation.

When to stop

Stop and escalate when:

Teams reset (full uninstall and reinstall) hasn’t resolved the issue.
Web Teams works fine but the desktop client has been broken for more than an hour after a fresh reinstall.
Multiple users on the same network show the same symptom.
dsregcmd /status shows the device is not properly registered with Entra ID and you don’t have admin rights to fix that.
You’ve started seeing other Microsoft 365 sign-in errors alongside the loading stall (Outlook signing in repeatedly, OneDrive disconnecting). That points at an account or tenant-level problem, not a Teams problem.

Don’t keep deleting cache folders in a loop hoping for a different result. Don’t follow guides that recommend running scripts from random forum posts as administrator — Teams troubleshooting has well-documented Microsoft fixes; nothing on a forum requires elevated PowerShell.

CAA50021 in Teams — appears alongside loading stalls when conditional access is the underlying cause.
Teams Error 80090016: TPM Has Malfunctioned — when the loading stall is actually the WAM plugin failing.
Microsoft 365 Error CAA50021 — the parent code hub if loading stalls span multiple Microsoft 365 apps.

Official references

FAQ

Why does Teams web work but the desktop app stays stuck? The desktop app caches state locally; the web app doesn’t. If web works and desktop doesn’t, the desktop client’s local data is corrupted — clearing the cache or resetting the app fixes it. The account, network, and tenant are all fine.

How long should I wait before assuming Teams is genuinely stuck? On a working machine, Teams loads in under 30 seconds — splash, sign-in (if needed), content. If you’ve waited two minutes with no progress, it’s stuck. Waiting longer rarely helps.

Should I delete the entire Teams folder under AppData? No. The Settings → Reset option does the same thing in a controlled way and won’t break anything. Manually deleting %appdata%\Microsoft\teams (classic Teams) or the new Teams package folder (new Teams) is fine if Settings → Reset isn’t available, but be aware that other apps occasionally write configuration to those folders.

My company uses single sign-on. Does that change anything? Yes. With SSO, Teams expects to silently authenticate using your Windows session. If the Windows session has lost its Entra ID device trust (dsregcmd /status shows AzureAdJoined: NO), Teams will hang on sign-in because it never sees a credential prompt. The fix is to restore the device join, which usually requires admin involvement.

Why did Teams suddenly start being stuck after a Windows Update? Windows feature updates regularly damage the Web Account Manager broker plugin. The fix is to rename the broker folder — see our 80090016 guide, which documents the same fix because it’s the same underlying problem.

Will reinstalling Teams delete my chat history? No. Chat history is stored on Microsoft’s servers, not in the local app. When you reinstall and sign in, your chats download again. The only thing you lose is unsent draft messages and local meeting recordings if you had them stored locally.

Can I just use Teams on the web permanently? You can. Trade-offs: no system tray presence, weaker desktop notifications, no native screen-sharing for some scenarios, slightly slower. Acceptable for occasional use; not ideal as a primary client.

↑ Back to top