When you switch between work or school tenants in Teams, the app sometimes shows a blank white window. This happens after you sign out of one tenant and sign into another, or when you use the account switcher. The blank window usually appears because the Teams desktop client keeps cached data from the previous tenant session. This article explains why the cache and authentication tokens cause the problem, and shows you how to clear them to get Teams working again.
You will learn the exact steps to clear the Teams cache, reset the app, and check for policy issues that can trigger the white screen. The fixes work for both Windows 11 and Windows 10. After following the steps, you can switch tenants without seeing a blank window.
Key Takeaways: Clearing the Teams Cache to Fix the White Screen on Tenant Switch
- Clear the Teams cache folder (%appdata%\Microsoft\Teams): Deletes corrupted local data that causes the blank white window after tenant switching.
- Sign out and sign back in (Teams > your profile > Sign out): Forces a fresh authentication token request from the new tenant.
- Teams admin center > User policies > App setup policy: Verify that the policy does not block the app or restrict tenant switching.
Why Teams Shows a Blank White Window After Switching Tenants
The blank white window occurs because Teams stores a local cache that includes authentication tokens, profile data, and UI state for each tenant. When you switch tenants, Teams tries to reuse this cache. If the cached data is corrupted or contains tokens from the previous tenant, the app cannot load the new tenant’s interface. The result is a white screen with no content.
Another cause is a conflict between the Teams desktop client and the Windows Credential Manager. The app may hold onto a token that belongs to the old tenant. When you sign in to the new tenant, the client attempts to validate the old token, fails, and does not render the UI.
How the Cache Works in Teams
Teams stores several folders in the %appdata%\Microsoft\Teams directory. The Cache, Code Cache, and GPUCache folders hold temporary files. The IndexedDB folder stores database files for the app. When you switch tenants, Teams reads these folders. If any file is corrupted, the app can freeze on a blank window.
Why Signing Out Does Not Always Fix It
Signing out removes the current user session but does not delete the cached files. The next sign-in reads the same corrupted cache. That is why the white screen persists even after you sign out and back in.
Steps to Clear the Teams Cache and Reset the App
Follow these steps in order. The first method clears the cache. The second method resets the app completely. The third method checks your tenant policy.
Method 1: Clear the Teams Cache Manually
- Close Teams completely
Right-click the Teams icon in the system tray and choose Exit. Then open Task Manager with Ctrl+Shift+Escape and end any Teams processes that remain. - Open the Teams cache folder
Press Win+R, type %appdata%\Microsoft\Teams, and press Enter. This opens the Teams data folder. - Delete the cache subfolders
Select and delete these folders: Cache, Code Cache, GPUCache, and IndexedDB. Do not delete the whole Teams folder because that removes your settings and accounts. - Relaunch Teams
Start Teams from the Start menu. The app will rebuild the cache with fresh data. Sign in to your new tenant.
Method 2: Reset Teams Using the Windows Settings App
- Open Windows Settings
Press Win+I and go to Apps > Installed apps. Find Microsoft Teams in the list. - Choose Advanced options
Click the three-dot menu next to Teams and select Advanced options. - Click Reset
Scroll down and click the Reset button. Confirm the action. This clears all local data, including the cache and sign-in information. - Sign in again
Launch Teams and sign in to the tenant you want. The blank window should no longer appear.
Method 3: Verify Your Tenant Policy in the Teams Admin Center
- Open the Teams admin center
Go to admin.teams.microsoft.com in a browser and sign in with your administrator account. - Check the app setup policy
Go to Teams apps > Setup policies. Select the policy that applies to your user. Make sure the Teams app is not blocked and that the policy allows the app to load. - Check the tenant switching setting
Go to Users > Manage users, select the affected user, and open the Policies tab. Confirm that the user has access to the Teams app and is not restricted from switching tenants.
If Teams Still Has Issues After Clearing the Cache
Teams Still Shows a Blank Window After Signing In
If the white screen appears after you sign in, the problem may be a corrupted Teams installation. Uninstall Teams from Windows Settings, then reinstall it from the Microsoft 365 portal. This replaces all app files.
Teams Opens but Shows a White Screen When Switching Accounts
This usually means the account switcher has stale profile data. Use the account switcher in the top-right corner, choose Sign out, and then sign in with the other account. Clear the cache again if the white screen returns.
Teams Shows a Blank Window Only on a Specific Tenant
The tenant itself may have a policy that blocks the Teams app. Check the tenant’s app permission policy in the Teams admin center. Go to Teams apps > Permission policies and verify that the policy allows Microsoft Teams.
New Teams Desktop vs Teams on the Web for Tenant Switching
| Item | New Teams Desktop | Teams on the Web |
|---|---|---|
| Cache location | Local appdata folder | Browser cache and cookies |
| Tenant switching behavior | May reuse stale tokens | Uses browser session per tab |
| Fix for blank window | Clear appdata cache or reset app | Clear browser cache or use incognito mode |
| Performance | Better for heavy use | Depends on browser memory |
If the blank window persists after clearing the desktop cache, try Teams on the web as a temporary workaround. Sign in to the new tenant in a browser and use the web app until the desktop client is repaired.
After you clear the cache and reset the app, Teams should load the new tenant correctly. If you switch tenants often, consider using Teams on the web for the second tenant to avoid cache conflicts. As an advanced tip, use the keyboard shortcut Ctrl+Shift+M to mute or unmute during a meeting, which confirms the app is fully loaded after the fix.