Few disruptions are more frustrating than Microsoft Teams not launching minutes before a meeting or daily standup. The desktop client may show an empty white window, close itself right after opening, or hang in an invisible background state.
Common support threads recommend a generic reboot. On modern Windows, though, startup freezes usually trace back to corrupted local cache, orphaned background processes that hold configuration files, or an authentication deadlock involving the Edge WebView2 runtime.
LEVELZA verified the walkthrough below to isolate each of these triggers in order, starting with the least invasive fix.
QUICK FIX
Root Cause: Corrupted local Edge WebView2 cache data, orphaned background ms-teams.exe processes holding lockfiles, or expired workplace credentials stored in Windows Credential Manager.
- Immediate Action 1: Force-terminate all lingering Teams processes in Task Manager (Ctrl + Shift + Esc).
- Immediate Action 2: Reset app data through Windows Settings > Apps > Installed apps > Microsoft Teams > Advanced options > Reset.
- Immediate Action 3: Clear obsolete identity tokens in Control Panel > Credential Manager > Windows Credentials.
Escalation Condition: If the client crashes with an application error (Event ID 1000) across all user profiles, check Microsoft 365 Service Health for an active authentication outage, or perform a clean reinstall of the Edge WebView2 Runtime.
Why Microsoft Teams Fails on Startup: The Root Causes
While Microsoft Teams operates as a unified workspace, launch failures are rarely random. Four distinct mechanisms account for most cases, and each one calls for a different fix.
1. Local Cache Corruption in the WebView2 Runtime
The current desktop client no longer runs on the legacy Electron framework. It renders its interface through Microsoft Edge WebView2, a runtime shared with the operating system.
That design depends on local session data: cached pages, IndexedDB databases, and local storage states. If an update is interrupted or a session ends badly, these files can be left half-written.
The embedded web view then cannot build the application shell. The result is usually an unhandled silent crash, with no error message to point to the cause.
2. Stale Identity Tokens in Windows Credential Manager
Teams relies on Single Sign-On to authenticate before it draws the main window. On startup, the client presents cached identity tokens to Microsoft Entra ID, the service formerly named Azure AD.
Tokens rotate or expire after password changes, security policy updates, or long periods of inactivity. If the cached token no longer matches what the identity service expects, the authentication handshake can stall.
The client may then hang on the loading screen or terminate. Clearing the stored tokens forces a fresh sign-in.
3. Zombie Background Processes and File Locks
Closing the Teams window does not always end the application. Headless processes can stay active in the background, particularly after a crash or an interrupted update.
A lingering ms-teams.exe instance can hold exclusive locks on configuration databases. A new launch then cannot initialize, because the files it needs are already claimed by the dead session.
This is the most common cause of a client that “does nothing” when clicked. It is also the fastest to rule out.
4. GPU Hardware Acceleration and Driver Incompatibilities
The interface uses hardware-accelerated rendering by default. Outdated or corrupted display drivers can conflict with that pipeline, especially after a Windows feature update changes graphics components.
The typical symptom is a blank white or black canvas that appears and then crashes during window creation. DirectX-related failures in the driver stack can produce the same effect.
If the first three fixes fail and the machine has an older or recently updated graphics driver, this cause deserves attention before any reinstall.
Step-by-Step Fixes for Microsoft Teams Not Launching
These fixes run from least invasive to most thorough. Work through them in order and test a launch after each one, so the change that worked is clear if the problem returns.
Fix 1: Terminate All Orphaned Background Processes
- Press Ctrl + Shift + Esc to open Task Manager.
- Select the Processes tab and sort by name to find any running instances of Microsoft Teams or ms-teams.exe.
- Highlight each entry and click End task. Also end any WebView2 sub-processes linked to Teams.
- Launch the application again from the Start menu.
If Teams opens normally, a stale process was holding a file lock. No further action is needed.
Fix 2: Execute an In-Place App Repair or Reset
- Open Windows Settings (Win + I) and go to Apps > Installed apps.
- Find Microsoft Teams, click the three-dot menu (…), and select Advanced options.
- Scroll to the Reset group and click Repair first. Repair checks package integrity without deleting local data.
- If launching still fails, return to the same menu and click Reset. This clears cached preferences and requires you to sign in again.
Try Repair before Reset. It resolves a meaningful share of cases without discarding any local settings.
Fix 3: Manually Purge the Local Data and Cache Folders
- Close Teams completely and confirm in Task Manager that no Teams processes remain.
- Press Win + R, paste the path below, and press Enter:
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache - Select all folders in this directory, including
Microsoft\MSTeams, and press Delete. - Restart the PC to release remaining file handles, then launch the app.
This removes the corrupted WebView2 session data described in the first root cause. Teams rebuilds the cache on the next successful launch.
Fix 4: Clear Obsolete Workplace Credentials
Step-by-Step Instructions
- Press the Windows key, type Credential Manager, and press Enter.
- Select Windows Credentials.
- In the Generic Credentials section, look for entries that reference Teams, Microsoft Office, or your work account name.
- Expand each matching entry and click Remove.
- Relaunch the application and sign in with your work or personal account when prompted.
Remove only entries tied to Microsoft and Teams sign-in. Credentials for unrelated software should stay in place.
Warning: Enterprise Tenant Restrictions and Service-Level Outages
If Teams fails to launch right after an IT policy update or a password change, client-side resets will not fix it. Administrators often enforce Conditional Access Policies through Microsoft Intune that block unmanaged or non-compliant devices from running authenticated apps.
A regional outage in Microsoft’s identity verification service produces the same failure regardless of local configuration. Check your organization’s status page, or test the web client, before changing system settings.
If Nothing Above Works: Advanced Logs and Escalation
When every fix fails, the next step is collecting evidence. Logs give IT support something concrete to investigate and save a round of back-and-forth.
Generating Diagnostic and Debug Logs
While the client is open or attempting to start, press Ctrl + Alt + Shift + 1. Teams writes diagnostic text logs to the %userprofile%\Downloads folder. This shortcut only registers if the application window can receive input, so it may not work during a complete startup failure.
The Windows Event Viewer is the more dependable source. Press Win + R, type eventvwr.msc, and press Enter.
Go to Windows Logs > Application and look for error entries with Event ID 1000 or Event ID 1002, where the faulting application is ms-teams.exe. Note the faulting module and exception code, because these point support staff to the failing component.
Escalation and Fallback Access
Do not lose access to meetings while support investigates. Open the web client at teams.microsoft.com in Microsoft Edge or Google Chrome, or join urgent calls from the mobile app.
Send the exported logs and the Event Viewer details to your administrator. For background on supported platforms, account types, and deployment options, see the Microsoft Teams pillar guide.
