KB5132061 fails to install on a lot of Windows 11 PCs this week, and if you landed here you have probably watched it climb a few percent, stop, and come back with error 0x800f0993 or 0x800f0989. I have spent enough Patch Tuesdays chasing a failed cumulative update to know the reflex: reset everything, reinstall, blame the machine. This time that reflex is wrong. Microsoft confirmed the problem on November 11, 2026 and is pushing an automatic repair, so the smartest first move is also the laziest one. Below is what Microsoft actually said, how I would confirm a device is affected, and the supported steps to try if you cannot wait.
Quick Answer: KB5132061 Install Error 0x800f0993
If KB5132061 stops with install error 0x800f0993 (or 0x800f0989), Microsoft has confirmed the problem and is pushing an automatic repair. Wait for the repair first, repair the component store with DISM while you wait, and if the update still refuses, install the package manually with DISM /Online /Add-Package. Each step is explained below, in the order I would do them.
Why KB5132061 Fails to Install: What Microsoft Confirmed
KB5132061 is the Windows 11 November 2026 update, released on November 10. According to the Microsoft support article for KB5132061, it takes Windows 11 version 26H2 to OS build 26300.9974, version 25H2 to 26200.9974, and version 24H2 (Enterprise and Education editions only) to 26100.9974. It ships combined with servicing stack update KB5132688.
For the first day there was no official word, and The Register reported download and installation failures while Microsoft listed no known issues. That changed on November 11, when Microsoft added a known issue called November security update might fail to install on some devices. In Microsoft’s words, affected devices might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993.
The resolution section is the important part. Microsoft says the fix runs automatically on affected devices that are connected to the internet and use Windows Update in Settings, that no manual action is required, and that all affected devices should be repaired within 24 to 48 hours counted from November 11, 2026, 10 AM Pacific Time. Once a device has received the repair, it downloads and installs the November update by itself. If it still fails after 48 hours, Microsoft points you to its support channels.
Two honest caveats. Microsoft has not published a root cause, so anyone who tells you exactly why KB5132061 fails to install is guessing. And the symptom text on the page currently names KB5127936, which is the October preview update, even though it sits in the KB5132061 article. I read that as a typo, but I am flagging it rather than hiding it.
Step 1: Confirm KB5132061 Fails to Install for the Known Reason
Before changing anything, I check three things: which build the device is on, whether the update is registered as installed, and which error Windows Update logged. Open PowerShell as administrator:
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
Select-Object DisplayVersion, CurrentBuild, UBR
Get-HotFix -Id KB5132061Code language: JavaScript (javascript)If UBR is still below 9974 and Get-HotFix cannot find the update, you have confirmed that KB5132061 fails to install on this device. Next, pull the most recent installation failures from the System log. Event ID 20 from the Windows Update client records a failed installation together with the error code:
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-WindowsUpdateClient'; Id=20} -MaxEvents 5 |
Format-List TimeCreated, MessageCode language: PHP (php)
If the message names KB5132061 and one of the three codes Microsoft listed (0x800f0993, 0x800f0989 or 0x80070306), you are looking at the known issue. In the Microsoft Q&A thread on the install error people also describe several restarts that changed nothing and a Windows Update troubleshooter that would not run. If you see a different code, treat it as a different problem. For example, 0x800f081f is component store corruption, and I covered that one in my Windows Update error 0x800f081f DISM fix.
Step 2: Let the Automatic Repair Do Its Job
This is the step most people skip. When KB5132061 fails to install with one of the confirmed codes, the supported fix is to keep the device online and let Windows Update retry. My checklist for the Windows 11 November 2026 update is short:
- Keep the PC powered on and connected to the internet. A laptop that sleeps in a bag for two days cannot receive the repair.
- Make sure updates are not paused under Settings, Windows Update.
- Use Check for updates in Settings once or twice a day. Microsoft ties the repair to devices that use Windows Update in Settings.
- Count 48 hours from November 11, 10 AM Pacific Time. That puts the end of the rollout window at November 13, 10 AM Pacific.
One thing this incident reminded me of: Microsoft only promises the automatic repair for devices that talk to Windows Update directly. If KB5132061 fails to install on clients that scan against WSUS or Configuration Manager, the article does not say how or when the repair reaches them. In that situation I would hold the November deployment for the rings that have not installed it yet, and watch the KB page, because Microsoft says it will update the documentation once the rollout is complete. If your WSUS scans are failing for their own reasons, see my guide on the SCCM scan failed 0x80244022 WSUS 503 error.
Step 3: Repair the Component Store While You Wait
If KB5132061 fails to install on a machine that must be patched today, the next thing I try is the standard servicing repair from Microsoft’s Windows Update corruption guide. It is safe, it is supported, and in the Q&A thread at least one user reported that the update went through after running DISM and restarting. From an elevated Command Prompt:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannowRestart, then run Check for updates again. To see what the servicing stack logged for the failure, search the CBS log for the error code:
Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern '0x800f0993' |
Select-Object -Last 10Code language: JavaScript (javascript)If the download itself looks stuck or damaged, clear the Windows Update cache. Microsoft documents this quick reset in its additional resources for Windows Update:
net stop wuauserv
rd /s /q %systemroot%\SoftwareDistribution
net start wuauservBe aware that this clears the update history shown in Settings and forces a fresh download. It does not remove installed updates. I want to be clear about expectations here: these repairs fix real corruption, but they are not Microsoft’s stated resolution for this incident, and other people in the same thread saw no change. Try them once, do not loop on them.

