KB5132061 Won't Install: 0x800f0993, 0x800f0989 and 0x80070306
Microsoft has acknowledged this and is repairing affected PCs from its own side. The repair started rolling out on 11 November 2026 at 10am PT, and Microsoft expects every affected device to be fixed within 24 to 48 hours of that, with no action needed from you. So check Windows Update again before you change anything — on most PCs the update now installs. Microsoft has not published a technical cause, but its known-issue entry points at October's preview update, KB5127936, and lists the error codes 0x80070306, 0x800f0989 and 0x800f0993. If yours still fails after retrying, work down the steps below from least to most disruptive.
Microsoft's note on this is easy to misread. It lives on the KB5132061 support page rather than on the Windows release health dashboard, its symptom sentence names the wrong KB number, and it says it applies to Windows 11 24H2 Enterprise and Education only — while the people reporting it are mostly on 25H2 and 26H2. This page states what Microsoft actually committed to, what it did not, and what is worth trying if waiting has not worked.
Symptoms
- KB5132061 downloads and reaches a percentage, then rolls back and Windows Update shows it as failed
- Windows Update retries the same update over and over without ever completing it
- Update history shows error 0x800f0993, 0x800f0989 or 0x80070306 next to KB5132061
- The PC hangs on a black screen partway through installing and has to be power-cycled
- winver still reports an OS build ending in a number lower than 9974
Why this happens
A servicing fault on Microsoft's side, already being repaired
Microsoft confirmed the installation failure on the KB5132061 page and says the resolution is running automatically on devices that are connected to the internet and using Windows Update. It states that no manual action from end-users is required and that all affected devices should be repaired within 24 to 48 hours starting 11 November 2026 at 10am PT. That is the single most important fact here: for most people the correct action is to retry, not to start editing the system.
Check Windows Update again — Microsoft is repairing affected PCs
The PC installed October's preview update, KB5127936
Microsoft's known-issue entry is worded confusingly: its symptom sentence refers to "the November 2026 Windows security update KB5127936", but KB5127936 is the 28 October 2026 preview update, not KB5132061. Microsoft has published no technical explanation, so the connection it is drawing is not spelled out. It is consistent with at least one report in Microsoft's own Q&A thread, where the October preview had itself failed, installed late on 8 November, and was then followed by the November security update failing. Treat this as the condition Microsoft pointed at, not as a confirmed cause.
Check Windows Update again — Microsoft is repairing affected PCs · Install KB5132061 by hand from the Microsoft Update Catalog
Component store damage on your own PC
Not every failure to install this update is the Microsoft-side fault. A damaged component store produces the same outcome for any cumulative update, and Microsoft documents DISM and System File Checker as the repair for exactly that. One person in Microsoft's Q&A thread reports this clearing the failure for them.
Repair the component store with DISM, then run System File Checker
Windows Sandbox being enabled — reported, not confirmed
Two people traced their failure to the Windows Sandbox optional feature and reported the update installing once they turned it off. Microsoft does not mention Windows Sandbox anywhere on the KB5132061 page, and other people hit the same failure with Sandbox already disabled — so this is a reported association, not an established cause. It is cheap and reversible to test, which is why it is worth listing at all.
Turn off Windows Sandbox, install the update, then turn it back on
Fixes
Check Windows Update again — Microsoft is repairing affected PCs
about 15 minMicrosoft is deploying the fix from its own side, so on most affected PCs the update now installs with nothing else changed. Retrying before that repair reached the PC did not work for several people, so if you last tried on 11 or 12 November, try again now.
Applies to: Windows 11 26H2, 25H2, and 24H2 Enterprise and Education
- Open Settings > Windows Update and select Check for updates.
- If KB5132061 is offered, let it install and restart when prompted.
- Confirm it actually went in: press Windows+R, type winver and press Enter. You want OS build 26300.9974 on Windows 11 26H2, 26200.9974 on 25H2, or 26100.9974 on 24H2.
winver - If it failed again, open Settings > Windows Update > Update history, find the failed KB5132061 entry and note the exact error code. Which code you get decides what is worth trying next.
Confirmed by the vendor.
Source: Microsoft
Turn off Windows Sandbox, install the update, then turn it back on
Check before applyingabout 20 minTwo people traced this failure to the Windows Sandbox optional feature and reported the update installing once it was off. Microsoft has not confirmed any link.
Applies to: Windows 11 editions that include the Windows Sandbox optional feature
Before you do this
This turns off an isolation feature while the update installs, so turn Windows Sandbox back on afterwards. Microsoft has never named Sandbox in connection with this bug. One of the two people who reported this working was on error 0x800f0922, which is not one of the three codes Microsoft lists for this issue, and at least one other person hit the same failure with Sandbox already disabled. Treat it as worth ten minutes, not as the known cause.
- Press Windows+R, type optionalfeatures and press Enter.
optionalfeatures - If the Windows Sandbox checkbox is already clear, stop here — this is not your problem. Otherwise clear it and select OK.
- Restart the PC when prompted.
- Open Settings > Windows Update, select Check for updates, and let KB5132061 install.
- Once it has installed, re-open optionalfeatures, tick Windows Sandbox again, select OK and restart.
Reported to work by 2 users; not confirmed by the vendor. 1 report it did not help.
Source: The Register, Microsoft Q&A
Repair the component store with DISM, then run System File Checker
Check before applyingabout 45 minMicrosoft documents this as the repair when a Windows update will not install, and one person in Microsoft's own Q&A thread reports it clearing this exact failure.
Applies to: Windows 11 26H2, 25H2 and 24H2
Before you do this
DISM pulls replacement files from Windows Update, so leave the PC connected to the internet and on mains power, and do not interrupt it. The two scans together often take 30 minutes or more.
- Select Start, type cmd, right-click Command Prompt and choose Run as administrator.
- Run the component store repair and wait for it to reach 100%. It can sit on one percentage for several minutes; that is normal.
DISM.exe /Online /Cleanup-image /Restorehealth - Restart the PC.
- Open an administrator Command Prompt again and run System File Checker, waiting for 100% completion.
sfc /scannow - Open Settings > Windows Update and try KB5132061 again.
Confirmed by the vendor, though some users report it does not help.
Source: Microsoft, Microsoft Q&A
Install KB5132061 by hand from the Microsoft Update Catalog
Check before applyingabout 30 minMicrosoft's page offers a manual install as the alternative to Windows Update. One person reports the standalone package going in after Windows Update kept failing, though they had also freed disk space first, so the two are hard to separate.
Applies to: Windows 11 26H2, 25H2, and 24H2 Enterprise and Education
Before you do this
Installing a package built for a different Windows version or CPU architecture will either refuse to run or leave servicing in a worse state than it started. Match what winver reports exactly, and do not use this route to skip the prerequisites above.
- Press Windows+R, type winver and press Enter, and note which version you are on — 26H2, 25H2 or 24H2.
winver - Open the Microsoft Update Catalog and search for KB5132061.
https://www.catalog.update.microsoft.com/ - Download the package that matches both your Windows version and your CPU architecture. An x64 PC needs the x64 package; do not take an ARM64 package for an Intel or AMD machine.
- Check the prerequisites Microsoft lists for this update: on 26H2, the 22 September 2026 update (KB5124010) or later; on 24H2 and 25H2, a 10 June 2025 or later update such as KB5060842, plus the minimum servicing stack version.
- Run the downloaded .msu file, then restart when it finishes.
Confirmed by the vendor.
Source: Microsoft, Microsoft Q&A
Known issues
Open, with a server-side repair in flight. Microsoft added "November security update might fail to install on some devices" to the KB5132061 page on 11 November 2026 and says the resolution runs automatically on internet-connected devices using Windows Update, with all affected devices repaired within 24 to 48 hours from 11 November 10am PT. Microsoft has published no technical cause. Anyone still failing after that window is told to contact Microsoft Support.
Affects KB5132061 (10 November 2026), OS builds 26300.9974, 26200.9974, 26100.9974 · Status: open
Microsoft's entry is scoped more narrowly than the reports. The known issue says it applies to "Windows 11, version 24H2, Enterprise and Education editions only", but the Microsoft Q&A thread on this failure is about build 26300.9974 — Windows 11 26H2 — and the community thread tracking it covers 25H2 and 26H2. If you are on 25H2 or 26H2, the Applies-to line is not a reason to rule this out.
Affects Windows 11 25H2 (26200.9974), Windows 11 26H2 (26300.9974) · Status: open
The entry is not on the release health dashboard. As of 13 November 2026 the Windows 11 25H2 release-health page lists only the SQL Server linked server, USB audio and Remote Desktop issues. The installation failure is documented only in the "Known issues in this update" section of the KB5132061 support page, which is why searching the dashboard for it finds nothing.
Affects Windows 11 25H2, Windows 11 24H2, Windows 11 26H2 · Status: open
If none of this worked
Two nearby problems get mistaken for this one. If your error code is 0x80070005 or 0x800f0922, note that neither is among the three codes Microsoft lists for this known issue, even though both are reported by people in the same threads — so the server-side repair Microsoft describes may not be what you are waiting on. And if KB5132061 did install and the trouble started afterwards, this page is about the opposite situation and its steps will not help. Separately, if Windows Update is stalling during the download rather than failing during installation, that is a download problem rather than this one.
Common questions
- Why can't I find this on Microsoft's Windows release health page?
- Because it is not there. Microsoft documented it in the "Known issues in this update" section of the KB5132061 support page instead. As of 13 November 2026 the Windows 11 25H2, 24H2 and 26H2 release-health pages list only the SQL Server linked server, USB audio and Remote Desktop entries.
- Microsoft says it affects 24H2 Enterprise and Education only. Why am I seeing it on 25H2 or 26H2?
- Microsoft's Applies-to line does say that, but it does not match where the reports are coming from. The Microsoft Q&A thread on this failure concerns build 26300.9974, which is Windows 11 26H2, and the community thread tracking it covers both 25H2 and 26H2. Microsoft has not explained the discrepancy, so do not use that line to rule the issue out.
- Does disabling Windows Sandbox actually fix it?
- Sometimes, apparently, but it is not the established cause and it is being repeated far more confidently than the evidence supports. Two people reported the update installing once Sandbox was off. Microsoft has never mentioned Sandbox in connection with this bug, and other people hit the same failure with Sandbox already disabled. If the checkbox is already clear on your PC, this is not your answer.
- Why does Microsoft's note name KB5127936 instead of KB5132061?
- That is what the page says, and KB5127936 is the 28 October 2026 preview update, not the November security update. Microsoft has not clarified it. The most likely reading is that the October preview is the condition that makes a PC susceptible, rather than the update that fails — but Microsoft has not said so, so it is worth checking your update history for KB5127936 rather than assuming either way.
- Can I just skip this update?
- Not safely as a long-term plan — KB5132061 is a security update, and it is also the update that resolves the USB Audio Class 1.0 Code 10 regression left over from September. Waiting a few days for Microsoft's repair to reach you is reasonable. Leaving it uninstalled indefinitely is not.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.
Report a problem with this pageRelated problems
- Windows Update Stuck Downloading or Failing to Install
- USB Audio No Sound or Code 10 After Windows Update KB5124008
- Battlefield 6 and other anti-cheat games crash seconds after launch on Windows 11 KB5124010
- PowerToys Mouse Without Borders: "Pairing could not be loaded or updated" after the 0.102 update
- NVIDIA driver writes to the SSD constantly (NVDisplay.Container.exe, nvlog.nvlgstg)
- No Sound Over HDMI or DisplayPort on an AMD Graphics Card After a Windows 11 Update
Sources
Microsoft · Support page · checked Nov 13, 2026
- The KB5132061 page carries a known issue titled "November security update might fail to install on some devices"
- Affected devices might repeatedly attempt to install the update, or display error code 0x80070306, 0x800f0989, or 0x800f0993
- Microsoft says the resolution runs automatically on devices connected to the internet and using Windows Update, and that no manual action from end-users is required
- Microsoft says all affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT
- The known-issue symptom sentence names KB5127936, the October 28, 2026 preview update, rather than KB5132061
- The known-issue entry is scoped to "Windows 11, version 24H2, Enterprise and Education editions only"
- KB5132061 delivers OS builds 26300.9974 on 26H2, 26200.9974 on 25H2 and 26100.9974 on 24H2, and was released November 10, 2026
- Prerequisites are a September 22, 2026 or later update such as KB5124010 on 26H2, and a June 10, 2025 or later update such as KB5060842 plus a minimum servicing stack version on 24H2 and 25H2
- Microsoft directs users who still have installation problems after 48 hours to Microsoft Support
- The page offers a manual installation route as an alternative to Windows Update
Microsoft · Documentation · checked Nov 13, 2026
- Microsoft documents DISM.exe /Online /Cleanup-image /Restorehealth, run from an administrator Command Prompt, as a repair step when Windows updates will not install
- Microsoft documents sfc /scannow and says to wait until the scan reaches 100% completion
- Microsoft documents the Windows Update troubleshooter at Start > Settings > System > Troubleshoot > Other troubleshooters on Windows 11
Microsoft · Release notes · checked Nov 13, 2026
- As of 13 November 2026 the Windows 11 25H2 release-health page lists three known issues — SQL Server linked server connections, USB audio devices, and Remote Desktop for non-admin users — and carries no entry for a KB5132061 installation failure
- The page was last updated 12 November 2026
The Register · News · checked Nov 13, 2026
- Complaints that KB5132061 would not download or install appeared within hours of its release
- Users reported error 0x800F0993 and error 0x800F0989
- Microsoft initially listed no known issues for KB5132061, then confirmed the installation trouble in an update added on 12 November 2026
- An ElevenForum member posting as Forceflow suggested Windows Sandbox was involved and reported that disabling the feature and rebooting let the patch install
- Other users reported failures regardless of whether Windows Sandbox was enabled
Microsoft Q&A · Forum · checked Nov 13, 2026
- About eleven distinct people report KB5132061 failing to install, in posts dated 11 and 12 November 2026
- Reported error codes include 0x800f0993, 0x80070005 and 0x800f0922, and some installs hang on a black screen with no code shown
- One user reports DISM /Online /Cleanup-Image /RestoreHealth followed by a restart and sfc /scannow cleared the failure
- One user reports the install succeeded after disabling Windows Sandbox, having first tried DISM and SFC without success
- One user reports Windows Sandbox was already disabled on their system, so it was not the cause of their failure
- One user reports the standalone package from the Microsoft Update Catalog installed after Windows Update kept failing
- Repeated restarts and retries alone did not resolve the failure for several users
- One user reports the October preview update KB5127936 had itself failed before installing on 8 November, after which the November security update failed
- The thread concerns build 26300.9974, which is Windows 11 26H2