How to Troubleshoot Microsoft Teams (2026 Guide)
Why Microsoft Teams Keeps Breaking
I've seen this on hundreds of machines across enterprise environments and home offices alike , you open Microsoft Teams, and something is just wrong. Maybe it won't load past the splash screen. Maybe your camera freezes mid-call. Maybe you get the dreaded "We're sorry , we've run into an issue" error with no real explanation of what "the issue" actually is. Sound familiar?
Here's the honest truth: Microsoft Teams is one of the most architecturally complex communication apps ever shipped to everyday users. It's essentially a web browser (Chromium-based Electron wrapper), a VoIP client, a real-time collaboration engine, and an enterprise identity platform all jammed into a single process tree. That's a lot of moving parts, and any one of them can go sideways.
The most common root causes I see when troubleshooting Microsoft Teams:
- Corrupted application cache, Teams caches everything aggressively. When that cache gets into a bad state (usually after a crash or a forced update), it can prevent sign-in entirely or cause random UI glitches.
- Account token expiration or corruption, Teams stores authentication tokens locally. If your system clock drifts, or if a conditional access policy changed on the server side, those tokens become invalid and Teams won't tell you in plain English why it's failing.
- Driver conflicts with audio/video devices, Webcam and microphone issues account for roughly 30% of Teams support tickets I've handled. A Windows Update that quietly updates your USB audio driver can suddenly make your microphone invisible to Teams.
- Network issues and proxy misconfiguration, Teams requires specific Microsoft 365 endpoints to be reachable. Corporate firewalls blocking
*.teams.microsoft.comor*.skype.comtraffic is more common than you'd think, and the error Teams shows you gives you zero indication that's the actual problem. - The new Teams app vs. classic Teams conflicts, Since Microsoft pushed the "New Teams" client broadly in 2024–2025, I've seen machines running ghost processes from both versions simultaneously, causing login loops and notification failures.
- Windows 11 permission regressions, After certain feature updates, camera and microphone permissions for desktop apps quietly get reset. Teams stops seeing your devices and just shows a black screen in video.
The other thing that makes troubleshooting Microsoft Teams frustrating is the error messages. "Something went wrong" is not a diagnosis. That's why I'm giving you the actual technical steps here, not the generic "restart your computer" advice you'd get from a first-level helpdesk.
The Quick Fix, Try This First
Before you go deep on troubleshooting Microsoft Teams, try this sequence. In my experience, it resolves about 60% of cases in under five minutes.
Step 1: Fully kill Teams, not just close it. Teams likes to linger in the system tray. Right-click the Teams icon in your taskbar notification area and select Quit. Then open Task Manager (Ctrl + Shift + Esc), look for any process named ms-teams.exe or Teams.exe, right-click it, and select End task. Do this for every Teams-related process you see.
Step 2: Clear the Teams cache. Press Win + R, type %appdata%\Microsoft\Teams, and press Enter. You'll see a folder with subfolders like Cache, blob_storage, databases, GPUCache, IndexedDB, Local Storage, and tmp. Delete the contents of these folders, not the folders themselves, just what's inside them. Leave settings.json if you want to preserve your custom settings.
Step 3: Relaunch Teams and sign in fresh. Open Teams from the Start menu. If it prompts for your credentials, that's actually a good sign, it means the cache clear worked and you're getting a clean authentication attempt.
If you're on the new Teams client (the one with the dark teal icon rather than the purple one), the cache path is slightly different:
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeamsNavigate there the same way via Win + R and clear the EBWebView and Cache folders inside.
If the cache clear didn't do it, the next place to look is the installation itself. Teams updates itself silently in the background, and occasionally an update partially fails, leaving you with a half-new, half-old version that behaves unpredictably.
Open Settings (Win + I), go to Apps > Installed apps, search for "Microsoft Teams" in the search box. You may see multiple entries, "Microsoft Teams" (the machine-wide install) and "Microsoft Teams (work or school)" (the new client). Click the three-dot menu next to each one and select Advanced options.
On that page, scroll down to the Reset section. Click Repair first. Wait 30 seconds. If that doesn't help, come back and click Reset, this is more aggressive and will wipe your local app data for that install.
For the classic Teams client, you can also run a repair directly. Open Control Panel > Programs > Programs and Features, right-click Microsoft Teams, and select Repair if that option appears. Not all versions expose this, but it's worth checking.
After repair or reset, relaunch Teams. You should see a fresh sign-in screen. Sign in with your Microsoft 365 or personal Microsoft account credentials. If the sign-in succeeds and Teams loads normally, you're done. If you still see an error, note any error code shown, codes like 0xCAA20003, 0xCAA70007, or 0x8004e034 point specifically to authentication token failures, which we address in Step 3.
Your call just started and your video is a black square. Or Teams says "We can't detect your microphone." I know that panic, especially when thirty people are waiting on you.
First, check Windows privacy permissions. Go to Settings > Privacy & security > Camera. Make sure Camera access is toggled On, and that Let desktop apps access your camera is also On. Do the same under Microphone. Windows 11 sometimes resets these after feature updates, it's one of the most underreported regressions I've seen.
Next, check device selection inside Teams. In the Teams app, click your profile picture (top right), go to Settings > Devices. Under Camera, you'll see a dropdown, make sure it points to your actual webcam and not "Virtual Camera" or some other device. Same for Microphone and Speaker. Teams sometimes latches onto a device that's been disconnected and refuses to switch automatically.
If the correct device isn't showing at all, open Device Manager (Win + X, then Device Manager). Expand Cameras and Audio inputs and outputs. Look for any device showing a yellow warning triangle. Right-click it and select Update driver > Search automatically. If the driver update doesn't help, try Uninstall device, then scan for hardware changes to let Windows reinstall it fresh.
Run this PowerShell command to quickly check if your camera is being detected at the OS level:
Get-PnpDevice -Class Camera | Select-Object Name, Status, InstanceIdIf Status shows anything other than OK, the problem is at the driver level, not Teams.
The Teams sign-in loop is one of the most maddening issues out there. You enter your credentials, it spins, then dumps you back to the login screen. Over and over. Error codes like 0xCAA20003 (credentials rejected), 0xCAA70007 (network timeout during auth), or 80090016 (key not valid) all point to broken authentication state.
Start by signing out of Teams completely, not just closing it. In Teams, click your profile picture and select Sign out. Then quit Teams entirely using Task Manager as described in the Quick Fix section.
Now clear your Windows Credential Manager entries for Teams. Open Control Panel > Credential Manager > Windows Credentials. Look for entries containing "MicrosoftOffice", "teams", "msteams", or your work email domain. Remove all of them. These are the cached tokens that are causing the loop.
If you're on a domain-joined machine and getting error 80090016, the issue is almost certainly the Windows Hello for Business key. Run this in an elevated PowerShell window:
certutil -user -store MyIf you see expired or invalid certificates tied to your work identity, that's your culprit. Your IT admin will need to re-provision your Windows Hello PIN or smart card credentials. In the meantime, try signing into Teams web at teams.microsoft.com, that bypasses the desktop client auth stack entirely and will at least let you stay productive.
After clearing credentials, relaunch Teams and sign in. When it works, you'll go through a Multi-Factor Authentication prompt and land directly on your Teams workspace, no loop.
Teams is extremely network-sensitive. It uses UDP for media (audio and video) on ports 3478–3481, and TCP 443 for signaling. If your firewall, VPN, or corporate proxy is blocking any of these, your calls will drop, your status won't sync, or you'll see "Connecting..." indefinitely.
Run the Microsoft 365 Network Connectivity Test first. Open your browser and go to connectivity.office.com. It'll run an automatic test and show you exactly which Microsoft 365 endpoints are reachable and which are being blocked. This is the same tool Microsoft's Tier 2 support uses, it gives you real data instead of guesswork.
You can also run a quick DNS check from PowerShell to confirm Teams endpoints resolve correctly:
Resolve-DnsName teams.microsoft.com
Resolve-DnsName presence.teams.microsoft.com
Resolve-DnsName api.teams.skype.comIf any of these time out or return unexpected IP addresses, you likely have a DNS filtering issue, common in corporate environments using tools like Umbrella or Zscaler.
If you're on a VPN, try disconnecting it temporarily and testing Teams. Many VPNs route Microsoft 365 traffic through their tunnel, which adds latency and sometimes breaks UDP. The fix is configuring "split tunneling", your IT team can set this up so Teams traffic goes directly to Microsoft's network rather than through the VPN. The Microsoft documentation specifies exact IP ranges and FQDNs to exclude from tunneling, and any competent network admin will recognize the request immediately.
In the Teams app, check your connection health in real-time during a call by pressing Ctrl + Shift + Alt + 1, this opens the call diagnostics overlay showing packet loss, jitter, and round-trip time. Packet loss above 5% explains most call quality issues.
When nothing else works, a clean reinstall is the answer. But "uninstall and reinstall" done wrong leaves behind residual files and registry entries that cause the same problem to come back immediately. Here's how to do it right.
First, uninstall both Teams entries you see in Settings > Apps > Installed apps, "Microsoft Teams" and "Microsoft Teams (work or school)" if both are present. Also check for "Teams Machine-Wide Installer" and uninstall that too.
After uninstalling, manually delete these folders (copy-paste these paths into File Explorer's address bar):
%appdata%\Microsoft\Teams
%localappdata%\Microsoft\Teams
%localappdata%\Microsoft\TeamsMeetingAddin
%localappdata%\Microsoft\TeamsPresenceAddin
%localappdata%\Packages\MSTeams_8wekyb3d8bbweThen clean up the registry. Open Registry Editor (Win + R, type regedit). Navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Office\TeamsDelete the Teams key entirely if it exists. Also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TeamsNow download the latest Teams installer directly from microsoft.com/en-us/microsoft-teams/download-app. Run the installer. Sign in when prompted. The first launch after a clean install takes 60–90 seconds as it rebuilds all local data, that's normal. Once you're in and your channels load, the problem should be gone.
Advanced Troubleshooting
For IT admins, power users, and anyone dealing with enterprise-specific Teams issues, here's where we go deeper.
Reading Teams Logs
Teams writes detailed logs you can actually read. In the Teams app, press Ctrl + Alt + Shift + 1 to generate a diagnostics package, or navigate manually to:
%appdata%\Microsoft\Teams\logs.txtOpen this in Notepad++ or VS Code and search for lines starting with ERROR or WARN. Pay attention to timestamps, correlate errors with the exact moment Teams broke for you. You'll often find specific error codes and stack traces that tell you exactly what subsystem failed.
Group Policy and Intune Configuration
On domain-joined machines, Teams behavior is heavily influenced by Group Policy and Microsoft Intune MDM policies. If Teams won't let you change settings, like your notification preferences or background images, a GPO is likely locking them down. Open a command prompt and run:
gpresult /h C:\GPReport.htmlOpen that HTML file in a browser and search for "Teams" to see all applied policies. Common culprits include DisableAnonymousJoinByPolicy, AllowMeetNow set to false, and meeting room policies that prevent external participants.
Event Viewer Analysis
For crashes and hangs, Event Viewer is your friend. Open it via Win + X > Event Viewer. Navigate to Windows Logs > Application. Filter by Source = "Application Error" and look for entries where the Faulting application name is ms-teams.exe. Event IDs 1000 (application crash) and 1002 (application hang) will give you the faulting module, often a specific DLL, which points to whether the crash is in Teams itself, a GPU driver, or a third-party add-in.
Proxy Authentication Issues
In enterprises using authenticated proxies (NTLM or Kerberos), Teams sometimes fails to authenticate through the proxy because the Electron runtime doesn't always pass Windows credentials automatically. The registry fix for this:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Teams
Value: AuthzProxyScheme (REG_SZ) = "negotiate"This tells Teams to attempt Kerberos/NTLM negotiation with your proxy. Pair this with ensuring your proxy address is configured in Settings > Network & internet > Proxy at the Windows level, Teams inherits these system proxy settings.
Teams Meeting Add-in Missing from Outlook
This is its own special kind of frustrating. If the "New Teams Meeting" button is gone from Outlook's calendar toolbar, run this in an elevated PowerShell window:
Get-ChildItem -Path "HKLM:\SOFTWARE\Microsoft\Office\Outlook\Addins" | Where-Object { $_.PSChildName -like "*Teams*" }If the add-in is listed but has a LoadBehavior value of 2 (disabled), change it to 3 (load at startup). If it's missing entirely, repair the Teams installation using the method in Step 1, then restart Outlook.
If you've worked through all of the above and Teams still won't function correctly on a specific machine, particularly if it's a corporate device and multiple users are affected, it's time to escalate. Scenarios that genuinely require Microsoft's involvement include: persistent error code 0x8004e034 after a clean reinstall (indicates a federated identity issue on the server side), Teams Rooms devices failing to authenticate after an Azure AD policy change, and "Resource not found" errors tied to missing service plans in the user's license. Reach out directly at Microsoft Support and open a ticket with your tenant ID and the specific error codes, don't go in without those, it'll speed up triage dramatically.
Prevention & Best Practices
Once you've fixed Teams, the goal is obviously to not have to do this again. Here's what I recommend based on managing Teams deployments across organizations of all sizes.
Keep Teams updated, but thoughtfully. Teams updates itself automatically in the background, which is usually fine. But in enterprise environments, I recommend enabling the Teams update rings in the Teams admin center so you can control rollout timing. Going to Teams admin center > Teams apps > Update policies lets you stage updates, test them on a small group before they hit your whole organization. The number of "Teams just stopped working after an update" tickets drops significantly when you have this control.
Don't let the cache grow unchecked. The Teams cache can balloon to 10–15 GB over time, especially if you're in organizations with lots of channels, tabs, and shared files. A bloated cache doesn't just waste disk space, it slows Teams down and makes it more likely to corrupt. I have a PowerShell script I run quarterly on managed machines that clears old cache while Teams is closed. You can also just build this habit manually: every few months, follow the cache-clearing steps from the Quick Fix section above as maintenance rather than repair.
Standardize your audio and video devices. In enterprise settings, USB headsets and webcams that change between sessions (hot-desking, dock cycling) cause a disproportionate number of Teams support calls. Standardizing on a single headset model across the organization, and ensuring its firmware is current, eliminates most audio complaints before they start.
Configure network quality proactively. Work with your network team to implement QoS (Quality of Service) tagging for Teams media traffic. Teams recommends DSCP marking of 46 (Expedited Forwarding) for audio and 34 (Assured Forwarding) for video. This tells your network switches to prioritize Teams call packets over background file transfers, the difference in call quality on a congested network is night and day.
- Set a monthly calendar reminder to clear your Teams cache, treat it like browser maintenance
- Bookmark teams.microsoft.com as a fallback when the desktop client misbehaves, it's feature-parity with the app for most tasks
- In Teams Settings > General, enable Register Teams as the chat app for Office, prevents Outlook from losing the Teams Meeting button after updates
- Run Windows Update and Device Manager driver updates together, not at different times, keeping audio/video drivers in sync with Windows reduces hardware conflicts
Frequently Asked Questions
Why does Microsoft Teams say "We're sorry, we've run into an issue" with no error code?
This generic message almost always means the app hit an unhandled exception during startup or sign-in. The most common triggers are a corrupted local cache, an expired authentication token, or a failed connection to Microsoft's identity servers. Start with the cache clear steps in the Quick Fix section, that resolves this in the majority of cases. If it persists, open %appdata%\Microsoft\Teams\logs.txt and look for the ERROR lines around the timestamp when it crashed. Those will give you the actual technical reason.
Microsoft Teams camera shows a black screen, how do I fix it?
A black camera screen in Teams is almost always a Windows privacy permission issue or a driver conflict, not a Teams bug. Go to Settings > Privacy & security > Camera and make sure both camera access and desktop app access are enabled. Then go into Teams Settings > Devices and confirm the correct camera is selected in the dropdown. If the camera shows as an option but still shows black, right-click the camera in Device Manager and uninstall it, then scan for hardware changes to reinstall the driver fresh.
Teams keeps signing me out every day, why does this keep happening?
Repeated sign-outs are almost always driven by a Conditional Access policy on your organization's Azure AD tenant, specifically a session lifetime policy that's configured to expire tokens daily. This isn't Teams misbehaving; it's an intentional security control your IT team set up. You can verify this by checking whether the same sign-out behavior happens on Teams web. If it does, talk to your IT admin about adjusting the "Sign-in frequency" setting in Azure AD Conditional Access. There's no client-side fix for this, it has to be changed at the tenant level.
Teams is slow and takes forever to load, what can I do to speed it up?
Slow Teams loading is usually either a bloated cache or a resource-constrained machine. Start by clearing the cache (see Quick Fix). Then check your machine's RAM usage in Task Manager while Teams is loading, Teams needs at least 4 GB of available RAM to run comfortably, and 8 GB if you're also running Outlook and a browser. If RAM is the bottleneck, closing other apps before opening Teams makes a real difference. Also try disabling GPU hardware acceleration in Teams Settings > General > Disable GPU hardware acceleration, on machines with older or underpowered GPUs, this actually speeds up rendering.
The "New Teams Meeting" button disappeared from Outlook, how do I get it back?
This happens when the Teams Meeting Add-in for Outlook gets disabled, usually after a Teams update or Outlook repair. Open Outlook, go to File > Options > Add-ins. At the bottom, set the Manage dropdown to COM Add-ins and click Go. Look for Microsoft Teams Meeting Add-in for Microsoft Office, if it's unchecked, check it and click OK. If it's not listed at all, repair Teams through Settings > Apps > Installed apps, then restart Outlook. The add-in should reappear after the repair completes.
Teams notifications stopped working on Windows 11, how do I fix this?
Windows 11 has a notification permission system that Teams needs to get right at two levels: the Windows notification settings and the Teams in-app settings. First, go to Settings > System > Notifications, scroll to find Microsoft Teams, and make sure notifications are set to On with banners and sounds enabled. Then inside Teams, go to Settings > Notifications and check that chat messages, mentions, and calls are not set to "Off". Also check Windows Focus Assist, if it's set to "Priority only" and Teams isn't in your priority list, you'll get silence. Settings > System > Focus is where to add Teams to the allowed apps list.