Windows 11 25H2 severe instability and servicing corruption associated with KB5124008 / build 26200.9444

I’m posting this in case it helps anyone seeing similar behavior, and also as a report for Microsoft. I cannot prove KB5124008 was the root cause, but the timing and the servicing state make it my leading suspicion.


System: Windows 11 Pro 25H2. Stable build after recovery: 26200.9168.


The machine had previously been stable, but around the attempted September 2026 quality/security update KB5124008 (26200.9444) it developed severe instability. Symptoms included repeated hard freezes in normal Windows, freezes even while working in Safe Mode, failed/looping Automatic Repair, and behavior severe enough that we initially suspected failing RAM, SSDs, or other hardware.


At one point Windows could enter Recovery, but Startup Repair could not repair the installation. Because the freezes were occurring in multiple Windows environments, we started testing hardware rather than assuming the OS was at fault.


Hardware checks performed:

• MemTest86 ran for about 9 hours 19 minutes, completing 48/48 tests with zero errors on 64 GB RAM.
• All three Samsung SSDs reported Good health in Samsung Magician.
• Short diagnostic scans on all three SSDs completed 100% green.
• The machine could remain stable for many hours outside Windows, which made a broad RAM/CPU/motherboard failure increasingly unlikely.

Windows repairs performed:


Offline SFC was run from Windows Recovery:


sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows


SFC reported that it found corrupt files and successfully repaired them.


DISM then reported:


“The component store is repairable.”


An offline RestoreHealth attempt initially failed because the available Windows 11 25H2 ISO contained build 26200.8037, which was older than the installed 26200.9168 image and did not contain suitable repair content.


Once Windows was stable enough to run normally, this command succeeded:


DISM /Online /Cleanup-Image /RestoreHealth


Afterward:


DISM /Online /Cleanup-Image /CheckHealth


reported “No component store corruption detected.”


However, SFC then refused to run because Windows reported a system repair pending.


Investigation showed that Windows Update had KB5124008 (26200.9444) pending restart, while the .NET security update KB5126052 had also failed with error 0x8000ffff.


DISM /Online /Get-Packages /Format:Table


showed a very large number of 26200.9444 packages in “Install Pending” state, while corresponding 26200.9168 packages were in “Uninstall Pending” state. This included language, networking, feature-on-demand, printing, media, PowerShell, Wi-Fi, and other Windows components.


Windows Recovery could not uninstall the latest quality update because it reported:


“You have pending update actions and we won’t be able to uninstall the latest quality update of Windows.”


From WinRE Command Prompt, the pending transaction was reverted with:


DISM /Image:\ /Cleanup-Image /RevertPendingActions


DISM reported that the revert completed successfully and would be finalized after reboot.


On reboot Windows displayed:


“Something didn’t go as planned. No need to worry—undoing changes.”


After the rollback completed, Windows returned to 25H2 build 26200.9168.


Final checks:


DISM /Online /Cleanup-Image /CheckHealth


→ No component store corruption detected


sfc /scannow


→ Windows Resource Protection did not find any integrity violations


The machine is now stable again.


What I would suggest to others seeing similar symptoms:

1. Do not assume hardware failure immediately, even if the machine is freezing badly enough to resemble bad RAM or SSD problems.
2. If possible, test RAM independently with MemTest86 and check drive SMART/diagnostics before replacing hardware.
3. Run SFC and DISM, preferably from Recovery if normal Windows is unstable.
4. Check DISM /Online /Get-Packages /Format:Table for large numbers of Install Pending / Uninstall Pending packages.
5. If the system is stuck in a pending-update state and WinRE cannot uninstall the latest quality update, /RevertPendingActions from offline WinRE may be useful. Do not use it casually on a healthy running installation.
6. Avoid interrupting the rollback once Windows begins “undoing changes.”
7. Once repaired, verify with both DISM /CheckHealth and sfc /scannow.
8. Create a restore point and back up important files before allowing further servicing changes.

Again, I cannot prove KB5124008 itself caused every aspect of this failure, but the update was staged, hundreds of related components were pending replacement, the machine became highly unstable during this servicing state, and stability returned after the pending transaction was reverted and Windows corruption repaired.