Loading story…
Microsoft confirmed that security updates released on or after August 11, including KB5121003, can cause Microsoft Teams and the new Outlook for Windows to crash, close unexpectedly, or fail to launch on ARM-based Windows devices. Affected systems run Windows 11 24H2 or later—including 25H2 and 26H1—with Surface Pro 11 and Surface Laptop 7 among the impacted hardware.
The problem is most likely to affect newly deployed or freshly imaged PCs that have not received current Microsoft Store updates. Microsoft has mitigated the issue by directing administrators and users to update the Auto Super Resolution Package through the Microsoft Store to version 1.0.19.0 or later; a permanent fix is in development for delivery through a future Windows update.
See real exploitation activity before you spend the cycle.
2 events from the most recent confirmed update back to the earliest known activity.
Microsoft published a Windows release health dashboard advisory describing the issue on ARM-based Windows 11 systems. It recommended updating the Microsoft Store Auto Super Resolution Package to version 1.0.19.0 or later as mitigation while a permanent Windows Update fix is developed.
Windows security updates released on or after August 11, including KB5121003, caused Microsoft Teams and the new Outlook for Windows to crash, close unexpectedly, or fail to launch on affected ARM-based Windows 11 devices.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Microsoft’s January 2026 Patch Tuesday release for Windows 11 (notably **KB5074109** for 24H2/25H2) delivered roughly 100+ security fixes (including reported **zero-days**) but also introduced significant reliability regressions. Reported impacts include **system lockups**, **black screens** on systems with Nvidia/AMD GPUs, graphics-related hangs in GPU/DirectX-intensive applications, and application failures such as **Outlook Classic** freezing or failing to launch; additional issues were reported with File Explorer behavior and cloud-backed storage workflows (e.g., OneDrive/Dropbox) causing apps to become unresponsive when saving or syncing data.
Jun 29, 2026
Microsoft has confirmed three known issues affecting **Windows 11 26H2**, which shares its servicing branch with 25H2 and 24H2. A September update can break USB Audio Class 1.0 devices, removing audio input and output and potentially freezing or crashing Sound settings. Enterprise devices using Active Directory and Credential Guard can also fail to sign in when Machine Identity Isolation causes machine accounts to lose their secure channel. A separate desktop-loading issue, first linked to the August non-security preview update `KB5120998`, can leave some users at a black screen after sign-in because the desktop session does not automatically load. The issue particularly affects Azure Virtual Desktop hosts using FSLogix profiles and may generate Windows Explorer crashes in the Application event log; Windows Server is not affected. Microsoft has provided Known Issue Rollback Group Policy packages for affected enterprise versions, while users can manually start `explorer.exe` through Task Manager; it has marked this issue mitigated and is developing a permanent update.
Oct 2, 2026
Microsoft’s January 2026 Windows security updates introduced regressions that disrupted enterprise endpoints, including **Remote Desktop authentication failures** affecting access to *Azure Virtual Desktop* and *Windows 365*. After installing `KB5074109` on specific Windows client builds (noted as Builds **26200.7623** and **26100.7623**), users reported repeated credential prompt/sign-in failures in the **Windows App**, preventing successful remote session establishment; Microsoft acknowledged the issue and issued an **out-of-band** update intended to restore normal Remote Desktop connectivity. Separately, Microsoft confirmed another January patch-related issue on Windows 11 23H2 where some systems with **Secure Launch** enabled may **fail to shut down, restart, or hibernate**, leaving devices running and potentially draining batteries. As a workaround, Microsoft advised forcing shutdown via the command: ```cmd shutdown /s /t 0 ``` Microsoft indicated a permanent fix would be delivered in a future update, but did not provide scope/impact metrics for affected devices.
Jun 29, 2026