The flowchart is the whole plan for the days when KB5132061 fails to install: confirm, wait, repair, and only then install by hand.
Step 4: Install KB5132061 Manually With DISM /Online /Add-Package
The known issue text also says you can install the update by following the linked install instructions, and the same support article documents a manual procedure with packages from the Microsoft Update Catalog. The catch is that the package comes as more than one MSU file: the required checkpoint cumulative update KB5043080 and the target update KB5132061. Order matters, so I prefer the DISM method, which sorts it out for you.
- Open the Microsoft Update Catalog entry for KB5132061 and download every MSU file listed for your architecture (x64 or Arm64).
- Put them in one empty folder, for example
C:\Packages. Microsoft is explicit that no other files should be in that folder. - Run DISM /Online /Add-Package against the KB5132061 file from an elevated Command Prompt. Use the exact file name you downloaded, including the hash at the end.
DISM /Online /Add-Package /PackagePath:C:\Packages\<KB5132061 msu file name>Code language: HTML, XML (xml)DISM scans the folder named in the path and installs the checkpoint update first if the device needs it. Microsoft’s DISM package servicing reference says the same thing: only the target cumulative update and its prerequisite checkpoint updates belong in that folder. If you prefer PowerShell, Add-WindowsPackage -Online -PackagePath with the same file is the documented equivalent. Restart when asked.
A practical warning from the field reports: the Q&A thread includes a user for whom both Windows Update and the standalone installer failed. So if KB5132061 fails to install through the manual route as well and stops with 0x800f0993, do not escalate to a reset or an in-place reinstall. Go back to Step 2 and let the repair arrive.
What About the Windows Sandbox Workaround?
You will see this tip everywhere, so here is my read on it. A forum user found that disabling Windows Sandbox and rebooting let the update install, and Born’s IT and Windows blog documented the command. The Register noted that for other people KB5132061 fails to install regardless of Sandbox, and one user in the Microsoft thread had Sandbox disabled already and still hit the error. Microsoft does not mention Sandbox in the known issue at all.
So I treat it as an unconfirmed, low-risk experiment for a single test PC, not as a fix to roll out. If you want to try it, check the feature state first, disable it, restart, retry the update, and turn it back on afterwards:
Get-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM
Disable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM
# after the update is installed
Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -All -OnlineCode language: PHP (php)The feature name and the enable command come straight from Microsoft’s Windows Sandbox installation page. If the first command shows the feature as Disabled, this workaround has nothing to offer you.
Step 5: Verify That KB5132061 Is Installed
After the restart, run the same two checks from Step 1. A healthy device now lists the hotfix and reports the new build revision:
Get-HotFix -Id KB5132061
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' |
Select-Object DisplayVersion, CurrentBuild, UBRCode language: JavaScript (javascript)
You want UBR 9974 next to build 26300 on 26H2, 26200 on 25H2, or 26100 on 24H2. I also open Settings, Windows Update, Update history once, just to confirm the entry reads successfully installed and that nothing is queued to retry. If the entry still shows a failure and KB5132061 fails to install again, go back to Step 2.
What I Would Not Do When KB5132061 Fails to Install
- Do not reset or reinstall Windows for this. A confirmed service-side issue with an automatic repair does not justify rebuilding a PC.
- Do not skip the Windows 11 November 2026 update. It is a security release, and it also fixes the USB Audio 1.0 error code 10 problem and an error 87 when adding printers published in Active Directory.
- Do not keep retrying every ten minutes. Each failed attempt costs a download and a restart prompt, and it does not bring the repair any sooner.
- Do not strip optional features across the fleet on the strength of one forum post. Test on one device, and put the feature back.
The lesson I take from this one is simple: when KB5132061 fails to install, or any cumulative update fails on many unrelated machines on the same day, read the known issues section of the KB article before touching the machine. It took Microsoft about a day to confirm this one, and the answer turned out to be patience.
Read more: Windows Update Error 0x800f081f? The Proven DISM Fix
Read more: Windows 11 26H2 Is Here: How to Install It Safely
Read more: SCCM Scan Failed 0x80244022? Fix the WSUS 503 Error Fast
FAQ
Why does KB5132061 fail to install with error 0x800f0993?
Microsoft confirmed on November 11, 2026 that the November security update might fail to install on some devices with error 0x800f0993, 0x800f0989 or 0x80070306. It has not published a root cause, but it is rolling out an automatic repair through Windows Update.
How long does the automatic repair take when KB5132061 fails to install?
Microsoft says all affected devices should be repaired within 24 to 48 hours starting from November 11, 2026, 10 AM Pacific Time. The device must be connected to the internet and use Windows Update in Settings.
Is KB5132061 not installing a sign that my Windows 11 PC is corrupted?
Not necessarily. KB5132061 not installing with one of the three listed error codes matches a known issue on Microsoft’s side. Running DISM /RestoreHealth and sfc /scannow is safe, but a reset or reinstall is not needed for this error.
Can I install KB5132061 manually from the Microsoft Update Catalog?
Yes. If KB5132061 fails to install through Windows Update, download all MSU files for your architecture into one empty folder and run DISM /Online /Add-Package against the KB5132061 file. DISM installs the required checkpoint update KB5043080 first if it is missing.
Does disabling Windows Sandbox fix the KB5132061 install error?
Some users report that it helped, others had the failure with Sandbox already disabled, and Microsoft does not list it as a workaround. Treat it as an optional test on one device and re-enable the feature afterwards.
References
Microsoft Support: November 10, 2026, KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974)
Microsoft Update Catalog: KB5132061 packages
Microsoft Learn: Fix Windows Update corruptions and installation failures
Microsoft Learn: Additional resources for Windows Update
Microsoft Learn: DISM operating system package servicing command-line options
Microsoft Learn: Install Windows Sandbox
Microsoft Q&A: 2026-11 Security Update (KB5132061) (26300.9974) – Install error – 0x800f0993
The Register: Microsoft’s Patch Tuesday can’t break stuff if it won’t install
Born’s IT and Windows blog: Windows: November 2026 Patchday-Probleme?






