Quick Answer — Microsoft Teams Not Working
Before you touch anything on your PC, find out whether Teams is actually down. If Teams won't load for your whole team or company at once, it is a Microsoft outage, not your computer — check the Microsoft 365 admin center service health and Downdetector first. (A widely reported spike of Teams sign-in and "Connecting" failures hit on June 16, 2026.) If it's just you — Teams is stuck on "Connecting", keeps signing you out, or shows "We're sorry—we've run into an issue" with caa70004 or caa20004 — then clear the Teams cache and sign back in. That single step fixes the large majority of cases on both classic Teams and new Teams. The full 7-step guide below covers everything else.
What "Microsoft Teams Not Working" Actually Means
"Teams not working" is a catch-all for several different failures, and the right fix depends on which one you're hitting. The desktop app may open to a blank or grey window and never load, sit forever on the spinning "Connecting" screen, repeatedly drop you back to the sign-in page, or throw "We're sorry—we've run into an issue" with an authentication code such as caa70004 or caa20004. Calls and meetings may connect but show no video, or chat may load while presence stays stuck on "Unknown".
The single most important question is "is it just me, or is it everyone?". If colleagues across your organization all lose Teams at the same moment, it is a Microsoft Teams service outage and there is nothing to fix on your PC — you wait for Microsoft to restore service. A notable Teams disruption was widely reported on June 16, 2026, with users worldwide seeing sign-in and "Connecting" failures. If the problem is only on your machine, it is almost always a local cause: a corrupted cache, a stale credential token, or a network/proxy/clock issue. This guide covers both classic Teams (the older Electron app) and new Teams (the rebuilt ms-teams app), because the cache locations and reinstall steps differ between them.
Which Symptom Did You Get?
All of these point at the same handful of causes. Here is the fastest first move for each:
| Symptom | What it usually means | Best first fix |
|---|---|---|
| Won't load / blank window for everyone | Microsoft Teams service outage | Fix 1 (check status) |
| Stuck on "Connecting" | Network, proxy or date-time problem | Fix 7 (network & DNS) |
| Keeps signing you out | Corrupted Teams cache | Fix 3 (clear cache) |
caa70004 / caa20004 | Sign-in token can't be validated | Fix 4 (reset credentials) |
| "We're sorry—we've run into an issue" | Corrupted cache or stale token | Fix 3 then Fix 4 |
Symptoms You'll See
- The desktop app opens to a blank, grey or white window that never finishes loading
- Teams sits on "Connecting…" indefinitely and never reaches your chat list
- You sign in, then get dropped back to the login screen over and over
- The error screen "We're sorry—we've run into an issue" with code
caa70004orcaa20004 - Presence shows "Unknown", or messages won't send and show a red "Failed to send"
- The web app at teams.microsoft.com works but the desktop app does not (or vice-versa)
Teams down right before a meeting?
Don't waste 30 minutes guessing. Our certified bilingual technicians remote in, confirm whether it's an outage or your PC, clear the cache, reset your sign-in and get you back into Teams — same day, flat rate, no fix no fee.
Common Causes (Why This Happens)
- Microsoft Teams outage — the #1 cause when it fails for everyone at once. A service-side problem at Microsoft (as on June 16, 2026) takes Teams down regardless of your PC.
- Corrupted Teams cache — the most common local cause. A bad cached file makes Teams hang on "Connecting" or kick you back to sign-in.
- Stale credential / sign-in token — an expired or cached Microsoft Entra ID (Azure AD) token drives
caa70004andcaa20004. - Network or proxy block — a VPN, strict corporate firewall or proxy blocks the Teams endpoints, leaving it stuck on "Connecting".
- Wrong system date & time — an incorrect clock breaks the TLS/token handshake and causes silent sign-in failures.
- Outdated or half-installed client — an old classic Teams build, or a broken new Teams (
ms-teams) install, that needs repair or reinstall.
The 7 Fixes (In Order — Start at the Top)
Work through these in order. Fix 1 saves you from "fixing" a PC that isn't broken, and Fix 3 (cache) resolves most local cases. Run any Command Prompt / PowerShell step as Administrator (Win + X → Terminal (Admin)) and quit Teams completely before clearing its cache.
Check the Microsoft Teams Service Status — Rule Out an Outage First
Always start here. If Teams is down on Microsoft's side, no local fix will help and you'll just waste time.
- If you're an admin, open the Microsoft 365 admin center → Health → Service health and look for an active Teams advisory.
- Check Downdetector (search "Microsoft Teams Downdetector") for a spike in reports — a sharp spike means a broad outage, like the one reported on June 16, 2026.
- Ask a colleague: if Teams is down for them too, it's an outage. Use the web app or wait it out, and check the Microsoft 365 Status feed for updates.
If it's only you, move on to Fix 2 — the rest of this guide is for local problems.
Fully Quit Teams from Task Manager and Relaunch
Teams often hangs because a background process is stuck. Closing the window isn't enough — Teams keeps running in the tray, so you must end every process.
- Press Ctrl + Shift + Esc to open Task Manager.
- Under Processes, find every entry named Microsoft Teams and ms-teams (and
Teams.exe), select each and click End task. - Relaunch Teams from the Start menu and let it make a fresh connection.
This alone clears a surprising number of "Connecting" and frozen-window cases.
Clear the Teams Cache (the fix that solves most local cases)
A corrupted cache is the #1 local cause of Teams not loading or signing you out. Quit Teams completely first (Fix 2). Clearing the cache does not delete your chats or files — those live in the cloud and reload automatically.
Classic Teams — delete the cache folder. Press Win + R, paste the path and delete everything inside the Teams folder:
%appdata%\Microsoft\TeamsOr wipe it from an elevated prompt in one line:
taskkill /F /IM Teams.exe
rmdir /S /Q "%appdata%\Microsoft\Teams"New Teams (ms-teams) — clear the app-package cache instead:
taskkill /F /IM ms-teams.exe
rmdir /S /Q "%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache"Relaunch Teams and sign in again. It will rebuild the cache from scratch.
Sign Out and Remove Cached Office Credentials — best for caa70004 / caa20004
The caa70004 and caa20004 errors mean Teams can't validate your sign-in token. Clearing the stored credential forces a clean sign-in.
- In Teams, click your profile picture → Sign out, then quit Teams.
- Open Credential Manager (search it in Start) → Windows Credentials.
- Under Generic Credentials, remove any entries beginning with
MicrosoftOffice,msteamsorMicrosoft_Teams(click each → Remove).
You can also open it directly:
control /name Microsoft.CredentialManagerRelaunch Teams and sign in again with your full email address.
Use the Teams Web App as a Stopgap
If you have a meeting now and can't wait, the browser version gives you full chat, calls and meetings while you repair the desktop client.
- Open Microsoft Edge or Google Chrome and go to teams.microsoft.com.
- Sign in with your work or school account.
- If the web app works but the desktop app doesn't, the problem is the local app (go back to Fix 3). If the web app also fails, it's your account or network (Fix 7) — or an outage (Fix 1).
Repair or Reinstall the New Teams Client
If the cache fix didn't hold, reset or reinstall the app. Your data is in the cloud, so nothing is lost.
- Repair / Reset: Settings → Apps → Installed apps → Microsoft Teams → Advanced options → Repair (then Reset if Repair fails).
- Reinstall via winget (elevated PowerShell):
winget uninstall "Microsoft Teams"
winget install Microsoft.Teams- Or via the Microsoft Store: open the Store, search Microsoft Teams, and click Update / Get to reinstall the latest build.
Reboot, launch Teams and sign in.
Fix Network / Proxy / Date-Time and Flush DNS — best for "Stuck on Connecting"
If Teams hangs on "Connecting", the connection itself is failing. Check these in order:
- System clock: right-click the clock → Adjust date and time → enable Set time automatically and click Sync now. A wrong clock breaks the sign-in handshake.
- VPN / proxy: temporarily disconnect any VPN and disable proxy settings, then retry Teams.
Then flush DNS and reset the network stack in an elevated prompt:
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock resetReboot after netsh winsock reset. If your company uses a firewall, the required Teams endpoints may be blocked — your IT admin (or an IT Cares technician) can confirm and whitelist them.
Advanced: Read the Teams Diagnostic Logs
To see exactly why sign-in is failing, collect the Teams logs. In the Teams system-tray icon, right-click → Collect support files (or press Ctrl + Alt + Shift + 1 while Teams is focused). The debug logs are written to:
%appdata%\Microsoft\Teams\logs.txt (classic) and %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs (new Teams)
Open the latest log and search for the error code. Common lines and the fix they map to:
- "caa70004" / "caa20004" / token errors → Fix 4 (reset credentials)
- "ECONNREFUSED" / "timeout" / "proxy" → Fix 7 (network & DNS)
- "cache" / "corrupt" / repeated sign-out → Fix 3 (clear cache)
- "Service Unavailable" / 503 for everyone → Fix 1 (it's an outage)
Teams Still Not Working After All 7 Fixes?
IT Cares technicians remote into your PC, read the Teams logs, confirm whether it's an outage or your machine, clear the cache, reset your sign-in and get you back into meetings — usually under 30 minutes. Flat rate, no fix no fee.
Common Mistakes to Avoid
- Don't reinstall before checking the status page. If it's a Microsoft outage, reinstalling Teams ten times changes nothing.
- Don't just close the window. Teams keeps running in the tray — end every process in Task Manager before clearing the cache.
- Don't worry about losing chats. Clearing the cache or reinstalling never deletes messages or files — they're in the cloud.
- Don't ignore the system clock. A wrong date or time silently breaks sign-in and is easy to overlook.
- Don't mix up classic and new Teams cache paths. Clearing the wrong folder does nothing — match the path to the app you actually run.
How to Prevent Teams Problems Going Forward
- Keep Teams updated — let the new Teams app auto-update, or run
winget upgrade Microsoft.Teamsmonthly. - Leave Set time automatically on so your clock never drifts.
- Bookmark teams.microsoft.com as a fallback so you're never locked out before a meeting.
- Restart your PC at least weekly so background Teams processes don't pile up.
- If you're on a managed/corporate device, ask IT to confirm the required Teams network endpoints aren't blocked by your firewall or proxy.
Related Errors We Cover
- Windows 11 Update Failed (0x800f0922 / 0x80073712) — Fix
- Wi-Fi Not Working After a Windows Update
- Chrome STATUS_BREAKPOINT Error
- Chrome Keeps Crashing on Windows 11 — Fix
- Full error code library →
Frequently Asked Questions
Why is Microsoft Teams not working today?
If Teams won't load for everyone in your organization at once, it's almost always a Microsoft Teams service outage rather than your PC. Check the Microsoft 365 admin center service health and Downdetector first. A reported spike of Teams sign-in and "Connecting" failures occurred on June 16, 2026. If it's only you, the cause is usually a corrupted Teams cache or a stale credential token — clear the cache and sign back in.
What does error caa70004 or caa20004 mean in Teams?
Both are Teams authentication errors. They mean Teams couldn't validate your sign-in token with Microsoft Entra ID (Azure AD), usually because of a corrupted cached credential, a network/proxy block, or an incorrect system clock. Clearing the Teams cache (Fix 3), removing cached Office credentials in Credential Manager (Fix 4) and signing in again resolves the large majority of cases.
How do I clear the Microsoft Teams cache?
Fully quit Teams first. For classic Teams, delete the contents of %appdata%\Microsoft\Teams. For new Teams (ms-teams), clear %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache. Then relaunch Teams and sign in. Clearing the cache doesn't delete your chats or files — they're stored in the cloud.
What's the difference between classic Teams and new Teams?
Classic Teams is the older Electron-based desktop app that stores data under %appdata%\Microsoft\Teams. New Teams (the ms-teams app) is the faster rebuilt client installed as a Windows app package, with its cache under %localappdata%\Packages\MSTeams_8wekyb3d8bbwe. The fixes are similar, but the cache locations and reinstall method differ.
How do I fix Teams stuck on "Connecting"?
Teams stuck on "Connecting" is usually a network, proxy or date/time problem. Confirm Teams isn't down, check your system clock is correct, flush DNS with ipconfig /flushdns, temporarily disable any VPN or strict proxy, and clear the Teams cache. If your company uses a firewall, the required Teams endpoints may be blocked — a technician or your IT admin can confirm.
Can I use Teams while the desktop app is broken?
Yes. Open teams.microsoft.com in Edge or Chrome and sign in. The Teams web app gives you chat, meetings and calls and is a reliable stopgap while you repair the desktop client. It's also a quick way to confirm whether the problem is the app or your account.
Will I lose my chats or files if I reinstall Teams?
No. Your Teams chats, channels, files and meeting history live in Microsoft 365 in the cloud, not in the local app. Clearing the cache or reinstalling Teams only removes local temporary data — everything reloads from the cloud the next time you sign in.
How long does it take to fix Teams not working?
Checking the status page takes under a minute. Clearing the cache and re-signing in takes 3–5 minutes. Repairing or reinstalling the new Teams client takes 5–15 minutes. If it's a Microsoft outage you simply wait for service to be restored. Book a remote session or call (888) 711-9428 if you'd rather have it done for you.
Comments
Got Teams stuck on "Connecting" or error caa70004 / caa20004? Tell us which fix worked below.
Leave a Comment