January 2022 updates causing reboot loops. KB5009624

Jamshid Javidi 1 Reputation point
2022-01-17T19:52:16.823+00:00

Hello Support,

i have several servers 2012, 2016 and 2019) that have downloaded latest January 2022 rollup updates and need to be restarted. one of them went to continuous reboot afterward. So I am afraid of rebooting the others. I know Microsoft has acknowledged the problem but not sure what is the solution? If I restart the server it may go to continuous boot.
Also what needs to be done for the servers that have installed the latest updates and have not problem?
I appreciate your help.
Jamshid

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,348 questions
0 comments No comments
{count} votes

16 answers

Sort by: Most helpful
  1. Limitless Technology 39,296 Reputation points
    2022-01-18T14:22:48.213+00:00

    Hello @Jamshid Javidi

    In this case, I can recommend to log into the server using Safe Mode and remove the latest updates from the Update History.

    Something that can mitigate this in the future, would be to manually install this updates as Administrator.

    If you are still experiencing issues, it would be recommended to share which is the OS system affected as well what are the latest updates and any information related to the boot/reboot in System Event Log.

    Hope this helps with your query,

    ------
    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  2. Jamshid Javidi 1 Reputation point
    2022-01-18T17:37:18.17+00:00

    thank you for assisting me. I have many servers that have downloaded this update and require a reboot. i cannot physically go there and boot them to safe mode. looking for a solution.
    I appreciate your help.
    Thanks,
    Jamshid

    0 comments No comments

  3. Azevedo, Pedro 1 Reputation point
    2022-01-19T16:38:30.49+00:00

    After some checking, all my DC's affected were virtual: I just disconected the network adapter and loguing locally trough VMware (or Hyper-V seems the same?) there is time to remove the update with CMD or even GUID tools. Just go to Windows Update and remove the last one! Worked for me.

    0 comments No comments

  4. Jamshid Javidi 1 Reputation point
    2022-01-19T16:45:26.347+00:00

    Hello all,
    i appreciate your help. I was able to solve this by applying Microsoft out of Band updates 1/17/2022. If the server is not in a restart state the optional updated should be selected. If it is in the restart state then I downloaded the KB501xxxx from the Microsoft Catalog and restarted it. All worked.
    Thanks for your help.
    Jamshid

    0 comments No comments

  5. Helmer Nielsen 1 Reputation point
    2022-01-19T16:49:35.143+00:00

    It seems the problem is connected to NLA.
    Virtual DC jumps to Private Network and need to be set back to Domain Network.
    Try restart Network Location Awareness and set it to delayed start.
    You might need to do one single reboot in order to clear the problem.

    0 comments No comments