Microsoft investigates Teams desktop client launch failures on Windows

Microsoft has confirmed a known issue that prevents some Windows users from opening the Teams desktop client. The advisory is tracked as TM1466820 in the Microsoft 365 admin center service health dashboard, and it went up on Thursday 3 September 2026 at 16:45 EDT.

The symptom is narrow but obvious to anyone who hits it. On first launch of Teams on a Windows device, the client either fails to load at all, or takes as long as two minutes to become usable. Microsoft's service health post is titled around loading delays when opening the Teams desktop client on Windows devices.

The company has not named a build, a channel, a region, or a tenant type. Per the incident report seen by BleepingComputer on 4 September 2026, it describes the scope as some users within affected organisations, which is service health language for an issue with no clean fingerprint yet.

The advisory covers the Teams desktop client on Windows. Teams on the web and the Teams mobile apps are not affected, which is why Microsoft can offer them as a fallback.

There is no published user count, no device count, and no list of affected regions. Microsoft has said only that some users inside impacted organisations see the problem, with the first launch of the day as the trigger. That pattern matters for helpdesks: the reports will cluster in the first hour of the working day and then go quiet, which makes the issue easy to under-count from ticket volume alone.

A second, separate advisory affects a different group. TM1466659 covers Teams for Mac users who cannot join calls or meetings.

Microsoft says it is analysing service logs and telemetry, and that it has reached out to some affected users to collect more diagnostic data. Reaching out for client logs usually means the telemetry alone hasn't isolated the failure, so the investigation is in an evidence-gathering phase rather than a rollback.

That is a contrast with an earlier Teams launch incident. In April 2026, under TM1283300, Microsoft traced desktop launch failures to a regression in the Teams client build caching system and reverted the offending service update within hours. Nothing published so far ties TM1466820 to a service change, and Microsoft has not committed to a resolution time.

On the Mac side, Microsoft first pointed at a code change in the call and meeting service infrastructure, then walked that back and said it is reassessing its root cause understanding.

There is no fix to deploy, so the work is communication and triage. Microsoft's stated workaround is Teams on the web at teams.microsoft.com, or the Teams mobile app on iOS and Android.

1. Post a banner or channel notice telling staff to open Teams in a browser if the desktop client hangs, rather than rebooting or reinstalling.
2. Tell first-line support not to burn time on cache clears and reinstalls for this symptom. Neither addresses a service-side issue.
3. Follow TM1466820 in the Microsoft 365 admin center, and turn on service health notifications if they are off.
4. Log affected users, with device and Teams version, in case Microsoft asks for samples.

This advisory lands on top of two other recent problems, and they are worth keeping apart when you triage.

The first is an ARM issue. Microsoft confirmed on 1 September that Teams and the new Outlook for Windows can fail to launch or close unexpectedly on ARM-based devices such as the Surface Pro 11 and Surface Laptop 7, after security updates released on or after 11 August 2026, including KB5121003. Classic Outlook, Word and Excel are not known to be affected. The published workaround is to install version 1.0.19.0 or later of the Auto Super Resolution Package from the Microsoft Store.

The second is the Microsoft 365 authentication incident that ran from 31 August to 3 September, tracked as EX1464935 and MO1465074. Microsoft's post-incident communication lists Teams among the affected workloads, with stale presence, search failures, and problems creating or editing channels. That one is closed, with a post-incident report published on 5 September 2026.

So three different Teams failure modes in a fortnight, on three different causes. If a user cannot launch Teams on a Surface Pro 11, check the ARM workaround before assuming TM1466820.

Three things will tell you where this is going.

• Whether Microsoft names a service-side change. If it does, expect a revert and a fast close, as happened in April 2026. A client-side fault would mean waiting on a Teams client update.
• Whether TM1466820 and TM1466659 converge. Both involve Teams service infrastructure and both lack a confirmed root cause, but Microsoft is treating them as separate incidents.
• The September Patch Tuesday on 8 September 2026, the likely vehicle for the permanent ARM fix. It will not touch TM1466820, but it should remove one of the three failure modes from your queue.

Affected Windows users lose the Teams desktop client on first launch, or wait up to two minutes for it. Work continues through Teams on the web or mobile, so the cost is lost time and support load rather than a loss of service.

Security: None reported. This is a service reliability issue with no security dimension published by Microsoft.

Microsoft has confirmed, under TM1466820, that some Windows users cannot open the Teams desktop client or wait up to two minutes for it. The investigation is still at the log-gathering stage, and the only remedy on offer is the web or mobile client.