Teams refusing to open — clicking the icon and nothing appears, or the splash screen shows then disappears — is surprisingly fixable. The application loads far enough to show there’s a problem, then exits before the main window opens. Almost always a corrupted local data issue or a background process that’s stuck. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The fastest thing to try: Task Manager → look for any Teams processes still running (Teams.exe, ms-teams.exe) → end all of them → wait 10 seconds → launch Teams. If Teams got into a stuck state during a previous crash or improper close, killing the remnant processes often allows a clean launch immediately.
Clear the cache — the main fix
Teams’ local cache accumulates corrupted data. When the app tries to load this data on startup and fails, it exits. Clearing the cache forces Teams to start fresh.
For New Teams (version 2.x): %localappdata%PackagesMSTeams_8wekyb3d8bbweLocalCacheMicrosoftMSTeams → delete the Cache folder. Leave other folders intact.
For Classic Teams: %appdata%MicrosoftTeams → delete the following folders: Cache, blob_storage, Code Cache, databases, GPUCache, Local Storage, tmp.
Quit Teams completely before deleting (system tray → right-click → Quit → verify in Task Manager that all Teams processes are gone). Reopen Teams after deleting. This resolves the “splash screen then nothing” pattern in most cases.
App reset from Settings
Settings → Apps → Installed apps → Teams → three dots → Advanced options → Reset. This is the GUI version of the cache clear. More convenient but less thorough than manually deleting the cache folders. Try this first if the manual deletion seems involved — it catches many startup failures. If the App Reset doesn’t work: manual cache deletion next.
Check the Teams version
New Teams and Classic Teams behave very differently, and installing one over the other without fully removing the first can cause startup conflicts. Go to Apps → see which version is installed. If both appear: uninstall the one you don’t want. Microsoft now ships New Teams for most accounts, but Classic Teams may persist as a leftover from older installations.
For New Teams specifically: it’s installed as a Microsoft Store app. If it’s corrupted: Settings → Apps → Teams → Advanced options → Repair first, then Reset if Repair doesn’t help. The Store app reset path is different from the manual cache deletion and may work when the other doesn’t.
Microsoft 365 account authentication
Teams may fail to open if it can’t authenticate the Microsoft account on startup. This is less visible than a clear error — Teams just exits without explaining why. Check: Settings → Accounts → Access work or school → does your work account show there? Any sync errors or expired session warnings?
If the account shows issues: disconnect and reconnect the work account. Settings → Access work or school → click the account → Disconnect → confirm → restart → reconnect the account. This refreshes the authentication token Teams depends on.
Run Teams as administrator
Right-click the Teams shortcut → Run as administrator. If Teams opens normally as administrator but fails normally: it’s a permissions issue with the Teams installation files or profile folders. Check whether the %appdata%MicrosoftTeams or the New Teams package folder has restricted permissions. The current user account should have Full Control over its own AppData folders — if it doesn’t (can happen after a domain policy change), restoring those permissions resolves the launch failure.
Reinstall Teams
When cache clear and reset haven’t worked: a full clean reinstall.
- Sign out of Teams before uninstalling if it opens at all
- Settings → Apps → Teams → Uninstall
- Delete these folders manually after uninstalling:
%appdata%MicrosoftTeamsand%localappdata%MicrosoftTeams - For New Teams: also
%localappdata%PackagesMSTeams_8wekyb3d8bbwe - Restart the PC
- Download and install from teams.microsoft.com
The folder deletion after uninstalling is the critical step that most reinstalls skip. Without it, the installer recovers from the leftover folders and Teams reinstalls with the same corrupted state.
Conflicting software and startup order
VPN clients, security software, and some system management tools that start before Teams occasionally interfere with its authentication on launch. Task Manager → Startup apps → look for anything that starts before Teams. Disabling specific startup items temporarily (particularly VPN clients) and launching Teams manually after Windows has fully loaded sometimes reveals that the conflict is timing-based.
Microsoft Teams web client as a fallback
teams.microsoft.com in any browser provides full Teams functionality while the desktop app is being fixed. Meetings, messaging, and file sharing all work in the browser version. The web client is genuinely complete for most work tasks and is the practical alternative when the desktop app is down and there are meetings or messages to attend to.
Related authentication issues that sometimes cause Teams startup failure are covered in our Teams signing out guide — Azure AD token problems, Conditional Access policy failures, and Primary Refresh Token issues can all prevent Teams from completing its startup sequence. For New Teams specifically with Microsoft Store app issues, our Windows 11 apps not opening guide covers the Store app repair and PowerShell re-registration approaches. Microsoft’s Teams desktop client troubleshooting covers the Teams diagnostic log locations and the specific event log entries that Teams writes when it fails to start, including the error codes that distinguish authentication failures from installation corruption.
Teams startup after Windows Update
Windows updates occasionally break Teams in specific ways: the update changes a shared dependency (Visual C++ runtime, .NET version), Teams’ app registration in the Start menu becomes invalid, or the update changes security settings that affect how Teams’ processes can launch. Teams that opens fine after the update for a few days then starts failing suggests accumulated cache corruption from the changed environment rather than an immediate update impact.
Check Windows Update history for the date the Teams issue started. If a specific update correlates: search for that KB number alongside “Teams not opening” to see whether it’s a known regression. Microsoft patches Teams-specific Windows Update regressions usually within one to two release cycles.
Language and regional settings
Teams checks the system locale on startup and may fail if the locale configuration is corrupted or set to an unexpected combination. Settings → Time and language → Language and region → confirm the Display language and the regional format are consistent. If the display language is set to one locale but the keyboard is set to a different layout with conflicting input settings, Teams occasionally fails to initialise correctly.
Adding the correct language pack explicitly (Settings → Language and region → Add a language → select and install the preferred language with all language packs) ensures Teams finds consistent locale data on startup.
Windows credentials and the keychain
Teams stores authentication tokens in Windows Credential Manager. When these tokens become corrupted — after password changes, account moves, or security policy updates — Teams tries to load them on startup, fails, and exits rather than showing a login prompt.
Control Panel → Credential Manager → Windows Credentials → look for entries containing “Teams,” “MicrosoftTeams,” “msteams,” or general “MicrosoftOffice” entries → remove them all. Restart Teams — it re-prompts for login and creates fresh credential entries. This is worth doing before the full reinstall as it’s faster and specifically addresses the authentication token corruption path.
Teams and WebView2
New Teams uses Microsoft Edge WebView2 for rendering its interface. If WebView2 is missing, outdated, or corrupted, New Teams cannot open because it can’t initialise its rendering layer. Check: Settings → Apps → search “WebView2” → Microsoft Edge WebView2 Runtime should appear. If it’s not installed: download from Microsoft’s WebView2 download page and install. If it appears but Teams still won’t open: uninstall WebView2 → restart → download and reinstall the latest version → try Teams again.
GPU driver and Teams rendering crash
New Teams renders using hardware acceleration via WebView2. On machines where the GPU driver has compatibility issues with WebView2’s rendering, Teams crashes immediately on startup when it tries to initialise the display layer. The startup crash looks the same as other startup failures — the splash screen appears and disappears.
To test: set Teams to use software rendering. In the registry: HKEY_CURRENT_USERSOFTWAREMicrosoftTeams → create a new DWORD value named “DisableGPU” → set to 1. Restart Teams. If it opens with DisableGPU enabled, update the GPU driver from the manufacturer’s website → remove the DisableGPU registry value → test with hardware acceleration restored.
When Teams is installed for a different user
On shared machines or after a user account migration: Teams may be installed for a different user account than the currently active one. The shortcut exists and appears to work, but the installation is scoped to a different account’s profile. When the current user tries to launch, the exe exists but Teams’ profile data isn’t found for this user.
Sign out and back in as the user Teams was installed for — if it opens for that account but not the current one: Teams needs to be installed specifically for the current account. Download and run the Teams installer while logged in as the current user. The installer creates the necessary profile folders and registration for the active account.
Checking Teams event log
Teams writes to the Windows Event Log when it encounters startup errors. Event Viewer → Applications and Services Logs → Microsoft → Windows → any Teams-related entries, and also Windows Logs → Application → look for Application Error entries for Teams.exe or ms-teams.exe around when the startup failure occurred.
The “Exception code” in these crash events narrows the cause: 0xc0000005 is an access violation (permissions or corrupted file), 0xc000007b is a corrupted or missing dependency DLL (often WebView2 or .NET), 0x40000015 is heap corruption (often cache corruption), and STATUS_STACK_OVERFLOW indicates a crash during initialisation. Each code points at a different fix, making the event log check the most efficient diagnostic when the standard cache clear and reset approaches haven’t resolved the issue.
Proxy settings blocking Teams initialisation
Teams checks connectivity to Microsoft’s authentication and update servers on startup. If a proxy is configured in Windows settings that’s unreachable (corporate proxy when working from home, a VPN proxy that’s no longer active), Teams’ startup network checks fail, and it exits rather than proceeding with a failed connectivity state.
Settings → Network and internet → Proxy → confirm the proxy configuration is appropriate for the current network. “Automatically detect settings” or “No proxy” for home networks. If switching to no proxy allows Teams to open, the proxy configuration is the startup blocker.
Desktop shortcut vs Start menu pin
A specific scenario: the Teams desktop shortcut points to an old installation path (after an update moved the exe) while the Start menu pin points to the current location. The shortcut launches successfully from Start but the desktop shortcut fails — or vice versa. Delete both the desktop shortcut and the Start menu pin → right-click Teams.exe at its current location → Pin to Start / Send to Desktop.
For New Teams: the current exe location is %localappdata%MicrosoftWindowsAppsms-teams.exe. For the Store version, the shortcut should be created through the Start menu automatically after install — manually browsing to the exe and creating a shortcut sometimes creates a shortcut to a version-specific path that becomes invalid after an update.
In summary: the path from “Teams won’t open” to “Teams opens” is usually one of these in order: kill remnant processes → clear cache → App Reset → credential cleanup → full reinstall with folder deletion. The WebView2, GPU, and proxy causes are less common but worth knowing when the main four approaches don’t resolve it. The Teams web client is always available as a same-day workaround regardless of what’s happening with the desktop app.
One practical note: Teams updates silently in the background, and sometimes an update is partially applied when a crash or shutdown happens. The next launch tries to complete the interrupted update, fails, and exits. Checking whether a Teams update is pending: sign into the Teams web client → look at the version shown in Help → compare to the desktop app’s version (if it’s accessible at all). If the web client shows a newer version than the desktop had: the desktop app’s update was interrupted. A clean reinstall with the current version from teams.microsoft.com resolves this cleanly without needing to diagnose the specific interrupted update component.
And for IT administrators dealing with this at scale: Teams startup failures across multiple machines on the same update cycle are almost always a compatibility issue with a specific Windows or Teams version combination. The Teams Admin Center provides deployment health monitoring that surfaces these patterns at the tenant level, and Microsoft releases targeted remediation guidance for known startup regression issues through the Service Health dashboard in the Microsoft 365 Admin Center — checking there before troubleshooting individual machines often reveals whether the issue is a known, in-progress fix from Microsoft’s side. If this sounds familiar, Adobe Reader Not Opening is worth a look.
