KB5132061 Fails to Install: Fix 0x800f0993, 0x800f0989 and 0x80070306
Is KB5132061 fixed? Microsoft says the install failure affects a limited number of PCs that installed the October preview update KB5127936, and that an automatic repair reaches them within 24 to 48 hours of November 11, 2026 at 10 a.m. Pacific Time. After the repair, Windows Update installs the November security update by itself. If you did not install that preview, this issue is probably not yours, and the fixes below still apply. Microsoft’s current support page also lists Windows 11 24H2 Enterprise and Education, so those PCs should not rule themselves out.
Quick answer: How do I fix KB5132061 failing to install?
1. Check if you are affected: The issue hits PCs that installed KB5127936 (the October 28 optional preview). Look in Settings → Windows Update → Update history.
2. Wait for the automatic repair: Make sure your PC is online, restart, then select Check for updates in Settings → Windows Update. Microsoft says the repair arrives on its own and no user action is needed. If your organization manages the PC through WSUS or another deployment system, contact your IT administrator.
3. Still failing after the window? One user-reported workaround is to turn off Windows Sandbox, restart and retry. It is not confirmed by Microsoft, so use it only after the 48-hour window has passed and only if Sandbox is enabled.
4. Last resorts: Run the DISM and SFC repairs, install manually from the Microsoft Update Catalog (including the required checkpoint update), or contact Microsoft Support if you manage the PC.
KB5132061 Install Error Fix Finder
Answer four questions to get the fix path that matches your PC. The result also checks Microsoft’s repair window against your own clock.
What Microsoft confirmed about the KB5132061 install failure
Some of what is circulating online is confirmed and some is user speculation. Keeping the two apart tells you which steps are safe to rely on. Microsoft’s official KB5132061 support page is the primary source for the repair details. The repair-window timing was first communicated to administrators and reported by BleepingComputer.
| Claim | Status | Source |
|---|---|---|
| The November update can fail to install, repeat install attempts or show 0x80070306, 0x800f0989 or 0x800f0993 | Confirmed by Microsoft | Microsoft KB5132061 page and service update reported by BleepingComputer |
| It affects a limited number of devices that installed KB5127936 | Confirmed by Microsoft | Service update reported by BleepingComputer |
| The failure is listed for Windows 11 25H2 and 26H2, and for 24H2 Enterprise and Education | Confirmed by Microsoft | Microsoft KB5132061 page. Microsoft’s KB5127936 article says that preview shipped only for 25H2 and 26H2, and the two pages are not fully reconciled. |
| Repair takes 24 to 48 hours from November 11, 2026 at 10 a.m. PT and installs automatically through Windows Update on internet-connected devices | Confirmed by Microsoft | Microsoft KB5132061 page and service update reported by BleepingComputer |
| Administrators still seeing failures after 48 hours should contact Microsoft Support | Confirmed by Microsoft | Service update reported by BleepingComputer |
| Windows Sandbox is the cause, and turning it off lets the update install | User-reported, not confirmed | A user’s CBS log analysis, reported by Neowin and Pureinfotech |
| Error 0x800f0915 is part of the same problem | Reported by media, not listed by Microsoft | Pureinfotech and Neowin coverage |
Companion video from Pureinfotech covering the automatic repair, the Sandbox workaround, DISM/SFC and manual installation.
KB5132061 error codes: 0x800f0993, 0x800f0989, 0x80070306 and 0x800f0915
Advertisements
| Error code | Listed by Microsoft for this issue? | What to do |
|---|---|---|
| 0x80070306 | Yes | Wait for the automatic repair. If you have Sandbox on and the window has passed, try the Sandbox workaround. |
| 0x800f0989 | Yes | Same path. Reports describe the install freezing midway before the error appears. |
| 0x800f0993 | Yes | Same path. Microsoft has also tied this code to separate update problems earlier in 2026, so do not assume every occurrence has the same cause. |
| 0x800f0915 | No, reported by media | Follow the same steps, but expect less certainty. |
| Repeated retries, no code | Yes, Microsoft lists repeated install attempts | Stop restarting in a loop. Wait for the repair, then check for updates. |
When does Microsoft’s KB5132061 repair arrive in your time zone?
Microsoft’s window is stated in Pacific Time, which matters for readers in the UK, Canada and Australia. The table converts it. The window starts from November 11 at 10 a.m. PT (6 p.m. UTC).
| Time zone | 24 hours after start | 48 hours after start |
|---|---|---|
| US and Canada Pacific | Nov 12, 10:00 a.m. | Nov 13, 10:00 a.m. |
| US and Canada Eastern | Nov 12, 1:00 p.m. | Nov 13, 1:00 p.m. |
| UTC and UK (GMT) | Nov 12, 6:00 p.m. | Nov 13, 6:00 p.m. |
| Sydney and Melbourne (AEDT) | Nov 13, 5:00 a.m. | Nov 14, 5:00 a.m. |
| Perth (AWST) | Nov 13, 2:00 a.m. | Nov 14, 2:00 a.m. |
The banner at the top of this page uses your device’s clock to show whether the window is still open.
How to fix KB5132061 install errors, step by step
Step 1: Wait for Microsoft’s automatic repair
- Make sure your PC is connected to the internet.
- Restart your PC.
- Go to Settings → Windows Update → Check for updates.
- Let the update retry. Microsoft says it downloads and installs by itself after the repair reaches your device.
The automatic repair applies to affected PCs that are connected to the internet and use Windows Update through the Settings app. If your computer is managed by your organization through WSUS or another deployment system, contact your IT administrator rather than assuming the consumer Windows Update repair will apply in the same way.
Step 2: Try the Windows Sandbox workaround (user-reported)
Use this only if Sandbox is on and Microsoft’s 48-hour repair window has passed. It is temporary, and you can turn Sandbox back on after the update installs. On a work or school PC, ask your IT team first.
- Press Win + R, type
optionalfeaturesand press Enter. - Clear the Windows Sandbox checkbox and select OK.
- Restart when prompted, then run Windows Update again.
You can also do it in an administrator PowerShell window:
Restart, install KB5132061, then re-enable Sandbox if you use it. While it is off, do not run untrusted files on the host PC.
Step 3: Repair system files with DISM and SFC
Open Terminal as administrator and run these in order, restarting afterward:
Step 4: Install KB5132061 manually from Microsoft Update Catalog
If Windows Update continues failing, you can try Microsoft’s standalone packages.
- Open the Microsoft Update Catalog.
- Select the package matching your Windows version and processor architecture (x64 or Arm64).
- Check Microsoft’s KB5132061 installation instructions for the required checkpoint cumulative update, KB5043080.
- Install KB5043080 first if it is not already installed, then install KB5132061.
- Restart your PC and check Settings → Windows Update → Update history.
Microsoft specifies the checkpoint package and installation order for standalone installations. If Windows reports that the checkpoint is already installed, proceed with the target update.
Download packages only from Microsoft’s official catalog. Do not use third-party MSU download sites.
Step 5: Contact Microsoft Support
Microsoft told administrators that anyone still seeing the failure after 48 hours should contact Support. That also applies to managed devices, where IT can check whether a policy is blocking the repair.
Does KB5132061 fix the USB Audio Class 1.0 problem?
Yes. Microsoft confirms that KB5132061 resolves an issue affecting certain USB Audio Class 1.0 devices on Windows 11. Symptoms included Device Manager Code 10, missing audio output, unresponsive volume controls and unavailable sound settings.
If you experienced this problem, install KB5132061 or a later applicable security update. Check Microsoft’s Windows 11 resolved-issues page for the official resolution status. Our guide to the Windows 11 8GB RAM improvements covers the same 26H2 release.
The October preview update at the center of this problem is the same package covered in our KB5127936 customizable right-click menu guide.
Microsoft’s official Windows 11 release notes video for November 2026, linked from the KB5132061 support page. It is an overview of the update, not an installation tutorial.
Update log: what changed and when
Advertisements
This page is updated as Microsoft’s status changes. Each entry shows what was confirmed at that time.
- Rechecked against Microsoft’s support pages. Added the required checkpoint update KB5043080 to the manual install steps, noted that 24H2 Enterprise and Education is also listed by Microsoft, confirmed the USB Audio Class 1.0 fix on Microsoft’s resolved-issues page, and changed the finder so it no longer suggests the Sandbox workaround before the repair window ends.
- Microsoft confirmed the install failures to administrators and said affected devices will be repaired automatically within 24 to 48 hours of November 11, 10 a.m. PT. Page published.
- User reports of 0x800f0989, 0x800f0993 and 0x80070306 spread. One user pointed to Windows Sandbox in the CBS log.
Frequently asked questions
Why is KB5132061 failing to install?
Microsoft says the November 2026 Windows 11 security update can fail on a limited number of devices that installed the October 2026 non-security preview update KB5127936. Affected PCs may retry the install repeatedly or show error 0x80070306, 0x800f0989 or 0x800f0993. Microsoft’s current KB5132061 page lists Windows 11 25H2 and 26H2, and also Windows 11 24H2 Enterprise and Education.
Is Microsoft fixing the KB5132061 install error automatically?
Yes. Microsoft says affected devices should be repaired within 24 to 48 hours starting from November 11, 2026 at 10 a.m. Pacific Time. The repair runs on internet-connected devices that use Windows Update through Settings. After the repair, the device downloads and installs the November update automatically, and users do not need to take any action. Devices managed through WSUS or another deployment system should contact their IT administrator.
Do I need to uninstall KB5127936 to fix it?
Microsoft has not told users to uninstall KB5127936. Its guidance says no user action is needed and the repair arrives automatically through Windows Update.
Is disabling Windows Sandbox a safe workaround?
It is a user-reported workaround, not a Microsoft-confirmed fix, and it should wait until Microsoft’s 48-hour repair window has passed. One user traced the failure to Windows Sandbox in the CBS log, turned the feature off, restarted and installed the update. You can turn Sandbox back on afterward. On a work or school PC, ask your IT team first.
My PC never installed the October preview update. Why does KB5132061 still fail?
On Windows 11 25H2 and 26H2, Microsoft ties this specific issue to devices that installed KB5127936, so your failure likely has a different cause, such as corrupted system files, low disk space or a stuck update cache. Windows 11 24H2 Enterprise and Education is also listed by Microsoft, and its pages do not fully reconcile that with the preview history, so those devices should not rule themselves out. Try the troubleshooter, the DISM and SFC repairs, or a manual install.
How long should I wait for the automatic repair?
Microsoft’s stated window is 24 to 48 hours from November 11, 2026 at 10 a.m. Pacific Time. That is 6 p.m. UTC on November 12 to 6 p.m. UTC on November 13. If you still see errors after the window, administrators are told to contact Microsoft Support.
Should I skip KB5132061 until the problem is fixed?
KB5132061 is the November 2026 security update, so avoid leaving it uninstalled for long. Because Microsoft says the repair is automatic, waiting a day or two for it is reasonable for home users.
Does KB5132061 fix the USB Audio Class 1.0 problem?
Yes. Microsoft’s Windows 11 26H2 resolved-issues page lists the USB Audio Class 1.0 issue as resolved by KB5132061, with the resolution dated November 10, 2026. Symptoms included Device Manager Code 10, missing audio output, unresponsive volume controls and unavailable sound settings.
Disclaimer: Ultimate Info Guide is an independent publication and is not affiliated with or endorsed by Microsoft Corporation. Back up important files before changing Windows features or running repair commands.
