How to Reset Microsoft Teams Cache in Windows
A simple step-by-step guide to reset the New Microsoft Teams app in Windows when Teams is slow, stuck loading, or behaving unexpectedly.
When Microsoft Teams gets stuck loading, feels unusually slow, stops refreshing chats, or keeps showing odd sign-in behavior, the local Teams cache can be the reason. Resetting the New Microsoft Teams app clears that local app data so Teams can rebuild a fresh working cache the next time it opens.
This is a safe first troubleshooting step for many common Teams issues. It does not delete your Teams chats, meetings, channels, or cloud files. Those remain stored in Microsoft 365.
This guide follows Microsoft guidance for clearing the cache in New Teams on Windows. Reference: Clear the Teams client cache.
Before You Begin
- You will be signed out of Microsoft Teams and will need to sign back in.
- Some local Teams preferences may be removed.
- Your chats, files, meetings, and Teams cloud data are not deleted.
- The first launch after the reset may take a little longer while Teams rebuilds its cache.
Reset Microsoft Teams from Windows Settings
- Quit Microsoft Teams completely. Right-click the Teams icon in the taskbar notification area near the clock, then select Quit.
- Open Windows Settings. Press the Windows key or click Start, then choose Settings.
- Go to Apps > Installed apps. This is where Windows lists apps that can be repaired or reset.
- Search for Microsoft Teams. Choose the New Microsoft Teams app, usually listed simply as Microsoft Teams.
- Open Advanced options. Select the three-dot menu beside Microsoft Teams, then choose Advanced options.
- In the Reset section, select Reset. When Windows asks you to confirm, select Reset again.
- Open Microsoft Teams again and sign back in. Give Teams a moment to rebuild its cache on the first launch.
When to Contact Support
If Teams still will not open, keeps asking you to sign in, or the same issue comes back after the reset, contact JC Logic support. Include what you tried and whether the issue affects only Teams or other Microsoft 365 apps too.