KB5132061 crashes PC reproducibly πŸ˜’

Hero1318 45 Reputation points
2026-11-18T05:10:33.5033333+00:00

Desktop PC:

i7-9700

16 GB RAM

500 GB NVME SSD (boot drive), 350 GB free

NVidia GTX 1660Ti GPU, connected to 24" monitor, DP>DP

1T HDD, 800GB free (data only)

Win 11 Pro 26H2

All hardware drivers up-to-date

Win 11 Pro 26H2 runs stably with all updates installed except KB5132061. This KB downloads slowly (1T FiOS) and installs slowly. PC does several of rounds of "updates being installed", and several restarts. The desktop loads and Windows Updates History says KB5132061 was successfully installed. PC runs normally.

But... During very next boot, either Restart or cold boot, PC shuts off almost immediately and restarts itself 3 times and then RE opens. It attempts a repair, connects to internet and looks for solutions, but then message says "Your device ran into a problem and couldn't be repaired".

This happens every time KB5132061 gets installed, I have had to reimage the boot drive FIVE times in last 3 days using a Win 11 26H2 image saved on external USB SSD. After the backup gets restored, PC boots, runs normally, updates normally, aside from KB5132061, and reboots (Restart or cold), at least until next time KB5132061 gets installed. Learning the hard way, I've now paused Windows Updates.

Things I did after reimaging, before KB5132061 got installed again, but without finding/solving the problem:

Cleared BIOS

Installed fresh motherboard battery

MemTest86+: 4 passes without errors

PC's built-in pre-boot diagnostics: all tests passed

chkdsk c: /f: no errors reported

DISM.exe /Online /Cleanup-image /Restorehealth: successful

sfc /scannow: successful

Malwarebytes (free version): nothing found

CrystalDiskInfo: SSD health at 90%

Anyone else have this problem after KB5132061 gets installed? How do I fix this, aside from preventing KB5132061 from ever getting installed again?

THX!

Windows for home | Windows 11 | Windows update

2 answers

Sort by: Most helpful
  1. Hero1318 45 Reputation points
    2026-11-20T02:11:02.7566667+00:00

    @KRIS VAN BOGAERT Sorry you're have the same prob with KB5132061. I posted this in the Microsoft Feedback Hub but -so far- no response. There are 2 other threads with what sounds like similar issues with this KB, here and here. So we're not alone in this...

    I also tried using WinRE to remove the update but then I got a 0xc0000001 error which indicates "a required device isn't connected or that a system or boot file is corrupt". Everything is exactly the same when the boot fails after KB5132061 is installed and after re-imaging the boot drive, so I don't know what device isn't being detected and/or what file(s) might be corrupted.

    Since I have Win 11 Pro, as a workaround, I used the group policy editor (gpedit) so that Windows Update no longer automatically downloads and installs new updates. I resumed updates, but now it just alerts me when new ones are available, and I manually choose which ones to download and install, being careful not to choose KB5132061. Hopefully, none of the ones I allow depend on prior installation of KB5132061.

    Sure hope MS is doing something to fix this issue...soon...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. AI answer

    2026-11-18T05:11:45.3533333+00:00

    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

    1. 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.
    2. Verify and record the exact affected build.
      Run winver and record the version/build shown before KB5132061. For 26H2, KB5132061 is the November 10, 2026 security update corresponding to OS build 26300.9974.^5^
    3. Submit a Feedback Hub report while the restored system works.
      • Open Feedback Hub β†’ Report a problem.
      • Include:
        • Windows 11 Pro 26H2 and the winver build.
        • 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.
      • 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:

    1. Enter Windows Recovery Environment (WinRE).
    2. Select Troubleshoot β†’ Advanced options β†’ Uninstall Updates.
    3. Choose Uninstall latest quality update.
    4. 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

    1. Windows 11, version 26H2 known issues and notifications
    2. Windows 11 26H2 KB5132061 repeatedly fails with 0x800F0922 / EventsInstaller 0x80070057, some systems enter BSOD boot loop - Microsoft Q&A
    3. Windows 11 Pro 26H2 fails to boot after KB5132061 (26300.9974) on two attempts β€” 0x800F0823 during rollback - Microsoft Q&A
    4. [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/pause-updates-in-windows)
    5. Windows 11 release information
    6. Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
    7. Recovery options in Windows | Microsoft Support
    8. Windows Update log files
    9. Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
    10. November 10, 2026β€”KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.