If the November 2026 Windows 11 security update, KB5132061, keeps failing or retrying on your PC, you are not alone. Microsoft says the problem hits a limited number of devices that installed the optional October preview update (KB5127936). An automatic repair started rolling out on November 11, 2026 at 10am PT, and Microsoft expects affected PCs to be fixed within 24 to 48 hours. In most cases the right move is to stay online and let Windows Update do its job.
What happened with KB5132061
Microsoft released KB5132061 on November 10, 2026. It moves Windows 11 26H2 to build 26300.9974, 25H2 to build 26200.9974, and 24H2 Enterprise and Education to build 26100.9974. Soon after, users started reporting that the install climbed to 99% and then stopped with an error.
Microsoft then confirmed the issue. Affected devices "might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993." The company also says devices that did not install the October preview update are not affected.
How to tell if your PC is affected
- Open Settings > Windows Update > Update history.
- Look under Quality updates for "2026-11 Security Update (KB5132061)".
- If it says "Failed to install" with 0x800f0993, 0x800f0989 or 0x80070306, you have this issue.
- Scroll down the same list. If you see the October 2026 preview, KB5127936, that matches the cause Microsoft described.
How to fix KB5132061 step by step
- Wait for the automatic repair. Microsoft says no manual action is needed. Keep the PC connected to the internet and keep using Windows Update in Settings. Once the repair lands, Windows downloads and installs the November update by itself.
- Do not pause updates. A paused Windows Update cannot receive the repair. If you paused it, go to Settings > Windows Update and click Resume updates.
- Restart and check again. After a restart, click Check for updates. Give it a few tries over the 48 hour window.
- Still failing after 48 hours? Microsoft advises contacting Microsoft Support. That is the official route.
Workarounds other users reported
These come from users on Microsoft Q&A and Neowin, not from Microsoft. Try them only if you are comfortable with them and the automatic fix has not worked.
- Turn off Windows Sandbox. One user found the update failed only on the PC where Windows Sandbox was on. Search "Turn Windows features on or off", untick Windows Sandbox, restart, and try the update again. Others had the error with Sandbox already off, so this does not help everyone.
- Repair system files, then install manually. One user ran
DISM /Online /Cleanup-Image /RestoreHealthand thensfc /scannowin an admin Command Prompt, downloaded KB5132061 from the Microsoft Update Catalog, and it installed on two PCs. Another user said the manual package failed the same way. On x64, the catalog lists the checkpoint update KB5043080 first, and it must be installed before KB5132061. - Use "Fix problems using Windows Update". Under Settings > System > Recovery, this option reinstalls your current Windows build and keeps your files and apps.
My take: if your PC works normally, waiting is the safest bet. The errors are annoying, but the repair is already rolling out, and none of these tweaks is guaranteed.
Quick answers
What does error 0x800f0993 mean?
A volunteer moderator on Microsoft Q&A calls 0x800f0993 a "hydration" error: Windows cannot rebuild a system file from the update's pieces. For KB5132061, Microsoft ties the failure to the October preview update, and its automatic repair targets exactly that.
Is it safe to skip KB5132061?
Not for long. It is a security update, and it also fixes USB Audio 1.0 devices that failed with error code 10 in Device Manager. Hiding it and forgetting about it leaves your PC without the November security fixes.
My PC still runs Windows 11 23H2. Is this my update?
No. 23H2 gets a separate package, KB5131087, and it is the last one for that version. See our guide on Windows 11 23H2 end of updates to move to a supported release.