Microsoft Teams Won't Open Windows 11: 9 Things to Try

If Microsoft Teams won't open on Windows 11, check whether your PC is managed by an organization or fully yours before you touch anything else, since that decides which fixes below actually apply to you. The same troubleshooting applies if Microsoft Teams won't open Windows 10 too, though the sources behind this guide don't compare how the two versions behave side by side.

An October 2025 NHSmail alert documented a case where some Windows users saw intermittent crashes launching the Teams desktop app. The alert attributed the incident to a code regression in a standard service update and said Microsoft had remediated it by reverting the impacting change, not by any local repair (NHSmail Support, October 2025, Microsoft reference TM1181326). Check Microsoft's service status before you clear a single cache folder.

This guide walks through nine things to try to fix Microsoft Teams not opening, ordered to avoid unnecessary reinstalls and risky system commands. It covers Windows 11 and Windows 10, and splits personal-PC fixes from work or school-managed device fixes. The examples below come from several Microsoft Q&A threads, not from data on how common each cause is, so treat every step as something to test, not a guaranteed cure.

Is your PC managed by an organization or your own?

Check Settings > Accounts > Access work or school, but treat that as one signal, not the whole answer. The stronger signals are device ownership, whether it's enrolled in a management system like Intune, whether IT controls policy on it, and whether a Company Portal app is deployed on it. If any of those apply, treat the PC as managed, run the three checks below, then skip to the managed-device fixes.

A work account signed into Teams on a personal laptop doesn't by itself mean the device is enrolled in organizational management. If that's your setup, use the personal-PC fixes for local issues like cache corruption, but ask IT before touching WebView2 or changing how Teams is installed.

If the PC is personally owned and isn't enrolled in organizational management, use the personal-PC steps below. If you're not sure, ask IT before changing WebView2 or reinstalling Teams.

Three checks before you try a fix

Run these regardless of which type of PC you have. They help narrow down whether to keep working through local fixes or stop and wait.

1. Open Teams on the web. Go to teams.microsoft.com and sign in. If it loads and shows your chats, that shows Teams on the web is reachable for that sign-in; it doesn't rule out a bug specific to the desktop client, or a tenant or permissions issue the web app hasn't run into yet. Keep using the web version while you work through the rest of this list on the desktop app.

2. Fully exit and relaunch the desktop app. Right-click the Teams icon in the taskbar and choose Exit, not the window's close button. Wait a few seconds, then reopen Teams from the Start menu. Both a February 2026 Microsoft Q&A thread and a December 2025 Microsoft Q&A thread give this exact exit step before clearing the Teams cache (Microsoft Q&A, February 2026; Microsoft Q&A, December 2025), and it costs nothing to rule out first.

3. Check for a known issue on Microsoft's end. Admins can check the Microsoft 365 Service Health dashboard. Everyone else can check Microsoft's public status page or look for matching reports elsewhere. The October 2025 NHSmail alert mentioned above is one documented instance of a Teams desktop launch issue traced to a code regression in a standard service update, not something a cache clear would have fixed (NHSmail Support, October 2025). If service health or a wave of matching reports fits your symptoms, pause here; a cache clear or reinstall is unlikely to help against an active service-side incident.

Fix Microsoft Teams not opening on a personal Windows PC

These steps apply to unmanaged, personal PCs confirmed using the check above. Work through them in order rather than jumping to the last one.

Clear the Microsoft Teams cache on Windows

4. Clear the Teams cache. First, check Settings > Apps > Installed apps to confirm which version of Teams is actually on your PC, since that tells you which cache folder applies. Then exit Teams completely: right-click the taskbar icon and select Exit, and check Task Manager to confirm no ms-teams.exe process is still running if files won't delete.

Press Windows key + R to open the Run dialog, paste in whichever path matches your install, and select OK:

• %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
• %appdata%\Microsoft\Teams

Delete the contents of that folder, not the folder itself, then relaunch Teams (Microsoft Q&A, February 2026; Microsoft Q&A, December 2025). A December 2025 Microsoft Q&A thread notes that clearing the cache doesn't remove Teams from the device; it resets local data such as cached web content, thumbnails, and message history (Microsoft Q&A, December 2025). If neither path exists even after confirming your installed version, move on rather than guessing at a third location.

5. Restart Windows. One user in a February 2026 Microsoft Q&A thread reported the WebView2 error returning specifically after installing Windows updates (Microsoft Q&A, February 2026). A restart is a quick, low-effort test here, not a confirmed fix; if the error comes back, move to the next step.

