Forum Discussion
Windows server 2022 is not updating with latest patch KB5126655
Windows server 2022 is not updating with latest patch KB5126655. However, successfully installed 2026-10 Cumulative update for .Net framework. Last successful Cumulative update for the operating system version 21H2 is 2026-06.
Try to update the latest patch manually, the server is rolling back the patch.
3 Replies
- szymonn841Copper Contributor
There is a bigger issue on Supermicro motherboards when Intel SATA RAID is configured: the system fails to boot after an update. I have verified this on three different boards; X9SCL-F, X11SCW-F, X11SSL-F
the issue occurs after a second restart : A disk read error occurred
- fuzzysteveOccasional Reader
I'm seeing something similar with this. It's a significant issue for us. Don't suppose you've heard anything from microsoft on it?
- WinEndpointOpsBrass Contributor
Four months without a successful cumulative update, and a clean rollback when you install manually, usually points to component store trouble or a failed prerequisite, not to this specific KB. The rollback leaves a trail, so I would start there:
- Get the actual error code. In Event Viewer, look at Windows Logs > Setup and System around the install time, or run Get-WindowsUpdateLog. Codes like 0x800f0922, 0x800f0831 or 0x80073712 each point to a different fix, so the code matters more than the KB number.
- Check the CBS log at C:\Windows\Logs\CBS\CBS.log and search for the last Error lines before the rollback. They name the package or file that failed.
- Repair the component store: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then reboot and retry. If DISM cannot get its source files, point it at a Server 2022 ISO with /Source and /LimitAccess.
- Free space and pending work. Make sure the system drive has several GB free, no pending reboot is stuck (check for a pending.xml in C:\Windows\WinSxS), and the servicing stack update from your June baseline is installed.
- If it still rolls back, install the missing months in order (the latest Servicing Stack Update first, then the latest cumulative update) from the Microsoft Update Catalog, since an in-place repair needs a clean chain.
If you post the error code and the last few CBS.log errors, people here can narrow it down much faster.