|

Windows 11 KB5132061 Fails: 0x800f0993, 0x80070306, 0x800f0989

The November 10, 2026 Windows 11 security update KB5132061 failed to install on some PCs with error 0x800f0993, 0x80070306 or 0x800f0989, or kept retrying without finishing.

Microsoft started an automatic repair on November 11, 2026 and its release notes now mark the problem as resolved as of November 16, 2026.

Updated November 20, 2026. Everything below about the update comes from Microsoft’s KB5132061 page, read on that day.

Quick answer: what to do first

QuestionAnswer
Which errors?0x800f0993, 0x80070306 and 0x800f0989 during installation of the November update
Has Microsoft fixed it?Yes, an automatic repair began November 11, 2026 at 10 AM PT, and the issue is marked resolved as of November 16
Do I need to act?Not if the PC is online and uses Windows Update in Settings, because the repair arrives without user action
Still failing?Check for updates again, run the troubleshooter, or install manually, as described below

What Microsoft says about the failure

Microsoft’s known issue says some devices could not complete the installation and repeatedly tried to install the update or showed one of the three error codes.

The page does not state a root cause.

BleepingComputer reported that Microsoft tied the problem to a limited number of PCs that had installed the October 2026 preview update, and that PCs without that preview update were not affected.

That detail comes from the news report and not from the Microsoft page, so treat it as reported.

Timeline of the repair

Nov 10
Update released
Nov 11
Repair starts, 10 AM PT
24 to 48 hours
Repair reaches devices
Nov 16
Marked resolved
DateEvent
November 10, 2026KB5132061 released for builds 26300.9974, 26200.9974 and 26100.9974
November 11, 2026Automatic repair begins at 10 AM PT
November 16, 2026Change log marks the install issue resolved

Which Windows 11 versions get this update

KB5132061 applies to Windows 11 version 26H2 and 25H2 in all editions, and to 24H2 for Enterprise and Education only.

Microsoft also lists prerequisites, so a PC that skipped earlier updates may need those first.

VersionInstall first
Windows 11 26H2A Windows update released on or after September 22, 2026, such as KB5124010
Windows 11 24H2 and 25H2A Windows update released on or after June 10, 2025, such as KB5060842
All versionsServicing stack update 26100.9971 or later

Microsoft bundles servicing stack update KB5132688 with KB5132061 to improve installation reliability.

Let the automatic repair finish

  1. Connect the PC to the internet and plug it in.
  2. Open Settings, then Windows Update, and select Check for updates.
  3. Let the update download and install, then restart when asked.

Microsoft says a device that receives the repair downloads and installs the November security update automatically through Windows Update.

Our guide to checking for updates in Windows 11 shows each screen.

If it still fails

Microsoft’s own advice is to use Windows help or contact Microsoft Support, and you can also install the update manually using the instructions on the KB page.

Before that, Microsoft’s general update troubleshooting page lists safe steps in this order.

  1. Back up your personal files first.
  2. Run the troubleshooter at Settings, System, Troubleshoot, Other troubleshooters, then Windows Update, then Run.
  3. Make sure the PC is plugged in and connected to Wi-Fi or Ethernet.
  4. Unplug external storage, docks and other devices you do not need.
  5. Turn on Set time automatically and Set time zone automatically under Settings, Time and language, Date and time.
  6. Free up disk space, since Microsoft lists at least 20 GB free for a 64-bit upgrade.
  7. Check for updates again, then restart with Update and restart.

See how to run a troubleshooter in Windows 11 if you cannot find the menu.

Clear the Windows Update cache

Microsoft’s troubleshooting page also describes clearing the update cache by hand.

  1. Press Win and R, type services.msc and press Enter.
  2. Right-click Windows Update and select Stop.
  3. Open C:\Windows\SoftwareDistribution and delete everything inside it.
  4. Return to Services, right-click Windows Update and select Start.

Then check for updates again.

Repair system files

For experienced users, Microsoft lists two commands to run in a Command Prompt opened as administrator.

StepCommand
1DISM.exe /Online /Cleanup-image /Restorehealth
2sfc /scannow
3Restart and retry Windows Update

To confirm the servicing stack version, Microsoft says to run DISM /Online /Get-Packages and look for the ServicingStack line.

Install the update manually

Microsoft says the update is also available through the Microsoft Update Catalog and, for businesses, through WSUS.

Its KB page lists the optional updates area under Settings, Windows Update, Advanced options as another route.

Download only from Microsoft’s own catalog and match the file to your Windows version and build.

Different error codes

An error that is not one of the three above is a different problem with its own fix.

Notes for IT administrators

Microsoft says administrators still seeing installation problems after the repair window should contact Microsoft Support for business.

When you update installation media, Microsoft says to include the boot.stl file, because leaving it out can cause error 0xc0430001.

Microsoft recommends its Update WinPE script for this, or copying the file from the Windows\Boot\EFI folder.

The KB page also lists a separate open issue where SQL Server linked server connections might stay open on server devices, with a mitigation available through Microsoft Support for business.

What the November update changes

AreaChange listed by Microsoft
USB audioFixes USB Audio 1.0 devices failing to start with Code 10
PrintingFixes error 87 when adding an Active Directory printer
Remote DesktopFixes connection failures from a certificate mismatch after the October preview
Secure BootAdds targeting data for new Secure Boot certificates
NTLMTurns on NTLM message signing by default for non-anonymous connections
PowerShellStricter UTF-8 checks, so scripts with invalid UTF-8 may fail signature validation until re-saved as UTF-8 with a BOM and re-signed

Microsoft also notes there will be no December 2026 non-security preview update, with regular servicing resuming in January 2027.

Official sources

Leave a Reply

Your email address will not be published. Required fields are marked *