Computer Repair · November 15, 2026 · ComputerKing Team

Windows 11 November Update KB5132061 Won't Install, Error 0x800f0989: Which PCs Are Affected and How Long Microsoft's Automatic Fix Takes

Microsoft's November security update for Windows 11, KB5132061, released on 10 November, fails to install on some PCs with error 0x800f0989, 0x80070306 or 0x800f0993, and may keep retrying. Microsoft has confirmed that only PCs that installed the October preview update KB5127936 are affected; PCs without that preview are not. The fix began rolling out automatically on 11 November and takes 24 to 48 hours; once repaired, the PC downloads and installs the November update on its own. This guide shows how to confirm whether you are affected, what not to do while waiting, and what to check if it still fails after the fix window. Pricing is quoted case by case.

Key points

On 10 November 2026, Microsoft released the November security update for Windows 11, KB5132061. On some PCs it fails to install, showing error 0x800f0989, 0x80070306 or 0x800f0993, and it may keep retrying. Microsoft has confirmed that the problem only affects PCs that installed the October preview update KB5127936; PCs without that preview are not affected. The fix began rolling out automatically on 11 November at 10am Pacific Time and takes 24 to 48 hours; once repaired, the PC downloads and installs the November update on its own, with nothing for you to click. This guide shows how to confirm whether you are affected, what not to do while waiting, and what to check if it still fails after the fix window.

1. What happened: the November update won't install, but only on PCs that took the October preview

• Update numbers: for Windows 11 25H2 and 26H2, and Enterprise and Education editions of 24H2, the November security update is KB5132061. For 23H2 it is KB5131087.
• Which PCs are affected: Microsoft has confirmed that KB5132061 fails to install on some PCs that installed the October preview update KB5127936, released on 28 October. That preview itself was issued to fix a Remote Desktop connection failure.
• Error codes: a failed install shows one of 0x800f0989, 0x80070306 or 0x800f0993, and the PC may keep retrying the install.
• PCs without the preview are not affected: if your PC never installed KB5127936, the November update should install normally.
• Microsoft has not said how many PCs are affected, or why it happens — only that the scope is limited and the fix is already rolling out.

2. How to confirm whether you are affected

1. Open Settings, go to Windows Update, and check whether the November update shows as failed, with one of the three error codes above.

2. Click Update history and check whether KB5127936 was installed in October. Only PCs with that preview in their history belong to the affected group.

3. Also check in the history whether KB5132061 has failed repeatedly, or just once.

4. Do not guess from how the PC feels: some PCs fail updates for other reasons, such as low disk space or third-party antivirus getting in the way. The error code and the update history are the evidence.

3. How Microsoft's fix works: it arrives automatically, nothing to click

• The fix began rolling out on 11 November and Microsoft says it reaches affected PCs within 24 to 48 hours, so roughly by 13 November.
• It runs automatically: a PC connected to the internet and using Windows Update receives it without any download or click from you.
• After the repair, the PC automatically downloads and installs KB5132061. You do not need to try installing it manually again.
• By 15 November the fix should have finished rolling out. If your PC still cannot install the update, waiting longer is not the answer — run the checks in the next section.

4. While waiting for the fix, do not do these things

• Do not download a so-called KB5132061 repair tool or update fixer from an unfamiliar website: fake updaters are a common malware route. The official fix is delivered only through Windows Update.
• Do not switch off Windows Update entirely or disable your security software to force the update through: a failed update does not mean the PC is unprotected — the older updates are still there. Do not tear down the whole defence for one update.
• Do not delete the SoftwareDistribution folder or run commands from the internet to clear the update cache: that can leave the update state more confused and can affect updates that are already installed. If it ever needs clearing, back up first.
• Back up first, before doing anything: with your important files backed up, you have a way back whether you wait for the fix or try again yourself.

5. If it still fails after the fix window, what to do

1. Restart once, then go to Windows Update and click Check for updates. After the repair completes, a restart is sometimes needed before the download starts.

2. Confirm the repair has arrived: check Update history to see whether KB5132061 now shows as installed. If it still fails, note the error code.

3. Check disk space: the system drive needs enough free space. Too little space can make an update fail, and the error code may be a different one.

4. Run the built-in troubleshooter: find the Windows Update troubleshooter in Settings and let the system check the update components itself.

5. If the same error code keeps coming back: do not retry endlessly. Note the error code and the update history, and bring the PC in for a check — retrying a dozen times will not make it suddenly install, it only wastes time.

6. Do not confuse it with the other November known issue: activation failures

• The November update has another known issue, affecting organisations that activate Windows from the command line: running slmgr.vbs with the /skms-domain or /ipk parameter fails with error 0x80041008.
• The scope is different: Windows 10 21H2 and 22H2, Windows 11 23H2, and Windows Server 2019, 2022 and 2025. Ordinary users on 24H2, 25H2 and 26H2 are not affected.
• PCs that are already activated stay activated. Nothing becomes unactivated out of nowhere. The issue only blocks new activations and reconfiguration — it does not stop your PC from working.
• Microsoft says a fix is coming within days. If you see 0x80041008, that is a different issue, not KB5132061 failing to install.

7. When to bring it in

• After the fix window, KB5132061 still fails with error 0x800f0989, 0x80070306 or 0x800f0993.
• The update history shows other error codes, or you suspect you clicked a fake update tool.
• The PC is a work machine with updates managed by policy, which you cannot change yourself.
• In these cases, bringing the PC in with the error code and the update history is faster than trying things one by one on your own.