/ScanHealth found no component-store corruption, so first install the October cumulative update only—KB5126655 supersedes September KB5122882—after verifying its prerequisite update and obtaining the complete failure code.
1. Verify the actual build and update prerequisite
OsBuildNumber shows only 20348; retrieve the Update Build Revision (UBR) separately:
$cv = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
"{0}.{1}" -f $cv.CurrentBuildNumber, $cv.UBR
Get-HotFix |
Where-Object HotFixID -in 'KB5062572','KB5122882','KB5126654','KB5126655' |
Sort-Object InstalledOn
KB5126655 is the October 2026 cumulative update, includes the fixes from KB5122882, and requires:
- An update released on or after July 8, 2025, such as KB5062572.
- The latest servicing stack update (SSU); this release includes KB5126654, servicing-stack version 20348.5739. ^1^
On an internet-connected administrative workstation, download the applicable x64 packages from the Microsoft Update Catalog, transfer them to the server, and install in this order:
- The July 8, 2025-or-later prerequisite if it is absent.
- Reboot.
- KB5126655.
- Reboot and confirm the build is
20348.5761.
Do not repeatedly reinstall KB5122882 separately; it is the September update at build 20348.5622 ^2^ and is included in KB5126655.
2. Capture the complete failure status
The event output truncates each status after 0x, so it cannot establish whether this is a missing prerequisite, pending transaction, missing source, or CBS corruption. Export the complete messages:
Get-WinEvent -FilterHashtable @{
LogName='Setup'
StartTime=(Get-Date).AddDays(-7)
} | Where-Object Message -match 'KB5122882|KB5126654|KB5126655' |
Select-Object TimeCreated, Id, LevelDisplayName, Message |
Format-List | Out-File C:\Temp\Update-Setup.txt -Width 4096
Select-String -Path C:\Windows\Logs\CBS\CBS.log `
-Pattern 'error|failed|0x800f|KB5126655|KB5122882' |
Out-File C:\Temp\CBS-errors.txt -Width 4096
CBS logs are the supported source for identifying servicing errors and missing packages. For example, 0x800F0831 specifically means a required earlier package manifest is missing; that diagnosis should only be used if the full status or CBS entries show it. ^3^
3. Offline DISM repair, only if CBS identifies corruption or missing files
Because /ScanHealth completed with No component store corruption detected, /RestoreHealth is not currently indicated as the primary fix. If CBS does identify corruption, use matching Windows Server 2022 Standard x64 media with the same installed language. The repair source must contain the files required by the target; Microsoft notes that an older, unpatched source can fail against a more highly patched server. ^4^
Assuming the ISO is drive D:, identify the Standard edition index:
DISM /Get-ImageInfo /ImageFile:D:\sources\install.wim
The output lists each image’s index, edition, architecture, and language details. ^5^
Then substitute the correct Standard index:
mkdir C:\Mount
DISM /Mount-Image /ImageFile:D:\sources\install.wim /Index:<index> /MountDir:C:\Mount /ReadOnly
DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Mount\Windows /LimitAccess
sfc /scannow
DISM /Unmount-Image /MountDir:C:\Mount /Discard
/LimitAccess prevents DISM from trying Windows Update. Microsoft supports a mounted Windows image, matching running installation, or installation-media source for offline repair. ^6^
If the ISO contains install.esd rather than install.wim, do not substitute it blindly; first obtain compatible WIM-based media or prepare an appropriate repair source.
4. Preservation and fallback
DISM repair changes servicing components; it does not perform a clean installation and should preserve installed applications, roles, settings, data, and activation. Nevertheless, take a tested full-system backup or VM snapshot before servicing.
If the prerequisite is present, CBS identifies no repairable files, and KB5126655 still rolls back, use an in-place upgrade/repair only after validating application and role compatibility. Start setup.exe from within the running server—not by booting from the ISO—and select Keep files, settings, and apps. Microsoft requires a full tested backup, maintenance window, compatible roles/applications, and a valid activation method. ^7^
An upgrade to a newer Windows Server version can require a separate license; it should not be treated as a licensing-neutral repair without confirming the target version and licensing channel.
References
- October 13, 2026—KB5126655 (OS Build 20348.5761) - support.microsoft.com
- September 8, 2026—KB5122882 (OS Build 20348.5622)
- Error 0x800F0831 when you install an update
- Configure a Windows Repair Source
- Take Inventory of an Image or Component Using DISM
- Repair a Windows Image
- Perform an in-place upgrade of Windows Server