Keep KB5132061 paused, report the reproducible boot failure through Feedback Hub, and wait for a superseding update or Microsoft mitigation rather than installing the same package again.
Microsoft currently does not list an Automatic Repair or boot-loop problem as a known issue for KB5132061 on Windows 11 26H2. The documented 26H2 issue resolved by KB5132061 concerns USB Audio Class 1.0 devices, not startup failure.^1^ However, other Microsoft Q&A users have reported KB5132061 installation and BSOD/boot-loop failures,^2^ including a closely matching case where repeated installation attempts made Windows 11 26H2 unbootable.^3^
What to do now
- Leave updates paused.
Go to Settings β Windows Update β Pause updates β Pick a date. Windows 11 permits pausing for up to 35 days, with extensions calculated from the current date.^4^
Pausing is temporary and carries a security trade-off, but it is preferable to triggering another known-reproducible boot failure on this PC. - Verify and record the exact affected build.
Runwinverand record the version/build shown before KB5132061. For 26H2, KB5132061 is the November 10, 2026 security update corresponding to OS build 26300.9974.^5^ - Submit a Feedback Hub report while the restored system works.
- Open Feedback Hub β Report a problem.
- Include:
- Windows 11 Pro 26H2 and the
winverbuild. - KB5132061 / build 26300.9974.
- The successful first boot followed by failure on the next restart or cold boot.
- Automatic Repairβs exact message.
- The fact that restoring the same pre-update image reliably restores normal startup.
- Hardware model, BIOS version, storage controller mode, GPU and driver versions.
- Windows 11 Pro 26H2 and the
- Select Save a local copy of diagnostics and attachments and submit any requested diagnostics.^6^
Your five repeatable image restores and completed memory, disk, malware, DISM, and SFC checks already provide stronger evidence than rerunning those generic repairs. There is no value in reinstalling KB5132061 merely to reproduce it a sixth time.
Recover without restoring the entire image
If KB5132061 installs again and Windows enters Automatic Repair:
- Enter Windows Recovery Environment (WinRE).
- Select Troubleshoot β Advanced options β Uninstall Updates.
- Choose Uninstall latest quality update.
- Restart and verify that Windows starts more than once.
Microsoft documents WinRE update removal specifically for systems that cannot start after an update; it does not affect personal files or installed applications.^7^ If BitLocker is enabled, have the recovery key available before entering these recovery options.
If uninstalling the quality update fails, restore the known-good image as you have been doing. Avoid undocumented package-removal commands unless a support engineer identifies the exact package state from the servicing logs.
Preserve useful evidence before another update attempt
While the restored installation is operational, copy these folders/files somewhere outside the Windows partition:
-
C:\Windows\Logs\CBS\ -
C:\Windows\Logs\WindowsUpdate\ -
C:\ProgramData\USOShared\Logs\ - After a failed boot, from WinRE:
Windows\System32\LogFiles\Srt\SrtTrail.txt
CBS.log covers servicing-stack installation, while the USO logs cover download, installation, and reboot orchestration.^8^
For a Microsoft Support case, the documented TSS collection command gathers CBS, Windows Update, servicing, setup, compatibility, and rollback diagnostics:
# Run from an elevated PowerShell window after obtaining TSS
Set-Location C:\Path\To\TSS
.\TSS.ps1 -CollectLog DND_SETUPReport
Use the public TSS prerequisites and collection instructions rather than downloading troubleshooting scripts from unofficial sites.^9^
When to try updating again
Retry only when one of these conditions is met:
- Windows Update offers a later cumulative security update rather than the same KB5132061 package.
- Microsoft updates the 26H2 release-health page with a mitigation applicable to this startup symptom.
- Microsoft Support identifies a device-specific prerequisite or repair from the collected logs.
KB5132061 already includes its servicing-stack component, so the release notes do not identify a separate SSU that should be manually installed first.^10^ Consequently, no supported prerequisite installation sequence is currently documented for this particular boot failure.
References
- Windows 11, version 26H2 known issues and notifications
- Windows 11 26H2 KB5132061 repeatedly fails with 0x800F0922 / EventsInstaller 0x80070057, some systems enter BSOD boot loop - Microsoft Q&A
- Windows 11 Pro 26H2 fails to boot after KB5132061 (26300.9974) on two attempts β 0x800F0823 during rollback - Microsoft Q&A
- [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/pause-updates-in-windows)
- Windows 11 release information
- Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
- Recovery options in Windows | Microsoft Support
- Windows Update log files
- Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
- November 10, 2026βKB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974)