74 openlast updated

HomeNovember 2026 patch cycleKB5132061: install fails with 0x800f0993 or 0x800f0989

Known issueEnterpriseEnd-user apps

KB5132061: install fails with 0x800f0993 or 0x800f0989

Part of November 2026 patch cycle

Vendor
Microsoft
Products
Windows 11 26H2, Windows 11 25H2, and Windows 11 24H2 Enterprise/Education (KB5132061)
Published
· updated
Status
Open

Call: Known issue. Microsoft has confirmed it and is pushing a repair. The November Windows 11 cumulative update, KB5132061, fails to install on some machines with 0x80070306, 0x800f0989 or 0x800f0993. Microsoft added it to the KB5132061 known issues on Nov 11 as “November security update might fail to install on some devices.” It says a repair is “automatically running” on affected devices and should reach them all within 24 to 48 hours of Nov 11, 10 AM PT. That window closes around 11 AM Mountain on Friday, Nov 13. Keep deploying. Give it until Friday, then go after whatever is still stuck on October.

Update, Nov 12: Microsoft confirmed it. The KB5132061 release notes now say: “some devices might be unable to complete the installation. Affected devices might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993.” On the fix: “The resolution for this issue is automatically running in affected devices connected to the internet and using Windows Update in Settings to install updates. No manual action from end-users is required to receive the repair.” Once the repair lands, Windows Update downloads and installs the November update by itself. If a machine still fails after 48 hours, Microsoft says to contact support. Microsoft hasn’t named a cause on the public page. Its symptom line oddly calls KB5127936, October’s optional preview, “the November 2026 Windows security update”. BleepingComputer quotes a fuller version of the notice from Microsoft’s admin center: “This issue affects a limited number of devices that installed the October 2026 non-security preview update (KB5127936). Devices that did not install the October 2026 non-security preview update are not affected.” We couldn’t open that notice ourselves. If you never shipped the October preview, this probably isn’t your problem. One X user reports a different failure, 0x800F0920 (CBS_E_HANG_DETECTED) at 7% during the reboot. That’s a single report and not on Microsoft’s list.

Update, Nov 11 evening: Before Microsoft’s notice, Windows Latest said it had been told Microsoft was investigating, including whether Windows Sandbox is the cause. It also saw the update fail at 99% in its own testing and added 0x800f0922 to the list. The Register noted that some people hit the failure with Sandbox off.

What breaks: Windows Update downloads KB5132061, fails, rolls back and tries again. Windows Latest quotes one failure: “Windows failed to install the following update with error 0x80070306: 2026-11 Security Update (KB5132061) (26300.9974).”

Who’s hit: Windows 11 26H2, 25H2 and 24H2 Enterprise/Education (target builds 26300.9974, 26200.9974 and 26100.9974). According to the admin-center text BleepingComputer quotes, only machines that installed KB5127936 are affected. Microsoft’s repair is aimed at devices that get updates through Windows Update in Settings. It doesn’t say whether WSUS, Configuration Manager or Intune-managed devices get the repair the same way. Don’t assume they do.

Workaround:

  • Wait for the repair on internet-connected machines that use Windows Update. Microsoft says no action is needed.
  • Or install it by hand. Microsoft’s notice points to the manual install instructions: the .msu from the Microsoft Update Catalog, or DISM with the checkpoint updates in the same folder. For 26H2, check the prerequisite first: an update from September 22 or later (such as KB5124010).
  • Community fixes from before Microsoft’s notice still apply if you’re in a hurry. One user found that turning off Windows Sandbox (Disable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM), restarting and retrying got the update through. Others had luck with DISM.exe /Online /Cleanup-image /Restorehealth and sfc /scannow. Neither is Microsoft’s fix.
  • On Friday afternoon, check compliance. Anything still on October build numbers after the 48 hours is a support case, not something to wait out.

Sources: KB5132061 release notes, BleepingComputer, Neowin, Neowin on the Sandbox fix, Windows Latest, Windows Latest, Nov 11, The Register, X report 1, X report 2.

Sources

More from November 2026 patch cycle