Ever had Teams just... not open? Turns out it's not your machine.
Microsoft has confirmed an active, unresolved incident — TM1466820 — hitting the Teams desktop client on Windows. Some users can't launch it at all. Others sit through load delays of up to two minutes on first launch.
Here's the part that caught my attention as someone who spends a lot of time in logs: Microsoft's own engineers say their service log and telemetry analysis has been "inconclusive." They're now reaching out directly to affected users for client-side logs — which usually means the root cause isn't reproducible from server-side telemetry alone. That's a slower investigation cycle, not a same-day patch.
The impact is also uneven across tenants, which is itself a clue: it points more toward a backend/telemetry-dependent trigger than a broken client build pushed to everyone.
If you're troubleshooting this for your org, a few things worth knowing:
- Workaround: Teams web and Teams mobile are reportedly unaffected
- This is a different incident from the earlier TM1283300 outage (already resolved)
- It's also separate from the ARM-device Teams/Outlook issue tied to an August security update
I wrote up the full technical breakdown — safe PowerShell checks, Event Viewer review, cache-clearing done correctly, and a mitigation checklist for IT/SOC teams — here:
https://www.xpert4cyber.com/2026/09/microsoft-teams-desktop-client-not-loading-windows.html
Top comments (0)