Bad Update?

[Gongalong]

Hi folks,

 

Just running through some servers and updating, and three of our six 2019 DCs are stuck at boot. These are all VMs on Hyper-V. Two are stuck at a black screen with the spinning white wheel, and the third is stuck at "Applying computer settings".

 

Is there a bad update out there?

[willtech]

The ones in Jan were not good updates. Have not tried this months yet on any servers. Do you know which ones were installing ?

[Gongalong]

Looks like it was two April updates that I reckon are new today:

 

2022-04 Cumulative Update for Windows Server 2019 (1809) for x64-based System (KB5012647)

2022-04 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5012328)

 

It looks like it's actually four of the six DCs that won't boot. Of the two that are working, one is pending the restart (which I won't do!) and the other seems to have installed the updates and rebooted.

 

Not sure what to do, whether I try and restore one from Veeam from last night's backup. These are VMs on two different Hyper-V setups, so it doesn't seem to be something peculiar to one host server.

[dhicks]

Looks like it was two April updates that I reckon are new today

 

Thanks for the warning - I've updated a couple of Server 2019 servers and several Windows 10 VMs / workstations with those updates today with no issues, but I think I'll leave off updating the Domain Controllers and VM hosts for the moment.

[Gongalong]

It only seems to be DCs in my case. I'm sure other servers had the update without issue. This is different to the January boot loop issue as these servers don't even seem to be booting. Whether it's just a local issue here...

[jamesrhart]

My updates went on fine last night (including DC’s), the only issue I had was on our newer cluster whereby the cluster service didn’t start after reboot, I manually started it and everything worked.

[free780]

I'd read the release notes every patch Tuesday/Wednesday.

 

https://support.microsoft.com/en-us/topic/april-12-2022-kb5012647-os-build-17763-2803-9a10c5c9-e65f-4ae1-a9c4-2db9a8eca4fc

 

Release Health will also show issues.

 

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1809-and-windows-server-2019

 

Having a dev domain is a good idea to test updates.

 

Also be aware that some updates require you to monitor event logs and an enforcement update may occur in the future. Reviewing MS SRC is useful.

Edited April 13, 2022 by free780

[Gongalong]

I've involved our thirdline support, as it's beyond my skillset at this point. A mistake I made was rebooting two DCs with the same role at the same time - I've gotten lazy, and I won't do that again.

 

Thirdline have managed to recover one of the root DCs, it did the thing of rolling back Windows Updates so clearly something had gone awry there. Initially it wouldn't launch directory services, but after a couple of reboots it revived. Thirdline are building an extra root DC for the moment just so we have some additional recovery if it recurs.

 

Stressful!