Microsoft warns of update failures on certain Windows 11 builds

Microsoft has alerted administrators that a subset of Windows 11 devices upgraded to the 24H2 and 25H2 releases cannot apply the June 2026 cumulative updates. Affected machines display error codes 0x80073712 or 0x800f0993 when the installation process stalls. The issue appears after a system restart and blocks further monthly patches.

The problem stems from a component store corruption that occurs during the upgrade path from Windows 10 or earlier Windows 11 versions to the newer 24H2 and 25H2 builds. Microsoft notes that the error messages originate from the Windows Update stack and indicate missing hydration candidates or a corrupted component store. While the company expects a fix to reach unmanaged enterprise devices and personal PCs after a restart, devices already running the problematic builds require manual intervention.

For systems that have already moved to 24H2 or 25H2, administrators can remove the offending package by executing the following command in an elevated command prompt:

dism /online /remove-package /packagename:Package_for_RollupFix31bf3856ad364e35amd64~~26100.1742.1.10

If the command does not restore update functionality, a clean in‑place upgrade of Windows 11 is recommended. Microsoft has also published a set of KB articles that detail the specific client versions and the corresponding resolved KBs. Those references can be found at the official release health page and the June 2026 Patch Tuesday advisory.

The company emphasizes that no new devices should encounter this issue starting from May 19, 2026, after the initial rollout window. Restarting the machine may apply the resolution more quickly. For all other affected devices, the June 2026 Patch Tuesday updates are intended to install automatically and prevent the error from recurring.

Additional context can be found in Microsoft’s service alert and the related KB articles:

• https://learn.microsoft.com/windows/release-health/windows-11-24h2
• https://support.microsoft.com/en-us/topic/june-2026-windows-update-kb5094127

Security teams often monitor update health to ensure that patch cycles proceed without interruption. The Picus whitepaper on breach and attack simulation illustrates how proactive testing of SIEM and EDR rules can reduce the window of exposure when updates fail to deploy. Understanding the root cause of these errors helps organizations plan remediation steps and avoid downtime during critical patch windows.

Make sure to restart the device after applying the mitigation command and verify the update history in Settings > Windows Update > Update history. If the error persists, consider reaching out to Microsoft support for a deeper analysis.