Windows 2016 Server Standard updates will not complete and continually undo changes

Craig Saunders 0 Reputation points
2026-08-20T21:18:51.1466667+00:00

I am attempting to update a Windows 2016 Stardard server to the latest KB5120418 and it seem to install 100% and it seem at the very last part in can not complete the update and undo the changes. I'ved updated the SSU and ran the DISM with ISO installation without success.I have also attempted a manual installation of the cummulative update as well as ensuring that App Rediness was started automatically.

Is there anything I may have missed that would cause this issue?

At this point I am not sure what to do at this point.

Any guidance would be greatly appreciated.

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

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-08-20T21:19:07.5433333+00:00

    For Windows Server 2016, the most relevant next checks are the servicing stack state, component store health, and installing the update payload manually.

    1. Verify the servicing stack is current. Error 0x800f0823 indicates the servicing stack is out of date, and Windows Server 2016 can require the latest SSU before newer cumulative updates will install correctly. If the latest SSU is not already present, get the most recent one from the Microsoft Update Catalog and install it first, then retry the cumulative update.
    2. Repair the component store again with the full DISM and SFC sequence, then restart. Run these commands from an elevated Command Prompt: 
         DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH
   DISM /ONLINE /CLEANUP-IMAGE /CHECKHEALTH
   DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH
   Sfc /Scannow
      Then restart the server and try the update again.
    3. Install the update manually from the Microsoft Update Catalog. If Windows Update and the standalone installer both roll back, download the exact package that matches Windows Server 2016 from the Catalog and install it locally. This is a recommended next step when normal installation paths fail.
    4. If the update is partially installed or the component payload is damaged, remove and re-add the package with DISM. This is more invasive than a normal install path. Use caution because removing packages can affect update state. 
         Dism /online /remove-package /packagepath:C:\temp\<CabFileName>.cab
      Restart if prompted, then install it again: 
         Dism /online /add-package /packagepath:C:\temp\<CabFileName>.cab
      Restart again, then retry the update.
    5. If the server repeatedly reports that a restart is required, restart it again two or three times. If the problem continues after multiple restarts, reinstall any recently installed programs or Windows updates that may have failed to complete.
    6. Do not try to fix this by deleting or changing registry keys related to pending restart or update state. That workaround is specifically discouraged because it can cause later servicing problems.
    7. If the rollback continues after the steps above, collect logs and escalate to Microsoft support. The documented guidance for persistent restart/update servicing failures is to contact Microsoft support.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Harry Phan 30,960 Reputation points Independent Advisor
    2026-08-21T00:31:33.3266667+00:00

    Hello,

    When a Windows Server 2016 cumulative update installs to 100% and then rolls back at the final stage, it usually indicates a servicing stack or component store corruption that prevents the update from committing. Since you’ve already updated the SSU, run DISM with a mounted ISO, and attempted manual installation, the next areas to check are the CBS logs and pending update states.

    Navigate to C:\Windows\Logs\CBS\CBS.log immediately after the rollback. Look for entries around the time of failure, especially “Failed to finalize” or “Error 0x800f0922/0x800f0831.” These codes point to missing payloads or servicing corruption. If you see 0x800f0831, it means the update requires a missing manifest or payload from Windows Update. In that case, ensure the server can reach Windows Update or WSUS, and confirm that the update catalog is synchronized.

    Also check C:\Windows\WinSxS\pending.xml. If this file exists, it can block subsequent updates. Rename it to pending.old and reboot, then retry the installation.

    Another common blocker is low space in the system reserved partition. Updates may fail silently if the EFI/System Reserved partition has less than 500 MB free. Use mountvol to assign a drive letter and check free space. If it’s tight, extend the partition.

    Finally, if none of the above resolves it, run:

    DISM /Online /Cleanup-Image /StartComponentCleanup

    followed by:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess

    where D: is your mounted ISO. This ensures the component store is repaired against a clean source.

    If the cumulative update still fails, the last resort is to apply the update via an offline servicing method: mount the server’s VHD or WIM and inject the update using DISM /Image:<path> /Add-Package /PackagePath:<KB>.msu. This bypasses the live OS servicing stack.

    If you can share the exact error code from CBS.log or WindowsUpdate.log, I can narrow it down further. Without that, the most likely causes are pending.xml corruption, missing payloads, or insufficient reserved partition space.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    HP.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.