Home/Troubleshooting guide
Windows on Arm guide

Teams or Outlook not opening on Windows 11 Arm? Update first

Short answer: Microsoft resolved the Windows on Arm bug that could make Teams and new Outlook close at launch after the August 2026 updates. Install the latest Windows update for the PC first. If that update is unavailable and the exact symptom matches, update Auto Super Resolution Package to version 1.0.19.0 or later through Microsoft Store.

Unbranded laptop showing two blank application panels and an abstract update progress ring
Start with the permanent fix. Save your work and record the Windows version and OS build. Install the latest supported Windows update, restart if requested, and test Teams and new Outlook again. Use the Microsoft Store package step only when the resolving Windows update is unavailable and the PC matches the affected pattern.
Keep the repair narrow. Do not uninstall security updates first, download packages from mirrors, disable antivirus or organization controls, edit the registry, replace unrelated runtimes, or reset Windows. Do not post mail, meeting, account, token, or organization data in a public diagnostic.

The launch issue is resolved

Microsoft says the issue affected Teams and new Outlook on Arm-based PCs after the August 11, 2026 Windows updates. It was most likely on new or freshly imaged computers that had not received Microsoft Store updates. Microsoft lists classic Outlook, Word, and Excel as not known to be affected by this incident.

The status changed after the original reports. Microsoft says Windows updates released September 8, 2026 and later resolve the problem, including KB5124008. The current fix is the latest Windows update for the device, not removal of the August security update.

Check whether the PC matches

Open Settings > System > About. Record the processor, System type, Windows edition, version, and OS build. The issue in Microsoft's note applies to an ARM-based processor. An x64 or x86 PC needs a different launch check.

ObservationDoes it match?Next route
ARM-based processor, with Teams or new Outlook closing at launch after an August 2026 updateYes, especially on a new or freshly imaged PC without Store updates.Install the latest Windows update.
Classic Outlook, Word, or Excel opens normallyThis is consistent with Microsoft's narrow scope.Continue with the update sequence.
Teams opens but stays on a loading screenThat is a different symptom.Use the Teams loading guide.
Outlook opens but search does not workThat is a different symptom.Use the Outlook search guide.
Several unrelated apps fail, or the PC is not Arm-basedNo.Preserve the exact errors and use the support path for the broader failure.

Check Settings > Windows Update > Update history. Record the newest cumulative update and its date. Do not rely on the August update alone; the question is whether the PC has received a September 8 or later resolving update.

Install the latest supported Windows update

Save unsent messages, meeting notes, and other work. Keep a separate backup of important files. Open Settings > Windows Update and check for updates. Install the latest supported cumulative update offered for the device, then restart if Windows requests it.

After restart, read back the Windows version and OS build. Open the same Teams installation and the same new Outlook profile that failed before. Record whether each app opens, closes immediately, shows an error, or reaches its normal window.

If Windows Update itself is stuck or returns an error, stop mixing repairs and use the Windows Update guide. A failed update must be understood before the Store fallback can prove anything.

Use the Microsoft Store fallback only when needed

If the latest resolving Windows update is not available and the computer matches the exact Arm launch issue, open Microsoft Store. Go to Downloads and select Check for updates. Microsoft says Auto Super Resolution Package version 1.0.19.0 or later is the workaround.

Read the installed package version back after the Store update, then repeat the same Teams and new Outlook launch tests. Do not sideload the package, use a third-party download site, or install a similarly named file from a search result.

If Microsoft Store is blocked, managed, or unavailable, do not bypass the restriction. Give the administrator the processor type, Windows build, update history, affected apps, and the required package version.

Handle a different failure as a different problem

A launch failure that remains after the resolving Windows update may have another cause. Preserve the app version, Windows build, exact error, Event Viewer time, account scope, and whether another user profile has the same result. Do not keep replacing packages after the original signature no longer fits.

A broad Office failure, a sign-in loop, a Teams loading screen, broken Outlook search, or a crash on x64 Windows belongs to its own diagnostic path. The 2026 Arm incident does not prove that Teams, Outlook, Windows, or the processor caused every later launch failure.

Stop at organization controls

On a work or school computer, Windows Update and Microsoft Store can be governed by policy. Do not disable endpoint protection, detach the device from management, change update rings, remove organization accounts, or share confidential logs. Ask the administrator to apply the resolving Windows update or approved Store package.

A useful handoff includes the device model, processor and System type, Windows edition and build, newest cumulative update, Store package version, app versions, timestamps, exact behavior, and whether classic Outlook, Word, or Excel still opens.

Where OmniMend fits

OmniMend's current Windows host requirement is Windows 10 or 11 x64. It is not presented as an installer for the affected Windows on Arm PC. Check the current download requirements before installing it on any computer.

On a supported x64 Windows computer, OmniMend can organize supported local diagnostic evidence for that computer. It does not install Microsoft's Arm fix, bypass organization policy, or guarantee that Teams or Outlook will open. Use Microsoft or the device administrator for the affected Arm system.

Editorial sources

Checked October 13, 2026 against Microsoft's current notes for KB5121003 and the Windows Update FAQ. Microsoft supplies the affected Arm scope, the distinction between new Outlook and classic Outlook, the fresh-image pattern, Auto Super Resolution Package version 1.0.19.0 or later, and the September 8 or later resolution. Same-run reporting from BleepingComputer and Windows Central was checked for the original symptom language, but their unresolved framing predates Microsoft's current status. Current search results were also reviewed. They do not prove that every Teams or Outlook launch failure has this cause. OmniMend added the match table, evidence record, safety stops, internal routes, managed-device boundary, and current product requirement. OmniMend is not affiliated with Microsoft.

Apply the current fix.
Retest the same launch.

Keep the processor type, Windows build, update history, package version, and app result for support.

Check OmniMend requirements