6. Reinstall the WebView2 Runtime, personal PCs only. WebView2 is a shared Windows component, and other apps on your PC, including some finance or productivity tools, can depend on it. Check what else relies on it before you uninstall. Don't remove WebView2 from a managed computer without IT approval.

To reinstall it: close Teams completely, open Settings > Apps > Installed apps, search for Microsoft Edge WebView2 Runtime, and uninstall it. Download the current Evergreen Bootstrapper from Microsoft's official WebView2 page, run it, and restart your PC (Microsoft Q&A, February 2026; Microsoft Edge Developer). This isn't a fix for every launch failure, just the WebView2-specific one described above.

If the installer keeps reporting WebView2 as already present while Teams, or another WebView2-dependent app, still won't open, that may indicate an inconsistent WebView2 installation rather than something a standard reinstall clears up. A June 2025 Microsoft Q&A thread documents this exact pattern blocking Teams alongside a separate finance app on the same machine; the responder proposed deeper system-level repairs, but the thread ends with the original poster thanking them rather than confirming the fix actually worked (Microsoft Q&A, June 2025). Don't run system-repair commands pulled from a forum thread without a backup and real technical confidence. If this exact installed-but-broken pattern shows up on your PC, especially alongside another WebView2-dependent app failing too, contact Microsoft Support or a qualified technician instead of experimenting on your own.

7. Reinstall Teams, as a last resort. Uninstall Teams through Settings > Apps > Installed apps, restart, then reinstall through the Microsoft Store or whichever source you originally used. Do this only after steps 4 through 6. A December 2025 Microsoft Q&A thread documents a case where reinstalling Teams alone didn't fix a post-update launch error; the problem appeared tied to the installation source or configuration rather than the app files themselves (Microsoft Q&A, December 2025).

If Teams still won't launch after all four steps, local corruption likely isn't the cause. Avoid repeating the same steps, and instead check whether Microsoft has released a newer Teams or Windows update, since the documented cases above trace back to issues that surfaced right after an update rather than something stuck on your machine permanently.

Fix Microsoft Teams stuck loading on a work or school-managed PC

These steps apply if the check above confirmed a managed device, company-owned hardware, or a PC under IT policy control. Don't uninstall WebView2 or reinstall Teams outside approved channels here; it can conflict with device policy or simply behave differently than it would on a personal PC.

8. Install or repair Teams through Company Portal, if your organization has deployed it. In a December 2025 Microsoft Q&A thread, manually downloading Teams from Microsoft's public website failed to fix a post-update launch error on a managed device. Installing Teams through the organization's Company Portal app resolved it instead, suggesting installation source or configuration mattered in that case (Microsoft Q&A, December 2025). If Company Portal isn't deployed on your device, move to the next step instead of substituting the public installer.

9. Escalate to IT with a specific handoff. A separate October 2025 Microsoft Q&A thread shows why local troubleshooting can't always fix a managed-device failure. Teams failed to launch under an affected Entra AD-joined profile, but opened normally under a newly created local, non-domain profile on the same PC. Re-enrolling the device in Entra and recreating the user profile didn't help either (Microsoft Q&A, October 2025). The crash report listed ucrtbase.dll as the faulting module, a detail mainly useful as information to hand IT rather than something you can diagnose from the name alone. Give IT:

• The exact error text or code, for example "Something went wrong [76c6]"
• What actually happens: does Teams crash immediately, hang on a loading spinner, or prompt for WebView2?
• Your Teams version, found under Settings > About Teams
• Whether the device is managed and Entra AD-joined
• Whether Teams web works from the same account
• Whether coworkers are hitting the same symptoms, and whether it started right after an update

If multiple coworkers report the same symptoms, that increases the likelihood of a deployment, policy, or service-side issue, and gives IT a stronger reason to investigate rather than something a local reinstall is likely to solve.

What to do now

Start with the web app and a service-status check, since neither requires changing anything on your device. Open teams.microsoft.com to keep working, and check Microsoft's service health or status page for an active incident matching your symptoms.

If nothing's flagged and you're on an unmanaged personal PC, work through the cache clear, restart, and WebView2 reinstall in order, and treat a full reinstall as the last resort, not the first move.

If you're on a work or school-managed device, use Company Portal if it's deployed. If it isn't, send IT the exact error code, Teams version, and symptom details from the checklist above instead of repeating fixes that already failed for someone else.