"A small percentage of devices running Windows 10, versions 22H2 and 21H2, or Windows 11, version 23H2, that were then upgraded to Windows 11, version 24H2 or 25H2, might fail to install the latest cumulative update," Microsoft warned in a service alert on Tuesday.
How the failure shows up on affected machines
On impacted devices, users attempting to install the June 2026 cumulative updates may see failures recorded as error 0x80073712 or 0x800f0993. Microsoft said those codes appear both in Settings > Windows Update > Update history and in Windows Update log files. The vendor links the codes to specific internal conditions: 0x800f0993 corresponds to PSFX_E_REBASE_HYDRATION_CANDIDATES_MISSING, while 0x80073712 is recorded as ERROR_SXS_COMPONENT_STORE_CORRUPT.
Which devices Microsoft identifies as at risk
Microsoft limited the scope to systems that were running Windows 10 (versions 22H2 or 21H2) or Windows 11 (version 23H2) and were then upgraded to Windows 11, version 24H2 or 25H2. The company framed the population as "a small percentage" of devices that followed those upgrade paths; affected machines subsequently cannot install monthly Windows updates until the issue is addressed.
Microsoft's fixes and user-facing mitigations
For unmanaged enterprise devices and personal PCs (Home edition), Microsoft said a fix will be applied after a system restart. "No new devices in these categories should be affected by this issue starting from May 19, 2026, 6:30 p.m. PT," the company added, and noted that restarting the device may allow the resolution to apply sooner. Microsoft stated that no other action is required beyond a device restart for those categories.
For devices already upgraded to Windows 11, version 24H2 or 25H2 that continue to fail updates, Microsoft advised removing a specific package to unblock update installation. The vendor provided an elevated Command Prompt command to remove that package verbatim:
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10
If removing that package does not resolve the issue, Microsoft advised performing a Windows 11 in-place upgrade as the next mitigation.
Microsoft also said that it released Windows updates in the June 2026 Patch Tuesday cycle which should install automatically during upgrades to Windows 11 and prevent this issue from occurring on new upgrades. The company did not assert those Patch Tuesday updates would retroactively fix already-upgraded systems without the steps outlined above.
What this means for technologists, enterprise IT, and end users
- Technologists and security teams: Check Windows Update history and the update log for the two error codes (0x800f0993 and 0x80073712). For unmanaged enterprise endpoints and Home edition PCs, plan for user-initiated or scheduled restarts so the automatic fix can apply after May 19, 2026, 6:30 p.m. PT. For already-upgraded devices that still fail, be prepared to run the dism remove-package command or to perform in-place upgrades where necessary.
- Enterprise IT and procurement leaders: Note the distinction Microsoft made between unmanaged enterprise devices and other deployments; the restart-based rollout applies to unmanaged enterprise endpoints, so managed fleets may require coordinated remediation steps. Ensure IT support can execute the dism command or a controlled in-place upgrade for users who report persistent failures.
- End users and general consumers: If monthly updates fail and you see the listed errors in Update history, try restarting the device first — Microsoft says that should resolve the problem for many Home and unmanaged enterprise systems after May 19, 2026, 6:30 p.m. PT. If the restart does not help, follow the vendor’s directions to remove the named package using an elevated Command Prompt or seek assistance to perform an in-place upgrade.
Recent context: ongoing fixes to the update process
Microsoft's advisory sits amid a series of recent update-process fixes. The company issued an out-of-band update in April to fix the March 2026 non-security preview update (KB5079391), which also had triggered 0x80073712 errors during deployment. In a separate notice a month later, Microsoft warned of update failures after installing January 2026 optional non-security preview updates in restricted network environments. More recently, it resolved a known issue that caused failures and 0x800f0922 errors when installing the May 2026 Windows 11 security update (KB5089549).
Microsoft's guidance in this advisory is procedural: restart where the vendor has pushed the fix, run the provided dism command where a package blocks updates, and fall back to an in-place upgrade if removal does not work. For recipients of the June 2026 cumulative updates who still see errors, those are the steps Microsoft has published.
Source: BleepingComputer — Microsoft: Some upgraded Windows PCs fail to install monthly updates
