Microsoft Investigates Update Failures on Upgraded Windows 11 Systems
Microsoft is addressing an issue where some Windows PCs upgraded to Windows 11 24H2 or 25H2 are failing to install the latest monthly cumulative updates, citing error codes 0x80073712 and 0x800f0993.
Microsoft has alerted users to a prevalent issue impacting the installation of recent monthly cumulative updates on specific Windows devices. The problem primarily affects systems that were upgraded from Windows 10 to Windows 11 versions 24H2 or 25H2. Users encountering this bug will typically see update failures accompanied by error codes 0x80073712 or 0x800f0993 when attempting to install the June 2026 cumulative updates.
According to a service alert, the affected systems include those running Windows 10 versions 22H2 and 21H2, as well as Windows 11 version 23H2, which were subsequently upgraded to Windows 11 versions 24H2 or 25H2. Microsoft confirmed that on these impacted devices, monthly Windows updates will cease to install. A review of Windows Update log files on these machines will reveal the specific errors, indicating a corruption within the component store or a missing hydration candidate for rebase operations.
Microsoft has stated that a resolution for this known issue is being deployed. For unmanaged enterprise devices and personal PCs running the Home edition, the fix is expected to apply automatically following a system restart. The company noted that no new devices in these categories should be affected by this problem starting from May 19, 2026, 6:30 p.m. PT, and a simple restart might expedite the application of the resolution.
For other affected devices, Microsoft has incorporated fixes into its June 2026 Patch Tuesday releases. These updates are designed to install automatically during upgrades to Windows 11, thereby preventing the issue from occurring in the first place. Specific KB numbers have been provided for various Windows versions, including KB5094127 for Windows 10 versions 21H2 and 22H2, KB5093998 for Windows 11 version 23H2, and KB5094126 for Windows 11 versions 24H2 and 25H2.
However, Microsoft clarified that this particular issue will not be automatically resolved on systems that have already been upgraded to Windows 11 versions 24H2 or 25H2 and are currently experiencing the update failures. For these specific cases, users are instructed to manually remove the affected package by executing a DISM command in an elevated Command Prompt: dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10.
If the DISM command does not resolve the update problem, users are advised to perform a Windows 11 in-place upgrade as a further troubleshooting step. This process reinstalls Windows while preserving personal files and applications, potentially correcting the underlying corruption that prevents updates.
This incident is the latest in a series of update-related challenges Microsoft has faced in recent months. Previously, in April, an out-of-band update was released to address issues with the March 2026 non-security preview update (KB5079391) that also caused 0x80073712 errors. In January, Microsoft warned of potential update failures in restricted network environments following the installation of optional non-security preview updates. More recently, the company resolved a separate issue causing failures and 0x800f0922 errors with the May 2026 Windows 11 security update (KB5089549).
The ongoing nature of these update installation problems highlights the complexity of maintaining a stable and secure operating system across a vast range of hardware and configurations. Microsoft's continuous efforts to patch and resolve these issues underscore the importance of timely updates for system security and functionality, even as users face temporary disruptions.