Microsoft Windows Servers effected by January Update
It appears we have noticed another problematic Microsoft update but this time its effecting Windows Server 2012R2, 2019 and 2022 versions. Calls have mainly been about Server 2012R2 and only a few about the new 2019 and 2022 versions. We found removing the updates appears to be the only work around and it does require a server reboot. There is a different KB update for each, so here is the list and a command admin’s might be able to use for a quick uninstall.
PLEASE REVIEW THE UPDATE SECTION BELOW – Update 1-18-2022 11:30AM EST –
kb5009624 = Server 2012 and R2
wusa /uninstall /KB:5009624 /quiet /norestart
kb5009557 = Server 2019
wusa /uninstall /KB:5009557 /quiet /norestart
kb5009555 = Server 2022
wusa /uninstall /KB:5009555 /quiet /norestart
(You might want to consider following up with a reboot command that will reboot the server when it will have the least impact or if the server is effected by the below behavior reboot asap)
Or you can use the GUI interface by following these steps
PLEASE REVIEW THE UPDATE SECTION BELOW – Update 1-18-2022 11:30AM EST –
– Open Control Panel
– Open Programs and Features or choose uninstall a program
– Choose “View installed updates” in the top left corner.
– find the selected update and double-click it and confirm you want to remove it.
So far we have witnessed Windows Server’s having sporadic reboots, Hyper-V not starting and inaccessible file share volumes.
Lately Microsoft has been bundling security and fixes into the single update, removing these cumulative updates may fix this bug, but this action will also remove fixes for other recently patched vulnerabilities that are included in the bundled update. Removing these updates should only be done if absolutely necessary.
Update 1-18-2022 11:30AM EST – Microsoft released KB5010793 and it claims “Updates a known issue that causes unexpected restarts on Windows Server domain controllers” no word yet on the Hyper-V starting issue was included in this update.
