ErrorAway

Microsoft Teams won't open? Diagnose it and try 8 fixes

✓ Reviewed & updated July 19, 2026

Compare Teams desktop with Teams on the web before clearing anything. If the web app works with the same account, the service and account are probably usable and the desktop client becomes the main branch. If both fail, check service health, sign-in and organization policy first.

Use the steps in order and stop when the original symptom is gone. New Teams and classic Teams use different local storage paths, so identify the installed app before deleting cache data. On a work or school PC, your administrator may need to handle policies, installation or sign-in tokens.

Quick checklist

  1. Compare desktop and web behavior
  2. Check service health and the account
  3. Quit every Teams process and restart
  4. Update Teams and Windows
  5. Test network, VPN and system time
  6. Repair the new Teams app
  7. Clear only the correct Teams cache
  8. Reset or reinstall with administrator help if needed

Match the symptom before changing anything

What you seeBest first testWhat it suggests
Desktop app fails but Teams on the web worksQuit processes, update, then RepairA desktop-client or local-data problem
Desktop and web both reject the same accountCheck service health and ask the organization adminAn account, license, service or policy issue
Teams remains on loading or shows a blank windowRestart, then use the version-specific cache branchStale local client data may be involved
A meeting link fails but the main app opensOpen the link in a supported browser and test another meetingA link association, browser handoff or meeting-specific issue
Teams works on another networkReview VPN, proxy and organization network rulesThe original network path needs administrator investigation
Managed device or important meeting? Use Teams on the web as a temporary fallback when allowed. Do not remove organization certificates, disable security tools, or delete work-account credentials. Record the error and contact IT if the device is managed.

The 8 checks, from lowest to highest impact

1

Test Teams on the web and check service health

Open teams.microsoft.com in a current browser and sign in with the same account. For a work or school account, your Microsoft 365 administrator can check the service-health dashboard.

Result checkIf the web app also fails, stop resetting the desktop app until the account, service or policy branch is checked. If web works, continue with desktop checks.
2

Quit Teams completely and restart Windows

  • Right-click the Teams taskbar/tray icon and choose Quit when available.
  • Open Task Manager with Ctrl + Shift + Esc and end only clearly named Teams processes.
  • Restart Windows and open Teams once.
Result checkIf Teams now opens, stop. If it returns to loading or a blank window, note that exact state for the cache branch.
3

Update Teams and Windows

If Teams stays open long enough, use Settings and more → Update and restart Teams when that option appears. Microsoft notes that the desktop client also updates automatically while idle. Install Windows updates and restart when requested.

Result checkRepeat the same sign-in or launch action. A changed error should be diagnosed again instead of continuing automatically.
4

Check time, network and VPN without weakening security

Confirm Windows date, time and time zone are correct. If permitted, disconnect and reconnect the VPN or compare with another trusted network. A managed VPN or proxy should be changed only with IT guidance.

  • Do not disable Windows Firewall or antivirus as a test.
  • If another network works, report that comparison to the administrator rather than creating broad exceptions.
Result checkIf Teams works only without an organization VPN, stop and ask IT to inspect the approved Teams network path.
5

Use Repair for the new Teams app

Open Settings → Apps → Installed apps → Microsoft Teams → Advanced options. Select Terminate if shown, then Repair. Repair is the lower-impact choice and should be tried before Reset.

Result checkOpen Teams and test the original account. If Repair is not offered or the app is managed, do not force changes; continue only with administrator approval.
6

Clear the cache for the installed Teams version

Quit Teams first. Microsoft documents different Windows locations:

  • New Teams: open %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams.
  • Classic Teams remnants: open %appdata%\Microsoft\Teams.

Delete the contents only from the path that exists for the version you are troubleshooting. The first restart can take longer while Teams rebuilds its cache.

Before clearing: local cache and personalization can be removed, and sign-in may be required again. Confirm your account and authentication method. Do not delete similarly named parent folders.
Result checkIf Teams opens after rebuilding the cache, stop. If both web and desktop sign-in fail, return to the account/admin branch.
7

Reset the new Teams app only when Repair fails

Return to Teams Advanced options and select Reset. Microsoft states that Reset deletes app data, including personalization settings. Account-backed chats and files should remain in their Microsoft 365 services, but local settings and authentication state can be removed.

Result checkSign in and test. If the organization blocks Reset or account setup, stop and contact the administrator.
8

Reinstall from the approved source

Uninstall Microsoft Teams through Windows Settings, restart, and reinstall using Microsoft Store, Microsoft 365 deployment or the source approved by your organization. Do not download installers from software mirrors.

EscalateIf a fresh client fails while Teams on the web works, give IT the error, timestamp, account type, Windows version, network comparison and steps already tested.

Primary references: Microsoft Learn's Teams cache instructions, Microsoft Support's Teams update guidance, and Windows Repair and Reset guidance.

Frequently asked questions

Will clearing the Teams cache delete my chats?

Account-backed chats and files are stored in Microsoft 365 services, but clearing local app data can remove cached settings and authentication state. Confirm your sign-in method and follow the path for the correct Teams version.

Why does Teams work in a browser but not on desktop?

That comparison shows the account and service can work through the browser. Focus next on desktop processes, updates, Repair and version-specific cache rather than changing the account.

Should I run Teams as administrator?

It is not a normal permanent fix and can conflict with managed-device policy or link handoff. Use the supported Repair, cache and administrator routes instead.

What should I send to my IT team?

Include the complete error, time it occurred, whether the web app works, account type, network/VPN comparison, Windows version and the steps already tried.

If several desktop apps refuse to open, see the Bad Image/system-file guide. If only browser-based sign-in is failing, compare our Chrome startup guide.

Send us the details →