I’d be more than happy to help you with your query Thank you for your question and reaching out. What I am observing is that the servers that do end up hanging seem to be mostly file servers.įull list of updates we are applying as part of the patching campaign: I am of the mind to raise the topic with technet forums, but I have no idea if anything would change. System and Application log have a huge gap in them until the moment the server is reset.

Only error Status: 0x80070643 is observed in setup log. Once the reset is done some of the patches revert. Services cannot be reached, nor remote management tools, but a little bit of the file system can be accessed. The server just becomes unresponsive and in need of a reset, vmware/ilo console becomes black and unusable. The hung state does not seem to differ whether the server is physical or a vmware virtual machine. We attempted to install only the rest of the updates without it, but still experienced a hung issue on the server being tested. We assumed it was patch KB5022899 as it would fail install on some of the servers where there was no hung issue. The hung state occurs during the install, without even reaching the reboot part. on other 2012 R2 servers patch KB5022899 fails to install after the reboot some 2012 R2 servers enter a hung state during the installation (windows update -> install patches, before arranging the reboot) During patch deployment we experience the following: Unfortunately no pre-prod or test environment. Patch Ferbruary 2023 has left our environment with issues on 2012 R2 server.

Newbie to these forums so forgive me if the location of the question is incorrect and feel free to move this thread to wherever is the correct location.

0x800f0922