Server 2019 Domain Controllers broken by updates

Topic

New Reply

I experienced a client’s DC servers being broken by their NICs being changed to DHCP by a Windows Update.  Best guesstimate is that it was KB5055519, as the Server 2019 counterpart to KB5055523 which has reportedly borked DC NIC settings.

The servers received the OOB SSU KB5055662, KB5054695 and KB5055519.  All 3 said a reboot was needed to change them to the installed state, and after reboot the setup event log showed event ID 3 for all 3 saying “Package <kb> failed to be changed to the Installed state. Status: 0x800f0923.”

That reboot ended up putting the DCs in safe mode with the NIC set to DHCP so no domain-related services would work, including DNS server.

Anyone else have this problem?

Reply | Quote

Replies

I have 2019 Domain controllers here and have not seen it personally.  I will ask around if anyone else has seen this.

KB5055662  — that’s a SSU for Server 2012 R2  can you confirm what was installed?

https://support.microsoft.com/en-us/topic/kb5055665-servicing-stack-update-for-windows-server-2012-r2-april-8-2025-503528d7-d670-4b47-a162-b51ff463d788

Google hit the wrong KB.  You are referring to the fix for auditing.  I have not installed that and I would not have installed both updates at the same time.  Pick one or the other.  https://support.microsoft.com/en-us/topic/april-11-2025-kb5058922-os-build-17763-7240-out-of-band-84e282b6-22b9-45db-80c0-d485b8c254bc takes the place of the April 8th update.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

https://support.microsoft.com/en-us/topic/april-11-2025-kb5058922-os-build-17763-7240-out-of-band-84e282b6-22b9-45db-80c0-d485b8c254bc

by any chance was is that update?  The SSU is bundled into that update.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

5055662 is the recent standalone OOB SSU.   Or at least it was.  I am suddenly not finding information about it.  Looks like MS scrubbed it from the update catalog.   I only see it referenced in other KBs now but it was its own OOB SSU.

My patch management system automatically installs standalone SSUs because of MS guidance.  I have the attempt to install 5055662 logged in the Setup event log.

The 5055519 update is a cumulative update that should have its own SSU built in, from the April Patch Tuesday.

5054695 is a .NET cumulative update.  Not worried about that changing NICs on me.  So it was either the OOB SSU or the 5055519 cumulative update.  Probably the cumulative update – they toss everything in there.

 

 

 

 

Reply | Quote

Wow.  This is really weird.  Recent updates shows nothing, but if I go to uninstall updates on the server, it shows (contrary to what the setup event logs said) it installed the 5055662 SSU (10.0.17763.7125) and rather than the CU and .NET updates logged in the event log, it rather installed the January cumulative update for .NET 5049608 and the March 2025 cumulative update for Server 2019 KB5053596.

All 3 installed on April 26, 2025, the date the 3 updates I originally made note of were supposed to have installed when things went screwy with the NIC losing its static IP settings. Bizarro world is here.

It also says Windows Update services are hosed.  The troubleshooter detected an issue but did not say what, and even though it seems to claim it fixed the issue it did not.  The problem persists.

And of course SSUs aren’t removable from that interface.

Reply | Quote