Loading story…
Microsoft published out-of-band Windows updates KB5085516 and KB5086672 for OS builds 26200.x and 26100.x, distributing them as standalone .msu packages through the Microsoft Update Catalog rather than standard servicing channels alone. The company said the updates can be deployed to live Windows PCs as well as offline or mounted installation media, with supported installation methods including DISM, PowerShell, and the Windows Update Standalone Installer.
Microsoft warned that administrators must account for package prerequisites and installation sequencing when deploying the updates manually. Its guidance says organizations can either install all required MSU packages together so dependencies are resolved automatically, or install each package individually in the prescribed order; for KB5086672, that includes installing KB5043080 first when using the individual method. Microsoft also noted that the latest cumulative update includes AI component updates that apply only to Windows Copilot+ PCs and will not install on standard Windows PCs or Windows Server systems.
See real exploitation activity before you spend the cycle.
5 events from the most recent confirmed update back to the earliest known activity.
Microsoft published support guidance for KB5082063 for OS Build 26100.32690. The notice explains installation from the Microsoft Update Catalog using either combined MSU deployment or individual package installation in required order, including prerequisite KB5043080, and notes that included AI component updates apply only to Windows Copilot+ PCs.
Microsoft published support guidance for KB5083769 for OS Builds 26200.8246 and 26100.8246. The notice explains manual installation from the Microsoft Update Catalog using either combined MSU installation with automatic prerequisite discovery or individual MSU installation in required order, and notes that included AI component updates apply only to Windows Copilot+ PCs.
Microsoft published support guidance for KB5083768 for OS Build 28000.1836. The notice explains manual installation from the Microsoft Update Catalog for running systems and mounted installation media, and notes that included AI component updates apply only to Windows Copilot+ PCs.
Microsoft published support guidance for out-of-band update KB5086672 for OS Builds 26200.8117 and 26100.8117. The documentation describes manual installation methods, notes prerequisite KB5043080 when installing individually, and states that included AI component updates apply only to Windows Copilot+ PCs.
Microsoft published support guidance for out-of-band update KB5085516 for OS Builds 26200.8039 and 26100.8039. The guidance explains manual installation from the Microsoft Update Catalog, including prerequisite handling and deployment to running systems or mounted installation media.
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.
5 references tracked. Mallory keeps watching after this page renders.
support.microsoft.com
Open sourcesupport.microsoft.com
Open sourcesupport.microsoft.com
Open sourcesupport.microsoft.com
Open sourcesupport.microsoft.com
Open sourceMap 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 released an out-of-band Windows 11 update, **KB5086672**, to fix a widespread installation failure affecting versions **25H2** and **24H2** after the March preview update **KB5079391** triggered repeated setup errors. Affected systems entered a loop of failed update attempts and reported error code `0x80073712`, which indicates missing or corrupted update files. Microsoft withdrew the faulty preview release and replaced it with a cumulative package that also carries forward March security and quality fixes. The emergency package moves impacted devices to OS builds **26200.8117** and **26100.8117** and also updates several local AI components. Microsoft said the fix is available through **Windows Update**, the **Microsoft Update Catalog**, and manual installation in Settings, while enterprise administrators can accelerate deployment through **Intune** or **Windows Autopatch** expedited quality updates. Because the release combines the servicing stack and cumulative update, rollback options are limited and manual removal may require **DISM**.
Jun 29, 2026
Microsoft released **KB5089548** for **Windows 11 version 26H1**, advancing systems to **OS Build 28000.2113** and delivering the latest fixes from the **May 2026 Security Updates** guide. The cumulative update is available through standard support channels and the **Microsoft Update Catalog**, and Microsoft said it was not aware of any known issues affecting the release. The package also carries forward non-security improvements from earlier preview and cumulative releases, including more reliable **SSDP** notifications and better compatibility for some games that use embedded web content by reducing the impact of JavaScript errors on in-game features. Microsoft also updated several AI components and bundled the servicing stack update **KB5092761** (version **28000.2103**) to improve update installation reliability.
Jul 12, 2026
Microsoft’s January Windows security updates triggered an unusual **patch-break-patch** cycle that forced multiple out-of-band (OOB) releases after users reported significant regressions. Reporting indicates the Jan. 13 Patch Tuesday update (including `KB5074109`) was followed by an urgent Jan. 17 fix that introduced additional problems, leading to a second emergency OOB update on Jan. 24; impacts cited include Remote Desktop sign-in/authentication failures and broader stability issues such as Outlook freezing and file-system/compatibility problems affecting OneDrive and Dropbox integrations. Microsoft advised customers to move to the latest available update despite the disruption. Separate analysis highlighted that Windows’ long-standing commitment to **backwards compatibility** continues to create persistent exposure and operational risk: many exploited-in-the-wild Microsoft zero-days in 2025 were **elevation-of-privilege** issues rooted in legacy components, reinforcing that “traditional” exploit chains and accumulated Windows tech debt remain a primary driver of both security and patching complexity. Taken together, the coverage underscores that Windows defenders face a dual challenge: rapid deployment of security fixes to reduce exploitation risk, while managing the real possibility that emergency remediation can itself introduce enterprise-impacting outages.
Jun 29, 2026