ARM Windows apps fixed after patch

The bug hit quietly, at the worst possible time: fresh ARM-based Windows machines, set up and patched, that simply refused to open Teams or the new Outlook. Microsoft confirmed the problem last week and, on Tuesday evening, said it has now fixed it in the September 2026 Patch Tuesday cumulative updates.

What makes the episode worth a closer look is what it says about where the failure lived — not in the apps themselves, but in the order in which a new Windows machine gets its software.

How the failure surfaced

According to Microsoft's Windows release health update, the issue affected ARM-based devices running Windows 11 24H2 or later — the company names the Surface Pro 11 and Surface Laptop 7 as examples. The trigger was narrow and specific. This is not a bug that arrives on a machine that has been running for months and has been kept current through the Store. It is a bug that catches machines at a particular stage of their life.

Microsoft's own description of the failure mode points to the launch sequence as the vulnerable point — not file corruption, not a crash on use, but the moment the application tries to start.

The company's guidance for affected users was to update the Auto Super Resolution Package, a component that lets Copilot+ PCs use AI to smooth gameplay — an unusual workaround for an app-launch failure, and one that Microsoft offered without disclosing why it helped. At the time, the root cause had not been made public.

What Microsoft told users

The clearest account of the problem came from Microsoft's release health documentation itself, which described both the scope and the limits of the bug:

"After installing Windows security updates released on or after August 11, 2026, (KB5121003), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7."

— Microsoft, in a Windows release health update

The company also drew a boundary around what was affected, which matters for anyone trying to work out whether they were in the blast radius. The same notice stated that classic Outlook, Word, Excel and other applications are not known to be affected, and added that the failure is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates.

That last detail is the key to the whole incident: the bug was not evenly distributed. It favored machines that had Windows security updates applied before their Store components were brought up to date.

Why fresh installs were the target

New and freshly imaged PCs sit in a gap that long-running machines have already passed through. On an older device, Store components have been updated many times over, often automatically, and the machine's software estate is settled. On a machine set up from scratch, Windows updates and Store updates arrive on separate schedules, and the security update can land first.

Microsoft never published a root cause for the failure, so the precise mechanism linking the August security updates to app launch remains undisclosed. What the company did provide is the shape of the affected population — ARM-based hardware, Windows 11 24H2 or later, security updates since the August 2026 Patch Tuesday, and Store packages not yet updated.

For IT teams, the practical lesson shows up in deployment images. A freshly imaged ARM device that receives its Windows patches before its Store components may reproduce this failure, while an identical device updated in the other order would not.

The September patch closes it

Microsoft's fix arrived with the September 2026 Patch Tuesday cumulative updates. In its KB5124012 guidance, the company confirmed the resolution and urged users to apply it:

"This issue was resolved by Windows updates released September 8, 2026 (KB5124012), and updates released after that date."

— Microsoft, in a Windows release health update

The company's accompanying recommendation was to install the latest update for the device, noting that it contains important improvements and issue resolutions, including this one. Because the fix shipped inside the monthly cumulative update rather than as a standalone patch, affected users get it through the same channel that caused the problem — provided they install the September release or later.

Microsoft's release health page for the ARM device issue is the authoritative record of which builds carry the fix and remains the reference point if the failure reappears on a device that has not yet taken the September update.

A month of patch-related breakage

The Teams and Outlook launch failure was not an isolated slip. It belongs to a cluster of issues tied to Windows updates released in August 2026, several of which Microsoft has had to acknowledge and fix in sequence.

• On August 24, Microsoft confirmed that August 2026 .NET Framework updates were breaking printing and PDF exporting in apps built on the Windows Presentation Foundation UI framework.
• Days later, the company began rolling out a fix for a bug caused by peripherals with built-in RGB lighting, which triggered gaming problems and system crashes with EXCEPTION_ACCESS_VIOLATION errors on Windows 11 systems.
• Microsoft also told customers to ignore alerts claiming Microsoft Defender Antivirus had been turned off after installing the previous month's updates.
• This week, the company resolved known issues that wiped custom mouse settings and Windows desktop settings on some Windows 11 systems following the KB5120998 August 2026 preview update.

Across these cases the pattern is similar: a scheduled update lands, a subset of systems behaves unexpectedly, and the fix arrives in a later scheduled release. The ARM launch bug differs in one respect — it struck newest hardware and freshest installs, the machines least likely to have accumulated the Store updates that shielded everyone else.

What ARM users should do now

For anyone running Windows 11 24H2 or later on ARM hardware, the immediate action is straightforward: confirm that the September 2026 cumulative update, or any later release, is installed. Devices that have taken KB5124012 or a subsequent update are covered for this specific issue.

Machines still on August or earlier updates — particularly recently imaged devices that have not yet received Store updates — remain exposed to the original failure and should be brought current. The temporary workaround Microsoft offered while the bug was open, updating the Auto Super Resolution Package, is no longer the recommended path now that a permanent fix exists.

Administrators managing fleets of ARM laptops should also check imaging and provisioning sequences. If a build process applies Windows security updates before Store components are refreshed, it may be worth reordering those steps or verifying that the September patch is included in the image, so the condition that triggered this bug does not recur on the next batch of devices.

Why the sequencing matters

The headline fix is simple — install the September update — but the incident is a reminder that on modern Windows, update order is part of the security surface. A machine can be fully patched against known vulnerabilities and still be broken in ways that keep users out of the applications they need to work, which is its own form of risk: unlaunchable mail and chat clients push people toward workarounds, personal accounts, and unsanctioned tools.

For IT teams provisioning ARM hardware, this episode suggests that "fully updated" is not a single state. Windows updates and Store updates travel on different clocks, and a device can sit briefly in a configuration that no one intended and that no dashboard flags as unusual.

Microsoft has not explained the root cause behind the ARM launch failure, and that gap leaves a residual question for anyone running these devices at scale: the fix is documented, but the mechanism that produced the bug is not. Until that changes, the safe assumption for fleet managers is that fresh images on ARM hardware deserve a verification step after patching — opening Teams and the new Outlook once, on a test device, before the image goes wide.