unable to update cumulative updates sept 26 and oct 26

2026-10-26T05:07:26.3366667+00:00

Hello Microsoft Support,

I am experiencing a cumulative update installation failure on Windows Server 2022. DISM is also unable to complete the required servicing operation.

The server boots normally, but the cumulative update cannot be installed. when updated it taking too much time to roll back I would like assistance diagnosing the servicing issue and repairing the component store using Windows Server 2022 installation media, as the server has no internet access .is it possible to repair without losing the licence and other settings of installed apps.

Please help me identify the cause and the appropriate offline repair procedure.

Thank you.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Daphne Huynh (WICLOUD CORPORATION) 2,620 Reputation points Microsoft External Staff Moderator
    2026-10-26T06:40:40.18+00:00

    Welcome to Microsoft Q&A!

    Thank you for reaching out and for providing detailed information about the issue.

    Based on the symptoms described, the issue may be related to corruption in the Windows component store or missing servicing files. Windows updates may fail when corruption is present, and DISM can help repair certain Windows corruption errors.

    Since this server does not have Internet access, you can use a known-good repair source running the same Windows Server operating system version. The following example when a working Windows installation is used as the repair source:

    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\servername\c$\windows /LimitAccess
    

    Replace servername with the computer name of the system being used as the repair source. The repair-source computer must be running the same operating system version.

    If DISM reports that the restore operation completed successfully, run:

    sfc /scannow
    

    Afterward, restart the server if appropriate and retry the cumulative update.

    The above procedure uses DISM to service and repair the local Windows image. However, since DISM is already failing in your environment, the exact cause cannot be determined from the symptoms alone. This is a recommendation to review:

    C:\Windows\Logs\CBS\CBS.log
    

    The CBS log records issues that DISM found or repaired and can help identify missing or corrupted components.

    If DISM continues to fail even after you provide a correct repair source, the issue has reached a point where further investigation is beyond what can reasonably be performed through Microsoft Q&A.

    Because Microsoft Q&A is a public community-based forum. I can provide documented troubleshooting guidance and help explain supported repair approaches, but I do not have access to your server environment and cannot perform the detailed, environment-specific servicing investigation that may be required in this situation. In particular, cases involving persistent component-store corruption can require detailed review of servicing logs and the specific state of the affected server before the appropriate recovery action can be determined.

    For that reason, if the documented DISM repair continues to fail, I would recommend opening a Microsoft Support request rather than continuing with additional repair changes through the forum. A support engineer can work with the diagnostic information from your affected environment.

    I hope this helps clarify the appropriate repair path

    Reference:

    Fix Windows Update corruptions and installation failures - Windows Server | Microsoft Learn

    If you find it useful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

  2. AI answer

    2026-10-26T05:16:54.32+00:00

    /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:

    1. The July 8, 2025-or-later prerequisite if it is absent.
    2. Reboot.
    3. KB5126655.
    4. 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

    1. October 13, 2026—KB5126655 (OS Build 20348.5761) - support.microsoft.com
    2. September 8, 2026—KB5122882 (OS Build 20348.5622)
    3. Error 0x800F0831 when you install an update
    4. Configure a Windows Repair Source
    5. Take Inventory of an Image or Component Using DISM
    6. Repair a Windows Image
    7. Perform an in-place upgrade of Windows Server
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?