Windows Server January updates

[polleblanc1212]

Hi there,

So I'm new in this topic and I'm going give it a try since I've got some serious problems about the last update for Windows Server in January 2022.

There are last updates availabled :
Windows Server 2012 R2 : KB5009624
Windows Server 2019 : KB5009557

These update are fatals for servers that use Hyper-V and other issues, like, rebooting DC in loop, etc. I've got a lot of costumers that are running on Windows Servers 2012 R2 and 2019 and these KB, I don't want these to be installed. But the issue is, the majority of these servers has already installed these updates and then , it's pending to restart to complete the installation of these updates, BUT I DON'T WANT TO RESTART AND THEN BREAK HYPER-V. I've verified these KB fixes from Microsoft, but the only fix that I find is uninstalling these KB after installation and restart the server. In the majority of reviews for this fix are positives, but in my case, I've tried this solution on one that is Windows Server 2012 R2 and it has not been fixed, the vm is still not getting started.

My question is, still I don't want to restart these servers because I'm not sure what it will impacting even if I uninstall it after rebooting and complete the update, can I uninstall these KB manually WHILE it's saying that to complete the update , we must reboot the server ? ( see my attachment )

OR I should wait, and not doing maintenance for a while, the time Microsoft release a hotfix for this ?

This is getting me crazy, I'm not sure of nothing, so be free to share your knowledges and experiences and what you think about this situation.

Thank you

 

[ChatGPT]

I would recommend the best course of action for handling problematic updates on your Windows Servers:

1. Prevent Automatic Reboots: You can temporarily prevent these servers from automatically rebooting after the updates are applied. This prevents immediate issues after the installation. To do this:
   • Open a Command Prompt window as an administrator.
   • Enter the command: shutdown /a. This command can abort the system shutdown that would occur after the updates.
   • You may need to run this periodically to prevent any automated restarts.
   []Manually Remove Problematic Updates:
   • If these specific updates are causing issues and you need to avoid them, you can manually uninstall them.
   • Go to Control Panel > Programs > Programs and Features > Installed Updates.
   • Locate the problematic update (KB numbers you mentioned) and uninstall them from this screen.
   • Reboot the server manually after the uninstallation.
   []Review Pending Changes:
   • If you're facing Hyper-V issues or DC reboots, review any critical services and resources that can be affected.
   • Ensure you have recent backups before proceeding with any manual changes.
   []Monitor for Hotfixes:
   • Keep an eye on Microsoft's website or update channels for any hotfixes or additional guidance concerning these problematic updates.
   • It's always a good idea to wait for a hotfix if known issues are causing widespread problems.
   []Update Windows Registry:
   • To control whether a server will automatically reboot to complete the installation of updates after delaying/postponing it, you may modify the Windows Registry.
   • It involves adding or adjusting keys/values for HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU.
   • You can set options like NoAutoRebootWithLoggedOnUsers to prevent reboots while users are logged in and other related settings. Always proceed cautiously with manual intervention, especially in critical server environments. Ensuring you have backups and understanding the potential risks associated with delaying or uninstalling updates is crucial.