KB5132061 Stuck? Microsoft Says Windows 11 Fix Lands by Friday
Microsoft's November update fails with 0x800f0993 on PCs that took the October preview. An automatic repair arrives within 24 to 48 hours, so most can wait.
Hakkı ALKANPublished 3 min read
KB5132061, the Windows 11 security update Microsoft shipped on November 10, 2026, is failing to install on some PCs, stalling midway or looping with errors such as 0x800f0989 and 0x800f0993. Microsoft says only devices that installed the optional October preview update are hit, and an automatic repair should reach them by Friday, November 13.
Microsoft confirmed the problem on November 11 in a service alert seen by BleepingComputer. In short: if your PC keeps retrying the November Patch Tuesday update (Microsoft's monthly security release on the second Tuesday), the fix is coming to you, and you do not need to do anything yet.
Which PCs are affected by the KB5132061 install failure?
The trigger is KB5127936, the October 28 non-security preview update that added the customizable right click menu we covered in our Windows 11 preview update report. "Devices that did not install the October 2026 non-security preview update are not affected," Microsoft said. Affected machines may repeatedly attempt the install or show 0x80070306, 0x800f0989 or 0x800f0993.
The update covers Windows 11 26H2 and 25H2 (builds 26300.9974 and 26200.9974) and 24H2 (build 26100.9974). Microsoft calls the number of affected devices "limited" but has not shared a figure.
How do you fix KB5132061 if it will not install?
For PCs that are online and get updates through Settings, Microsoft says the repair runs automatically. "All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT," the company said. After the repair arrives, Windows downloads and installs the November update on its own. If installs still fail after 48 hours, Microsoft says to contact Microsoft Support.
Users have also shared workarounds that Microsoft has not confirmed. According to Neowin, one user traced the failure to Windows Sandbox, the built-in disposable virtual desktop, after the setup log showed a missing Professional.xml file. Turning Sandbox off, restarting and reinstalling worked for them. Others report success with DISM and SFC repairs or clearing the Windows Update cache.
What do you need to do right now?
- Never installed the October preview? You are not affected.
- Stuck on KB5132061? Leave the PC online and wait for the repair until Friday.
- Avoid forcing repeated installs in the meantime.
- Still failing on Saturday? Try the Sandbox workaround, then contact Microsoft Support.
- Do not wipe the PC over this; a full Windows 11 reinstall is a last resort, not a fix for a known issue.
What does KB5132061 change?
Beyond monthly security fixes, the Microsoft release notes list NTLM message signing by default for non-anonymous connections. NTLM is an older Windows sign-in protocol, and signing makes relay attacks, where an attacker forwards a stolen login, harder to pull off. The update also fixes USB Audio 1.0 devices failing with error code 10, an Active Directory printer error 87 introduced in October and an RDP certificate mismatch after the October preview.
| Item | Details |
|---|---|
| Update | KB5132061, released November 10, 2026 |
| Versions | Windows 11 26H2, 25H2, 24H2 |
| Error codes | 0x80070306, 0x800f0989, 0x800f0993 |
| Who is hit | PCs with October preview KB5127936 |
| Fix | Automatic repair within 24 to 48 hours from Nov. 11, 10am PT |
Is this a bigger Windows update problem?
It is a familiar one. Microsoft pulled preview update KB5079391 in March over error 0x80073712 and fixed May install errors with code 0x800f0922. That is the trade-off to weigh: optional preview updates give early access to features, but they also put you first in line for bugs. On a work PC, skipping previews and installing only Patch Tuesday releases is the calmer path.
Microsoft also says there will be no December 2026 preview update, so the next optional release arrives in January 2027.