Forum Discussion

Hazem_atiya's avatar
Hazem_atiya
Copper Contributor
Sep 29, 2026

I have an complicated problem for Windows Update in Windows Server 2016

Starting from Last April , when install Tuesday Patches , it's completed successfully but undo any change after reboot, when check Staged , I have find a lot of packages has stuck on Staged , I have remove all of them and install KB5123239 using Download KB , but the same issue still existing, and trying to install it using CAB file , but the same issue still existing, and trying to reinstall it after uninstall the EDR , but the problem still existing

otherwise , after reboot and check installed updates, I have find this KB it's shown as it's installed 

 

 

List of all Staged Pacakges : I have follow the below technote to remove them https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/error-0x800f0922-installing-windows-updates

and then trying to install it using cab file 

anyway, I'm trying to Exclude Drivers in updates.

After Undo changes (first picture above )after reboot, the control panel was shown this KB !!! this KB is related to patch in 2024 , and I'm already remove all staged packages !!!

BR,

Hazem Mohamed

windows server
windows server 2016 datacenter
Windows Updates

1 Reply

  • Jamony's avatar
    Jamony
    MCT
    Oct 05, 2026

    The update appearing in Control Panel after “undoing changes” does not prove every package committed; the component store and update history can disagree when servicing is damaged. Stop manually deleting staged packages because that can remove dependencies. Record the OS build, run DISM /Online /Get-Packages /Format:Table, and check whether KB5123239 is Installed, Install Pending, or Staged. Review the Setup log, WindowsUpdateClient events, and C:\Windows\Logs\CBS\CBS.log around the failed reboot for the first HRESULT and package name. Run DISM /Online /Cleanup-Image /RestoreHealth, using a matching Server 2016 repair source if Windows Update cannot supply files, followed by sfc /scannow and a reboot. Retry the latest applicable cumulative update, not an older superseded CAB. Excluding drivers matters only if CBS identifies a driver operation as the failure. If DISM cannot repair the store, preserve the logs and escalate or restore a known-good backup instead of forcing more removals