(Many) Thanks to Maxstar I was able to get the domain controller in this organization updating again. Now we're on to a different server, same organization. Windows Update is broken in an apparently different manner on this server. As mentioned in the title an attempt to install KB5029242 got to about 45% of the progress bar, then hung. I gave it several days before I attempted to gracefully cancel the update, then forcibly terminated the processes.
As this is a production server I will need to wait until after close of business in the Central time zone, UTC -6, (about 6pm, local time) to restart it.
Fixes already tried:
1. Stopping the Windows Update service and:
3. Running multiple Server 2016 install WIMs through DISM, each patched to a different build
4. Running SFCFix without assistance from Sysnative (dies due to unhandled exception)
Oddly enough no corrupted keys nor warnings were found using ComponentsScanner.
Please see attachments of CBS.zip (also includes DISM folder) and ComponentsScanner.txt.
As this is a production server I will need to wait until after close of business in the Central time zone, UTC -6, (about 6pm, local time) to restart it.
Fixes already tried:
1. Stopping the Windows Update service and:
- Re-registering all Windows Update DLLs
- Removal of all catroot2 files/folders
- Removal of %WINDIR%\SoftwareDistribution folder
- Re-starting the Windows Update service after the above
dism /online /cleanup-image /startcomponentcleanup /restorehealth
and sfc /scannow
3. Running multiple Server 2016 install WIMs through DISM, each patched to a different build
4. Running SFCFix without assistance from Sysnative (dies due to unhandled exception)
Oddly enough no corrupted keys nor warnings were found using ComponentsScanner.
Please see attachments of CBS.zip (also includes DISM folder) and ComponentsScanner.txt.