Microsoft Teams not loading — stuck on the loading screen, crashing immediately after opening, showing a blank white window, or a grey screen with a spinner that never resolves — is one of the more common enterprise software issues in Windows 11. The fix is almost always cache-related or a Teams update problem. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
Before doing anything complex: completely close Teams (right-click the system tray icon → Quit, not just X the window) → wait 5 seconds → reopen. Teams sometimes gets stuck in a bad state that clears with a proper restart. If it loads after a full quit and reopen: the session state was corrupted. If it’s stuck again within the same session: proceed to the fixes below.
Clear the Teams cache — solves most loading failures
Teams caches authentication tokens, meeting data, and app state locally. When this cache becomes corrupted: Teams loads partially then stops, loops on the loading screen, or shows a blank window. Clearing the cache forces Teams to rebuild from scratch.
Close Teams completely (Task Manager → end all Teams.exe processes) → navigate to:
%appdata%MicrosoftTeams
Delete the contents of these specific subfolders (not the folders themselves):
Cacheblob_storagedatabasesGPUCacheIndexedDBLocal Storagetmp
Restart Teams. It rebuilds the cache on launch — first load takes 30-60 seconds as data is re-fetched. This resolves loading failures in the majority of cases.
New Teams vs Classic Teams
Microsoft has two versions: “Classic Teams” (the original Electron-based app) and “New Teams” (rebuilt on WebView2, faster but had stability issues in earlier releases). If one version is failing: try the other. In Teams: click the three dots → Settings → General → “Switch to Classic Teams” or vice versa. New Teams is now the default and generally more stable in current versions; if you’re stuck on Classic Teams with issues: switching to New Teams often resolves loading problems.
Sign-out and sign-in to reset authentication
Teams’ authentication token can expire or become corrupted, causing the app to loop on “Signing you in…” indefinitely. If Teams gets past the loading screen but stalls at authentication: Teams → profile picture → Sign out → close Teams fully → reopen → sign in fresh. This forces a new authentication token without clearing other settings.
For persistent authentication failures: also clear the Windows Credential Manager entries for Teams. Control Panel → Credential Manager → Windows Credentials → remove any entry containing “msteams” or “microsoftteams” → restart Teams → sign in again.
Update Teams and Windows
An outdated Teams version may have compatibility issues with the current Windows 11 update or Microsoft 365 services. Teams → three dots → Check for updates → install any pending update → restart. Also: Settings → Windows Update → install all pending updates → restart Windows. Microsoft frequently pushes Teams fixes in both app updates and cumulative Windows updates.
Teams and corporate policies
Enterprise Teams deployments are managed through Microsoft 365 admin center, Intune, or Group Policy. If Teams stopped loading after a policy change or on a new device: the issue may be policy-enforced configuration. Signs: Teams loads on a personal machine but not on the work device, or Teams shows “We’re sorry — we’ve run into an issue” with error codes. IT manages these configurations; reporting to the help desk with the specific error code (Teams shows them at the bottom of some error screens) provides them with the information needed to diagnose policy-related failures.
Our guide on Teams audio and video issues covers the microphone and camera configuration within Teams once it’s loading. For authentication issues that affect Teams alongside other Microsoft 365 apps, our Microsoft 365 application guide covers the account and activation issues. Microsoft’s Teams troubleshooting documentation covers the Teams diagnostics tool (run Get-CsOnlineUser for IT admins), the Teams admin portal for user-level diagnostics, and the specific error codes that indicate license, policy, or service-side issues rather than local client problems.
Reinstall Teams cleanly
If cache clearing and authentication reset don’t resolve the loading failure: a full uninstall and reinstall provides the cleanest resolution. Teams installation is user-level rather than machine-level, which means uninstallation and reinstallation through Settings → Apps doesn’t require administrator rights.
- Settings → Apps → Microsoft Teams → Uninstall (do this for both “Microsoft Teams” and “Microsoft Teams Meeting Add-in for Microsoft Office” if listed)
- Delete the remaining data:
%appdata%MicrosoftTeams(entire folder) and%localappdata%MicrosoftTeams(entire folder) - Download the Teams installer from teams.microsoft.com or deploy via Microsoft 365 admin
- Install → sign in
The folder deletion step is critical — without it, Teams installation reuses the corrupted data from the previous installation, reproducing the same loading failure immediately.
Teams and antivirus interference
Antivirus real-time scanning occasionally interferes with Teams’ local database writes and cache updates, causing Teams to hang at loading while it waits for file operations that the antivirus has locked for scanning. Add Teams’ data folders to the antivirus exclusion list:
%appdata%MicrosoftTeams%localappdata%MicrosoftTeams%localappdata%MicrosoftTeamsMeetingAddin
These folders contain cached data that Teams has already scanned and verified — excluding them from ongoing real-time scanning reduces the antivirus load during Teams startup without reducing security for external file access.
Teams background processes
Teams runs multiple background processes even when the main window isn’t visible. After closing the Teams window: Teams helper processes (Teams.exe, Update.exe, Squirrel.exe) often continue running. These background processes can get into a stuck state that prevents Teams from loading cleanly when you try to open it again.
Ctrl+Shift+Esc → Task Manager → look for all Teams-related processes → right-click each → End task → then reopen Teams. This ensures a completely fresh Teams start without any inherited state from the previous session. For machines where Teams is used all day: restarting Teams completely once a day (quit from tray → reopen) prevents accumulated state issues.
WebView2 and New Teams
New Microsoft Teams is built on Microsoft Edge WebView2 rather than Electron (the framework used by Classic Teams). If WebView2 is missing, outdated, or corrupted: New Teams fails to load entirely. Settings → Apps → search “WebView2” → if not installed: download and install from microsoft.com/en-us/edge/webview2. If it’s installed but Teams still fails: uninstall WebView2 → reinstall it → then reinstall Teams. The dependency on WebView2 means Teams loading issues can sometimes be resolved by fixing WebView2 rather than Teams itself.
Teams in browser as a fallback
When the Teams desktop app won’t load: teams.microsoft.com in a browser (Chrome or Edge) provides full Teams functionality without installing anything. The browser version has minor limitations (some meetings features, background blur, device access on some browsers) but handles most everyday tasks — chat, file sharing, meeting attendance — reliably. Using the browser version while troubleshooting the desktop app maintains productivity rather than waiting for the desktop app to be fixed before participating in meetings.
Hardware-accelerated GPU scheduling and Teams
Teams uses GPU rendering for some UI elements. On machines where HAGS (Hardware-Accelerated GPU Scheduling) causes conflicts with Teams’ rendering: the app may show a blank grey window or crash during rendering. Settings → System → Display → Graphics → “Hardware-accelerated GPU scheduling” → try toggling this setting → restart Teams. Some GPU and driver combinations are better or worse with HAGS enabled for Teams specifically.
Teams error codes reference
| Error code / message | Cause | Action |
| caa30190 / caa30194 | Authentication failure | Sign out → clear credentials → sign in fresh |
| caa70004 | Cached token mismatch | Clear Teams cache; sign out and back in |
| 0xCAA80000 series | Network or proxy blocking | Check firewall; verify Teams URLs are whitelisted |
| You’re missing out! | Account type mismatch (personal vs work) | Sign in with the correct Microsoft account type |
| We’re sorry — we’ve run into an issue | Service or policy issue | Contact IT; check Microsoft 365 service health dashboard |
Teams loading failures are almost always resolved by the cache clear and full quit/restart sequence. The error code reference turns what looks like a generic failure into a specific, addressable issue — caa30190 points directly to authentication, 0xCAA80000 points to network. For enterprise deployments: the error code combined with the IT team’s access to the Microsoft 365 admin center provides precise diagnosis without relying on local troubleshooting alone.
Teams and Outlook calendar integration
If Teams loads but the calendar shows “Loading your calendar…” indefinitely: the Exchange or Microsoft 365 calendar integration has a configuration issue. This is separate from Teams’ general loading problem and usually involves the user’s Exchange Online mailbox settings. Signing out of Teams → clearing credentials → signing back in with the work account (not personal Microsoft account) often resolves calendar loading stalls. If the calendar continues to fail after fresh sign-in: IT needs to check the Exchange Online permissions and the Teams-Exchange integration settings for the specific account.
Teams log files for advanced troubleshooting
Teams generates detailed logs in %appdata%MicrosoftTeamslogs.txt. This file records all Teams activity including authentication attempts, API calls, and error conditions. When Teams fails to load in a way that doesn’t produce a visible error code: the logs.txt file often contains the specific error. Share this file with IT or search its contents for “ERROR” or “WARN” lines that correspond to the time Teams was failing to load. Teams also has a built-in diagnostic: Ctrl+Alt+Shift+1 while Teams is running (even if it appears to be loading) → Teams generates a diagnostic report to %userprofile%DownloadsMSTeams Diagnostics Log that includes system information, network state, and error details.
Teams via Intune and managed devices
On devices managed through Microsoft Intune: Teams is often deployed and updated through Intune policies rather than the Microsoft Store or direct download. If Teams fails to load on a newly enrolled device or after a compliance policy change: Intune may need to re-push the Teams installation, or the enrollment itself may not have completed correctly. Check the Company Portal app (installed on Intune-managed devices) for any pending actions or compliance issues that may be blocking Teams from running correctly.
A common scenario in hybrid work environments: Teams was working fine until someone replaced their laptop and tried to reinstall. On the new machine, Teams downloads, installs, and then fails to load — showing a blank screen or getting stuck at authentication. This usually happens because the Microsoft 365 account has a sign-in restriction (conditional access policy requiring a compliant device) and the new device isn’t yet compliant. Enrolling the device in Intune/Azure AD through the Company Portal app → passing the compliance check → then opening Teams resolves this without any Teams-specific troubleshooting needed. The issue isn’t Teams — it’s the device’s compliance status with the organisation’s access policy.
For IT administrators managing Teams at scale: the most efficient approach to Teams loading failures across multiple users is checking the Microsoft 365 service health dashboard (admin.microsoft.com → Health → Service health) first. Many “Teams not loading” reports during a specific time window are caused by a Microsoft-side service incident rather than local client issues. During service incidents: no amount of local cache clearing or reinstallation resolves the problem, and waiting for Microsoft to resolve the service issue is the only action available. Having users check the service health status themselves (via the Microsoft 365 status page: status.office365.com) reduces support ticket volume during service incidents by helping users understand when the fix isn’t in their hands.
The Teams loading failure has a reliable resolution path that works for the vast majority of cases: full process quit → cache folder cleanup → fresh sign-in. The complete reinstall (with folder deletion) handles the cases that the cache clear doesn’t. WebView2 installation handles New Teams failures that aren’t cache-related. These three steps cover perhaps 95% of “Teams won’t load” situations. The error code table and logs.txt file provide the diagnostic information for the remaining cases where Teams fails for reasons that are account, policy, or service-specific rather than local client issues.
One practical tip for Teams users who deal with loading issues frequently: enabling Teams’ “Background effect” and setting up the account before the first meeting of the day gives Teams time to fully initialise rather than opening it just as a meeting starts. Teams takes 30-60 seconds to fully load and synchronise after opening — notifications, chats, and calendar all need to update. Opening Teams 2-3 minutes before a meeting ensures everything is ready and reduces the chance of discovering a loading problem with 30 seconds before the call begins.
Teams’ evolution from Classic to New Teams has introduced both improvements and new failure modes. Classic Teams had the benefit of being a well-established Electron application with years of Windows compatibility work; New Teams, while faster and more efficient, introduced WebView2 dependency and new cache architecture that required its own troubleshooting patterns. If you’re experiencing loading failures: identifying which Teams version you’re on (classic vs new) is the first step, as the cache locations, error messages, and fixes differ between them. New Teams cache is at %localappdata%PackagesMSTeams_8wekyb3d8bbwe for the Store version; Classic Teams is at %appdata%MicrosoftTeams as documented above. See also Microsoft Teams Not Opening for a related case.
