Forum Discussion
KB5041578 causing Windows Server 2019 to be unresponsive
In testing the August 2024 security update for Windows Server 2019 (KB5041578) we are finding the update causes some Windows Server 2019 servers to become unresponsive. There is also a thread on...
This process worked great for me on one server. However, another server is so unresponsive that I cannot use this process. Can you please adapt this process so that the steps can be done via remote CLI to a server? Thank you.
Heya Karen - This may be something of a catch-22 situation; I found scripting it myself was problematic for just such reasons. If you have a device which is borderline unresponsive locally then any commands passed over WinRM/remote PS will equally never complete. I don't even get eventual timed-out, just a locked-up script which would never move on to the next device in a text file fed to it.
For those ones that are really unresponsive I've found the only fix is patience unfortunately. You may also need to taskkill the PID (which will be different every time the process spawns) numerous times before you can rename or delete the catroot2 folder.
For those ones that are really unresponsive I've found the only fix is patience unfortunately. You may also need to taskkill the PID (which will be different every time the process spawns) numerous times before you can rename or delete the catroot2 folder.
- Thank you, guess I just try and be patient. If I do get this unresponsive server to process the commands you placed here, I will respond with a reply of success.
- Success, thank you.
- Booting the server in safemode and uninstall the KB5041578 did the trick for me. Not all 2019 servers we are running were impacted.
- Microsoft have now released a Known Issue Rollback (KIR) .msi for this KB, specific to Windows 10/Server 2019. I think it's something an odd concept however, as after either installing the ADMX into Group Policy and assigning via GPO, or installing locally on a server and assigning via Local Policy, you still have to reboot.
As you say, booting into Safe Mode and removing the update does exactly the same thing ultimately... And you don't need to install anything first.
https://www.bleepingcomputer.com/news/microsoft/microsoft-august-updates-cause-windows-server-boot-issues-freezes/#:~:text=%22After%20installing%20the%20August%202024,%2C%22%20Microsoft%20confirmed%20on%20Wednesday.
