Microsoft says a small slice of Windows PCs upgraded to Windows 11 24H2 or 25H2 may fail to install the June 2026 cumulative updates, showing errors 0x80073712 or 0x800f0993. A fix will roll out after a restart for unmanaged PCs and some enterprises, while oth
For the second straight month of Windows Patch Tuesday drama, Microsoft is telling customers to expect a snag—this time during the install of June 2026 cumulative updates.
The problem is aimed at a narrow group: devices that were upgraded to Windows 11 24H2 or 25H2, after running Windows 10 versions 22H2 or 21H2, or Windows 11 version 23H2. Microsoft warned Tuesday that a “small percentage” of those systems might fail to install the latest monthly updates.
On affected PCs, the failures show up during the attempt to install the June 2026 cumulative updates. Users may see error 0x80073712 or 0x800f0993.
Microsoft also described what these failures look like once the update attempt is done. After encountering the issue, devices cannot install monthly Windows updates. In Windows Update. under Settings > Windows Update > Update history. the updates may show as failed with error 0x80073712/0x800f0993.
When Microsoft checks the Windows Update log files on impacted systems, the same story repeats in different error codes. Users will see error 0x800f0993 (PSFX_E_REBASE_HYDRATION_CANDIDATES_MISSING) or 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) triggered when trying to install the latest updates.
Microsoft says the fix is headed through the normal update pipeline—but timing matters. For all unmanaged enterprise devices and personal PCs (Home edition). the resolution will roll out “following a system restart.” No extra steps are required beyond rebooting the device. and Microsoft says the rollout is scheduled so that no new devices in these categories should be affected starting from May 19. 2026. 6:30 p.m. PT. Restarting could allow the resolution to apply sooner.
That still leaves a separate lane for other affected devices. Microsoft cautioned that this known issue “will not be addressed” on devices that have already been upgraded to Windows 11 version 24H2 or 25H2.
For those systems, Microsoft instructs users to remove the affected package to unblock update installation. The recommended step is to run the following command in an elevated Command Prompt:
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10
If that doesn’t restore the ability to install updates, Microsoft’s guidance is to perform a Windows 11 in-place upgrade.
What makes the situation feel especially frustrating for IT teams and regular users alike is how it fits into a recent pattern of Windows Update install problems. Microsoft has already issued multiple fixes over the past several months. In April. it released an out-of-band update to fix the March 2026 non-security preview update (KB5079391). after a known issue also triggered 0x80073712 errors on Windows 11 during deployment. One month later. Microsoft warned that Windows Update failures could occur after installing the January 2026 optional non-security preview updates in restricted network environments. More recently. it resolved another known issue causing failures and 0x800f0922 errors when installing the May 2026 Windows 11 security update (KB5089549).
The latest June 2026 issue doesn’t affect everyone—but for the users caught in that “small percentage,” it blocks monthly updates until the right remedy lands, and in some cases it forces a restart, a package removal, or a full in-place upgrade.
Microsoft Windows Update Windows 11 24H2 Windows 11 25H2 0x80073712 0x800f0993 June 2026 cumulative update Patch Tuesday troubleshooting