Windows 11 Pro 26H2 fails to boot after KB5132061 (26300.9974) on two attempts — 0x800F0823 during rollback
Has Microsoft identified a servicing or boot issue with KB5132061 on Windows 11 Pro 26H2? The same workstation booted normally after an image restore, then failed again when I retried the update.
System: Gigabyte Z690 UD AX DDR4, BIOS F34a, Intel Core i9-12900K, and a 2 TB WD SATA SSD using GPT and UEFI. I made no hardware or BIOS changes between attempts.
November 10: After Windows Update requested a restart, the PC entered a recovery loop. I restored the Windows partition from a two-week-old EaseUS backup and rebuilt the EFI boot files. Windows booted again.
November 14: I retried KB5132061 from build 26300.9818. Windows Update recorded Event ID 20 with 0x800F0823 (CBS_E_NEW_SERVICING_STACK_REQUIRED). CBS logged “Last resumed session requires servicing stack update” and then loaded servicing stack 26100.9971. DISM subsequently listed that stack as installed. After another retry and restart, Windows again failed to boot.
Offline recovery: The boot screens showed 0xc000000e for \Windows\System32\winload.efi and later 0xc0000098 for \BCD. From USB recovery media, I confirmed that winload.efi existed and the EFI partition’s BCD pointed to the Windows partition. DISM listed rollup 26100.9974.1.23 as Install Pending and 26100.9818.1.42 as Uninstall Pending. /RevertPendingActions reported success, but the next boot still failed. I recovered Windows with a second restore.
Before I retry, is there a supported prerequisite or installation sequence for moving from 26300.9818 to 26300.9974 when servicing stack 26100.9971 already shows as installed? Which CBS log entries or UEFI boot diagnostics would help distinguish an incomplete update rollback from a separate boot configuration issue? I can provide timestamped excerpts from the failed attempt.