Microsoft has released updates to resolve startup failures affecting Microsoft Teams and the new Outlook for Windows on ARM-based Windows 11 devices. The issue originated after users installed security updates from August 2026, causing both applications to fail during launch or close abruptly.
Microsoft Resolves App Startup Crashes on ARM Devices
Following the distribution of August security updates, reports emerged that ARM-based Windows 11 PCs were experiencing application crashes. Users attempting to open Microsoft Teams or the new Outlook for Windows encountered immediate app closures. Microsoft subsequently acknowledged the defect on its Windows Release Health portal and confirmed that cumulative updates released in September fully resolve the startup failures.
The company confirmed that the problem was concentrated on systems running Windows 11 version 24H2, 25H2, and 26H1. Systems that had not yet applied recent Store component updates were particularly susceptible to the crash behavior. For users maintaining general desktop environments, tracking broader operating system changes remains essential, such as when Microsoft fixes Windows 11 mouse settings reset bug or addresses core peripheral anomalies.
Affected Surface Hardware and App Behavior
The launch failures specifically affected ARM64 hardware running Copilot+ architectures. Flagship products including the Microsoft Surface Pro 11 and Surface Laptop 7 were among the primary devices exhibiting the issue. Devices equipped with Qualcomm Snapdragon processors faced sudden application terminations right after opening the updated software packages.
Notably, classic desktop versions of Microsoft Office apps were not impacted. Classic Outlook, Word, Excel, and PowerPoint continued to function normally across affected ARM systems. The scope remained isolated to web-derived and modernized app frameworks, which rely on specific shared operating system libraries during initial load routines. Such targeted software disruptions highlight the operational challenges IT teams face when deploying system patches, similar to incidents where a Windows 11 update breaks Active Directory domain logons across corporate networks.
Role of the Auto Super Resolution Package Update
Prior to releasing a permanent Windows Update patch, Microsoft directed impacted users toward a workaround involving the Microsoft Store. Technical telemetry revealed that changes to the graphics subsystem caused modern app entry points to call an outdated Auto Super Resolution component. This mismatch triggered code integrity policy protections, forcing the operating system to terminate the application process immediately to preserve system stability.
By downloading version 1.0.19.0 or higher of the Auto Super Resolution Package via the Microsoft Store, administrators and end users could bypass the crash. The updated package refreshed the shared dependencies, allowing security checks to pass without interrupting application execution. This component is typically associated with AI-assisted resolution upscaling on Copilot+ PCs, but its underlying binaries are shared across system visual pipelines.
Deployment Guidance for Windows 11 Administrators
Microsoft has formally integrated the final patch into the September cumulative updates, designated as KB5124012 and related OS builds. Systems updated through standard Windows Update channels no longer require manual intervention through the Microsoft Store. IT departments managing mixed architecture fleets are encouraged to confirm that their deployment rings include the latest cumulative packages for ARM64 clients.
Enterprise environments utilizing custom system images should ensure that store components are updated during image creation. Devices deployed directly from factory settings often lack updated Store dependencies, leaving them vulnerable to library mismatch issues until initial sync cycles complete. Monitoring ongoing preview builds, such as when Windows 11 beta build adds cross-device resume features, helps system administrators stay ahead of potential component conflicts.
Regular system validation post-patching remains vital for preventing workflow disruptions. Organizations experiencing residual app launch issues are advised to run standard update checks or manually verify build numbers in system settings. With cumulative updates now distributed globally, normal operation has been restored to affected ARM-based Surface devices and compatible hardware partners.
