If Microsoft Teams won't open on Windows 11, first check whether your PC is managed by an organization or fully yours. That determines which fixes you can safely try. Most of the troubleshooting also applies to Windows 10, although some Settings menus differ.
Teams can fail to launch because of damaged local app data, sign-in problems, WebView2 errors, organizational policies, or issues with Microsoft's services. Not every failure can be fixed by clearing a cache or reinstalling the app.
This guide covers nine things to try, starting with simple checks and moving toward more involved repairs. It separates personal-PC troubleshooting from work or school-managed devices to help you avoid unnecessary reinstalls or changes that conflict with IT policies.
Is your PC managed by an organization or your own?
Open Settings > Accounts > Access work or school to check whether your device is connected to an organization.
That screen is a useful starting point, but it doesn't establish whether the device is fully managed. Stronger indicators include company ownership, enrollment in Microsoft Intune or another management platform, IT-controlled policies, and an organization-provided Company Portal app.
A work account signed into Teams on a personal laptop doesn't automatically mean the entire PC is managed.
If the computer belongs to you and isn't enrolled in organizational management, you can generally follow the personal-PC troubleshooting steps below.
If your employer or school manages the device, run the initial checks, then move to the managed-device section. Don't uninstall shared components or reinstall Teams outside approved channels without IT authorization.
Three checks before you try a fix
Run these checks regardless of which type of PC you use. They help determine whether the problem is limited to the desktop app or might involve your account or Microsoft's services.
1. Open Teams on the web. Visit Microsoft Teams and sign in.
If the web app loads and displays your chats, you have a temporary way to keep working. It also suggests the problem may be specific to the desktop client, although it doesn't rule out every account or service issue.
If Teams fails in both the browser and desktop app, investigate your account, network, and service availability before changing local application files.
2. Fully exit and relaunch Teams. Right-click the Teams icon in the Windows notification area and select Quit.
If Teams isn't visible there, open Task Manager and check whether a Teams process is still running. End an unresponsive Teams process if necessary, then reopen the app from the Start menu.
Closing the Teams window isn't always the same as quitting the application completely.
3. Check for a known Microsoft service issue. Microsoft 365 administrators can check the Service health dashboard in the Microsoft 365 admin center.
Other users can check Microsoft's public service status page or ask their organization's IT team whether there's an active incident affecting Teams.
Microsoft has documented cases where Teams launch failures or crashes resulted from service updates rather than problems with individual PCs.
If a known incident matches your symptoms, wait for Microsoft's resolution instead of repeatedly clearing caches or reinstalling software.
Fix Microsoft Teams not opening on a personal Windows PC
These steps apply to personally owned, unmanaged computers. Work through them in order rather than jumping straight to a reinstall.
Clear the Microsoft Teams cache on Windows
4. Clear the Teams cache or reset its local app data. Microsoft provides different instructions for the current Teams app and the retired classic Teams client.
For the current Teams app, the simplest supported approach is to reset the application through Windows Settings.
Open Settings > Apps > Installed apps.
Search for Microsoft Teams.
Select the three-dot menu next to the app and choose Advanced options, if available.
Select Repair first if Windows offers that option.
If Teams still won't launch, select Reset.
Reopen Teams and sign in again if prompted.
Resetting Teams removes local application data, including some personalization settings. It doesn't delete the chats and files stored in your Microsoft 365 account.
Microsoft also documents a manual cache-clearing method for the current Teams client.
Fully quit Teams, press Windows key + R, and enter:
%userprofile%\AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams
Delete the contents of that folder, not the parent Teams package directory, then reopen Teams.
For the retired classic Teams client, the corresponding cache location is:
%appdata%\Microsoft\Teams
Use only the path that matches your installed client. Don't delete unrelated folders if the expected path doesn't exist.
Microsoft's official Teams cache instructions also warn that clearing the cache isn't appropriate for every Teams issue. It can remove diagnostic logs that IT may need to investigate problems with chats, channels, or notifications.
If Teams crashes on launch and you're using a personal PC, a targeted reset may be worth trying. If you're investigating missing messages or a managed-device failure, consult IT before deleting local data.
5. Restart Windows. Restart the computer after applying pending Windows or Teams updates.
A restart can clear stuck processes and complete updates that haven't fully taken effect.
This is a low-risk troubleshooting step, not a guaranteed fix. If Teams still fails to launch after Windows restarts, continue to the next check.
6. Check or repair the Microsoft Edge WebView2 Runtime. Teams uses WebView2 for parts of its desktop interface. A WebView2 failure can prevent Teams from loading correctly.
Start by checking whether the runtime is installed:
Open Settings > Apps > Installed apps.
Search for Microsoft Edge WebView2 Runtime.
If it appears, check whether a Modify or Repair option is available.
If repair is supported, use that option and restart Windows.
If WebView2 is missing or Teams explicitly reports that it can't find the runtime, download the current installer from Microsoft's official WebView2 page.
Don't uninstall WebView2 as a routine troubleshooting step. It's a shared component that other applications may depend on, and removing it can create additional problems.
Microsoft's Teams crash troubleshooting documentation identifies WebView2 process failures as one possible cause of desktop crashes.
However, a Teams launch failure doesn't automatically mean WebView2 is damaged.
If the installer reports that WebView2 is already installed but Teams still won't launch, avoid forcing removal or running system-repair commands copied from forum discussions.
Contact Microsoft Support or a qualified technician if you suspect a damaged runtime and the supported repair options don't work.
7. Reinstall Teams as a last resort. If the earlier checks haven't resolved the problem, reinstall the desktop application.
Open Settings > Apps > Installed apps.
Find Microsoft Teams and select Uninstall.
Restart Windows.
Download the current installer from Microsoft Teams.
Install Teams and sign in.
Use Microsoft's official installer rather than an unfamiliar third-party download.
Reinstalling Teams may resolve damaged installation files, but it won't necessarily fix account restrictions, service incidents, or problems caused by organizational policies.
If Teams still won't open after reinstalling, don't repeat the same steps indefinitely. Check for newer updates and consider contacting Microsoft Support with the exact error message.
Fix Microsoft Teams stuck loading on a work or school-managed PC
These steps apply to company-owned computers, school devices, and PCs enrolled in organizational management.
Don't uninstall WebView2, remove device-management software, or reinstall Teams outside approved channels. Those changes may conflict with deployment policies or security controls.
8. Install or repair Teams through Company Portal, if available. Some organizations distribute Teams through Microsoft Intune's Company Portal instead of allowing users to install it independently.
Open Company Portal, find Microsoft Teams, and check whether your organization offers an installation, update, or reinstall action.
A December 2025 Microsoft Q&A discussion describes a managed-device case where installing Teams through Company Portal resolved a launch problem that the public installer hadn't fixed.
That's one documented outcome, not proof that Company Portal will resolve every managed-device failure.
If your organization doesn't provide Teams through Company Portal, don't substitute an unapproved installer. Move to the next step.
9. Escalate to IT with specific details. If Teams still won't launch, collect enough information for your IT team to distinguish an application crash from a policy, account, or deployment problem.
A separate Microsoft Q&A case documented Teams failing under an affected Microsoft Entra-joined user profile while opening normally under a different local profile.
The crash report identified ucrtbase.dll as the faulting module, but that detail alone didn't establish a universal fix.
When contacting IT, provide:
The exact error message or code, such as "Something went wrong [76c6]."
What happens when Teams launches: an immediate crash, a loading spinner, a blank window, or a WebView2 warning.
Your Teams version, if you can open the app's Settings > About Teams page.
Your Windows version and whether the device is enrolled in organizational management.
Whether Teams works in a browser with the same account.
Whether coworkers are experiencing similar failures.
Whether the problem started immediately after a Teams or Windows update.
If Teams closes before you can check its version, tell IT that rather than guessing.
Multiple users experiencing the same symptoms may indicate a shared deployment, policy, or service issue. Your IT team can investigate those possibilities without requiring everyone to reinstall the application independently.
What to do now
Start with the web app, a complete Teams restart, and Microsoft's service status. None of those steps requires changing your Windows installation.
If Teams works on the web but won't open on an unmanaged personal PC, try the supported Windows repair or reset options, restart the computer, and investigate WebView2 only if the symptoms point toward it.
Treat a full Teams reinstall as a later step, not the first move.
If you're on a work or school-managed device, use Company Portal when your organization provides it. Otherwise, send IT the exact error, Teams version, and symptoms rather than making changes that could interfere with device management.
And if multiple users are suddenly unable to open Teams, check for a shared service or deployment problem before assuming every affected computer needs repair.
Comments
Be the first, drop a comment!