As of November 11, 2026, some Windows 11 users on versions 24H2, 25H2, and 26H2 (OS Builds 26100.9974, 26200.9974, and 26300.9974) report that the KB5132061 update fails in Windows Update with “0x800f0993” or “0x800f0989.” If your PC is one of them, don’t force repeated installs. Run the standard repair steps once, then pause updates and wait for Microsoft if the install still fails.
What Happened
Neowin reported that KB5132061 fails to download or install on some Windows 11 PCs and returns error 0x800f0993. Other user reports also mention 0x800f0989. Microsoft’s support page lists the update for Windows 11 versions 25H2 and 26H2, and for 24H2 Enterprise and Education editions, though when and how a given PC is offered it can depend on its servicing settings. Windows 11 version 26H1 gets a different November update, KB5132059, so this report doesn’t apply to it.
The report is based on user complaints, not a Microsoft known-issue entry. As of this writing, Microsoft’s KB5132061 support page says Microsoft is “not currently aware of any issues with this update,” and the Windows release health dashboard lists no known issue for these error codes. (Release health does list several older issues that KB5132061 resolves.) The 0x800f0993 failure also appears in a user thread on Microsoft Q&A.
That means any advice to pause and wait is precautionary rather than official guidance. Before you change anything, check two places for an official status:
- The Windows release health dashboard
- The KB5132061 page on support.microsoft.com
Microsoft’s KB5132061 support page confirms a November 10, 2026 release date and lists Windows 11 25H2 and 26H2 (all editions) and 24H2 (Enterprise and Education editions only) as the versions it applies to, at OS Builds 26100.9974, 26200.9974, and 26300.9974. Those are the releases the package targets, not a list of PCs confirmed to hit the error. Neither that page nor the Windows release health dashboard has been verified to name a cause or a fix for the 0x800f0993 and 0x800f0989 errors specifically. Be skeptical of any site that claims a confirmed fix beyond what Microsoft has published.
To find out whether your PC is affected, open Settings > Windows Update and look at the status line near the top.
Next, go to Settings > Windows Update > Update history. Find KB5132061 and read the exact error code listed next to it.
What 0x800f0993 and 0x800f0989 Mean
Both codes fall in the 0x800f09xx range. Microsoft hasn’t published a specific explanation for either code with KB5132061.
Factors worth checking when troubleshooting this range of errors include:
- A corrupted update cache
- A restart that’s still pending
- Too little free disk space
- Damaged system files
This list reflects general troubleshooting knowledge, not a Microsoft diagnosis for KB5132061 specifically. Microsoft hasn’t documented what either code means for this update, and the two may come from different servicing conditions, so neither code tells you the cause on its own.
How It Stacks Up
Microsoft’s general Windows Update troubleshooting guidance includes the built-in troubleshooter, SFC, and DISM, but no source shows whether or how often they clear these particular codes. None of the sources reviewed for this article include incident data measuring how widespread this particular failure is, so here are the options compared by effort and trade-off instead:
| Option | Effort | Downside |
|---|---|---|
| Restart and retry | Low | Fails again if the cause is on Microsoft’s side |
| Troubleshooter + SFC/DISM | Low to medium | Takes some time and may change nothing |
| Pause updates | Low | Delays security fixes until you resume |
| Manual install from Microsoft Update Catalog | Medium | Unverified for this KB, so treat it as a workaround |
| Wait for a superseding update | None | Leaves you a patch behind for a while |
A repair sequence to try:
- Restart the PC, even if Windows doesn’t say a restart is pending.
- Run Settings > System > Troubleshoot > Other troubleshooters > Windows Update.
- Open Terminal as administrator and run
sfc /scannow. - Run
DISM /Online /Cleanup-Image /RestoreHealth. - Free up several GB on the system drive.
Step 5 can be a problem on small drives. If a small system drive keeps running out of space for updates, a larger SSD can give you more headroom long term, provided your laptop supports the upgrade and low space is actually what’s blocking the install.
If you try the Microsoft Update Catalog route, check the prerequisites on Microsoft’s KB5132061 page first. Version 26H2 needs an update released on or after September 22, 2026 (such as KB5124010) and servicing stack 26100.9539 or later. Versions 24H2 and 25H2 need an update released on or after June 10, 2025 (such as KB5060842) and servicing stack 26100.4193 or later.
To see your installed servicing stack, run DISM /Online /Get-Packages | findstr /i "ServicingStack" from an administrator Terminal. The standalone update ships as more than one MSU file (a required checkpoint cumulative update, KB5043080, plus the KB5132061 package itself), and Microsoft’s page says they must be installed in a specific order, so use the instructions on that page that match your Windows version and your PC’s architecture (x64 or Arm64) rather than picking one file.
If steps 1 through 5 don’t resolve the error, disabling third-party antivirus is not a recommended routine step. Nothing in the reports so far ties these failures to security software, and turning it off exposes the system without clear evidence it will help.
If you still want to test for a security-software conflict, check your vendor’s documentation first and disconnect from untrusted or public networks beforehand. Disable protection only briefly, retry the update once, and re-enable it immediately afterward whether or not the install succeeds.
The Reaction
Reports go beyond Neowin’s coverage. A user thread on Microsoft Q&A describes KB5132061 (build 26300.9974) failing with 0x800f0993, and other users report 0x800f0989. All of it is user-reported so far; Microsoft hasn’t confirmed a cause or acknowledged the failures as a known issue.
Our Take
Verdict: Try the repairs once, then pause. Moderate concern, not panic.
If KB5132061 has already failed on your PC, the repair steps above are standard troubleshooting measures generally considered safe to run.
They target common causes behind these codes, though no source confirms they’ll resolve this specific issue or guarantee against a partial update in every system state.
If the install fails a second time after those repairs, stop there. Letting Windows Update retry on its own is normal behavior, but re-running the same repairs or manual installs against an unchanged failure rarely helps while Microsoft hasn’t acknowledged the problem.
KB5132061 is this month’s security update, so the decision comes down to exposure. Pausing updates for a week is a reasonable trade-off for most home PCs, but it does delay those security fixes, and Microsoft may not post a status in that time. For a PC that’s exposed to risky networks or handles sensitive data, keep working through the repairs or the manual install instead of waiting.
If the update hasn’t been offered to you yet, there’s no reason to pause in advance. The report doesn’t show a broad failure rate, and pausing also delays security patches.
Small-business IT helpers should take one extra precaution. Back up affected machines to an external SSD before trying a manual Microsoft Update Catalog install.
Wrapping Up
Run SFC and DISM if you haven’t already. They’re general Windows Update repair steps Microsoft documents, though no source confirms they fix this one. Use Pause updates only if the install keeps failing after the repairs, and resume once the release health dashboard lists a fix.
Repeated update failures alongside other symptoms can point to a deeper problem, though the symptoms don’t share one cause. Persistent disk errors in Event Viewer or a slow, clicking drive warrant an immediate backup and hardware diagnostics regardless of this update. Security software that won’t stay disabled is a separate issue worth raising with your antivirus vendor, not evidence of a bad patch. Neither sign confirms malware, and neither rules out an unrelated update problem.