2026-11 Security Update (KB5132061) (26300.9974) - "bricked" my PC, how to disable

Bruce E 0 Reputation points
2026-11-16T19:08:14.2133333+00:00

My PC applied the update (above) yesterday (Windows 11 Home), and this morning booted to a recovery screen saying my PC could not start. I restored to a restore point from Friday, and it's working again. I have paused updates for a week to figure this out, but the hide updates tool won't show this particular update as an option to hide (I guess the tool won't hide security updates? And it also seems deprecated anyway...). It's a security-related update, so I'd prefer not to skip it forever... I've created a new restore point "just in case." Note that I did install the optional October update. What is my best option here?

Windows for home | Windows 11 | Windows update

3 answers

Sort by: Most helpful
  1. Hendrix-V 21,065 Reputation points Microsoft External Staff Moderator
    2026-11-17T00:07:35.33+00:00

    Hi Bruce E,

    Good job getting the PC working again with System Restore and creating a fresh restore point. Before your pause ends, it's worth finding out why the PC failed to start, so a retry has a better chance of working.

    1. Check the failed install. Go to Settings > Windows Update > Update history and note any error code next to KB5132061.
    2. Look at the logs from that restart. Open Event Viewer > Windows Logs > System and filter by the date of the failed boot. Look for Kernel-Boot, disk or BugCheck errors and write down any stop code.
    3. Check for common conflicts. Third-party antivirus, disk encryption, or storage and RAID drivers often cause boot problems after an update. Temporarily uninstall the antivirus before retrying, and update storage drivers from your PC maker's website.
    4. Retry in a controlled way. Once those are done, download KB5132061 from the Microsoft Update Catalog and install it manually, with your restore point ready.

    I hope this gets the update installed safely. Please share what you find and we'll help from there.

    Was this answer helpful?

    1 person found this answer helpful.

  2. AI answer

    2026-11-16T19:10:20.9566667+00:00

    Keep KB5132061 paused, report the post-install boot failure through Feedback Hub, and avoid retrying it until Microsoft documents this boot symptom or a later cumulative update supersedes it.

    1. Keep updates paused temporarily.
      Go to Settings > Windows Update > Pause updates > Pick a date. Windows 11 supports pausing for up to 35 days; this delays updates rather than permanently disabling them.^1^ Windows 11 Home’s supported consumer controls primarily provide temporary pausing. Microsoft states that updates cannot be stopped entirely and will eventually need to be installed.^2^
    2. Report the reproducible failure.
      Press Windows key + F, choose Report a problem, and include:
      • KB5132061, build 26300.9974
      • The exact recovery-screen message
      • PC manufacturer and model
      • Whether Device Encryption/BitLocker is enabled
      • That the October optional preview was installed
      • That System Restore returned the PC to a working state
      Search first for an existing KB5132061 boot report and select Give similar feedback if one exists; otherwise submit a new report with diagnostics. Feedback Hub is the supported path for reporting unexpected Windows behavior, while Get Help or Microsoft Support is intended for immediate assistance.^3^ A closely matching KB5132061/26300.9974 case—repeated boot failure after the update and successful restoration—received the same recommendation: pause updates and report the boot failure through Feedback Hub.^4^
    3. Do not rely on the KB’s automatic repair as confirmation that your boot problem is fixed.
      Microsoft documents an issue in which the November update might fail to complete installation, repeatedly retry, or show errors 0x80070306, 0x800f0989, or 0x800f0993. Its automatic 24–48-hour repair applies to that installation issue; the release notes do not establish that it fixes a PC entering recovery after installation.^5^ Pausing may also prevent the documented automatic Windows Update download/install flow, so check the KB page or Microsoft Support before resuming rather than assuming the repair was received.

    Before any later retry

    • Back up important files.
    • If Device Encryption or BitLocker is enabled, confirm that the recovery key is accessible; WinRE may require it.^6^
    • Optionally run the supported repair reinstall:
      1. Settings > System > Recovery
      2. Under Fix problems using Windows Update, select Reinstall now
      3. Keep the PC connected to power and the internet
      4. Restart when complete
      This reinstalls the current Windows version while preserving apps, files, and settings.^7^ It is a precaution for damaged Windows components, not a documented guarantee that KB5132061 will boot successfully. If the option is absent, skip this step.

    The October preview matters because monthly security updates are cumulative and include non-security content from the preceding optional preview.^8^ Therefore, uninstalling or avoiding only the preview does not necessarily remove that content from KB5132061.

    If a later retry fails again

    In Windows Recovery Environment, select:

    Troubleshoot > Advanced options > Uninstall Updates > Uninstall latest quality update

    That operation is specifically supported when Windows cannot start after a recent update.^6^ If uninstalling fails, use the restore point already created, then contact Microsoft Support through Get Help and provide the Feedback Hub link and exact recovery error.


    References

    1. [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/pause-updates-in-windows#extend-the-update-pause)
    2. [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/windows-update-faq)
    3. Send feedback to Microsoft with the Feedback Hub app
    4. Windows 11 Pro 26H2 fails to boot after KB5132061 (26300.9974) on two attempts — 0x800F0823 during rollback - Microsoft Q&A
    5. November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100 ...
    6. Recovery options in Windows | Microsoft Support
    7. Fix issues by reinstalling the current version of Windows
    8. Update release cycle for Windows clients
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.
  3. Andrew Beebe 0 Reputation points
    2026-11-19T22:38:25.7833333+00:00

    KB5132061 boot failure (0xc0000001) fixed by disabling SVM in BIOS: AMD, 25H2

    System: Windows 11 25H2, AMD processor, AS ROCK B55M, NVIDIA GTX 1070.

    After the November update, the PC failed to boot with 0xc0000001. Safe Mode worked, but networking didn’t: the network adapter showed Code 37 and the Ethernet port disappeared. “Uninstall latest quality update” failed, System Restore failed, and Reset this PC failed.

    Things I found:

    • DISM showed Windows stuck at build 26200.9168, with the November servicing stack (9971) installed. So the November update looks like it failed partway.
    • DISM /RestoreHealth and SFC found no corruption.
    • The boot log (ntbtlog.txt) ended with afd.sys NOT_LOADED, after many repeated bindflt.sys NOT_LOADED lines.
    • DISM /Remove-Package for the RollupFix package failed with 0x800f0905, from both the recovery environment and a newer USB boot.
    • winsock/IP reset, chkdsk, and bcdboot didn’t help.

    What fixed it: in the BIOS, I disabled SVM Mode (AMD virtualization) and at the same time enabled Secure Boot, which had been off. Windows booted normally right away. I changed both settings together, but SVM matches other reports of disabling virtualization (VT-x on Intel), and the bindflt.sys entries point that way too. I’ve paused updates until Microsoft releases a fix.

    Hope this helps someone avoid a reinstall.

    Was this answer helpful?

    0 comments No comments

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.