LeMarchand Posted January 18, 2022 Posted January 18, 2022 I don't use WSUS anymore and simply run the updates when I am ready. For my 2012r2 DC that uses the built in Windows update, would it use the update Catalogue to fetch its updates from, or do I need to manually download / install this? The way I read it was that it would have to be a manual job, but don't currently have access to my 2012 server to confirm.
Koldov Posted January 18, 2022 Posted January 18, 2022 (edited) Interesting... When checking for updates on my 2012R2, KB5009624 still shows so I guess it doesn't disappear automagically and I will have to disappear it manually. However, I did notice KB5010794 has appeared in my 'optional' updates... OPTIONAL! Yeah optional if you want your (DC, Hyper-V or ReFS) server to function correctly... Now is this a full update or a patch to the update...? KB5009624 = 574.5 MB KB5010794 = 81.0 MB Edited January 18, 2022 by Koldov
mullet_man Posted January 18, 2022 Posted January 18, 2022 Just installed on a DC, restarted and all seems fine so far fingers crossed 2016 I should add. Seems OK on a 2nd DC too. Not sure am brave enough for HyperV servers just yet.
tmoon-mint Posted January 18, 2022 Posted January 18, 2022 2016 I should add. Seems OK on a 2nd DC too. Not sure am brave enough for HyperV servers just yet. I think I need to do a risk assessment on whether applying these patches is worth it or if I should just wait until the February cumulative update. I dont like the idea of being unpatched for a month but at the same time we need to be operational!
mullet_man Posted January 18, 2022 Posted January 18, 2022 I think I need to do a risk assessment on whether applying these patches is worth it or if I should just wait until the February cumulative update. I dont like the idea of being unpatched for a month but at the same time we need to be operational! I've tested our DCs which are VMs first so if anything happened I could easily roll them back. Am guessing Microsoft must be confident with the 2016 patches as these seem to be still available but others have been pulled.
tmoon-mint Posted January 18, 2022 Posted January 18, 2022 I've tested our DCs which are VMs first so if anything happened I could easily roll them back. Am guessing Microsoft must be confident with the 2016 patches as these seem to be still available but others have been pulled. Thats strange because the DC I had that was rebooting constantly was Server 2016. I think I will install them this weekend and then be prepared for angry phone calls Monday morning
Koldov Posted January 18, 2022 Posted January 18, 2022 Now is this a full update or a patch to the update...? KB5009624 = 574.5 MB KB5010794 = 81.0 MB Maybe that has answered my own question, given the size difference my guess is that it's a patch to the update... So what's the plan, install the update and hope the server stays up long enough to apply the patch...?
tmoon-mint Posted January 18, 2022 Posted January 18, 2022 Maybe that has answered my own question, given the size difference my guess is that it's a patch to the update... So what's the plan, install the update and hope the server stays up long enough to apply the patch...? I heard stopping the Netlogon service stops the reboots. Havent tested it myself but unplugging it from the network entirely meant it stayed up long enough to remove the patch. 1
Koldov Posted January 18, 2022 Posted January 18, 2022 Thanks. Sounds about right if the DC reboots when "Active Directory attributes are not written correctly during a Lightweight Directory Access Protocol (LDAP) modify operation with multiple specific attribute changes" that might include people logging in I guess... Shame I can't get someone to stand in the server room overnight, unplugging the network and plugging it back in... as I was hoping to get this done remotely 'out of hours'.
mullet_man Posted January 18, 2022 Posted January 18, 2022 Thats strange because the DC I had that was rebooting constantly was Server 2016. I think I will install them this weekend and then be prepared for angry phone calls Monday morning 2 out of 3 DCs I've installed it on so far have been OK. Last DC Software Centre is just stuck at downloading the update. Will keep everyone updated, hopefully the HyperV servers go OK.
TwistedHelixis Posted January 18, 2022 Posted January 18, 2022 (edited) In regards to 2012r2 DC... 2 people on Reddit post have manually applied the new update in different ways. First, simply ticked all updates including the new optional update and clicked update. Apparently the reboot took almost an hour and they were about to power cycle when it completed. Next user, tried to just install the option update, but first attempt it said it wasn't needed, then later it did apply, after reboot they ticked all other updates and installed. Tbh, I might just bounce this month and see if they release a cumulative update with the patch in February. Edited January 18, 2022 by TwistedHelixis
Koldov Posted January 19, 2022 Posted January 19, 2022 But what's the other half of the story... is it fixed?
TwistedHelixis Posted January 19, 2022 Posted January 19, 2022 But what's the other half of the story... is it fixed? Both DCs were up and running when they posted. Although I have read a few posts where the original updates were fine for a few days, only to start boot looping.
5tu Posted January 19, 2022 Posted January 19, 2022 The OOB update for Windows Server 2019 has been released now (just in case anyone needs it) - https://support.microsoft.com/en-us/topic/january-18-2022-kb5010791-os-build-17763-2458-out-of-band-43697313-d8e0-4918-b6df-7f64d4d9a8cd
Steve21 Posted January 19, 2022 Posted January 19, 2022 Does anyone know if KB5009557 has been fixed in the actual update like a re-release? Haven't installed Jan updates yet, and tried it on a test server and once KB5009557 installs there's no OOB update for it showing to install after so wondering if they fixed it for those who haven't installed them yet Steve
computer_expert Posted January 19, 2022 Posted January 19, 2022 Does anyone know if KB5009557 has been fixed in the actual update like a re-release? Haven't installed Jan updates yet, and tried it on a test server and once KB5009557 installs there's no OOB update for it showing to install after so wondering if they fixed it for those who haven't installed them yet Steve The OOB update is under a different KB no. This is the 2019 one. Needs to be manually imported into WSUS, or installed from the catalog. 1
Steve21 Posted January 19, 2022 Posted January 19, 2022 The OOB update is under a different KB no. This is the 2019 one. Needs to be manually imported into WSUS, or installed from the catalog. Ah yeah, ironically it's still updating via Windows Updates with the broken one! Just restarted it and it now lets me see the fix... odd haha Thanks, Steve
Duranis Posted January 20, 2022 Posted January 20, 2022 In regards to 2012r2 DC... 2 people on Reddit post have manually applied the new update in different ways. First, simply ticked all updates including the new optional update and clicked update. Apparently the reboot took almost an hour and they were about to power cycle when it completed. This is more or less what I did. I had the broken update set to install overnight so not sure how long that took to reboot. It had still been crashing when I checked in the morning so installed the optional update. Restart didn't take any longer than normal for this and so far everything is running fine.
Koldov Posted January 20, 2022 Posted January 20, 2022 I think I will tick both updates (KB5009624 in 'Important' and KB5010794 in 'Optional') and hope it sorts itself out over the weekend...
TwistedHelixis Posted January 20, 2022 Posted January 20, 2022 I think I will tick both updates (KB5009624 in 'Important' and KB5010794 in 'Optional') and hope it sorts itself out over the weekend... Fingers crossed. Keep us posted :-)
Koldov Posted January 24, 2022 Posted January 24, 2022 OK, on SERVER 2012R2 ticked both updates (KB5009624 in 'Important' and KB5010794 in 'Optional') and installed them last night, didn't take any longer than usual. So far 'normal service has been resumed'... Both DCs, no reboots all night and Hyper-V host started the Virtual Machines. 2
mullet_man Posted January 25, 2022 Posted January 25, 2022 2 out of 3 DCs I've installed it on so far have been OK. Last DC Software Centre is just stuck at downloading the update. Will keep everyone updated, hopefully the HyperV servers go OK.Third DC updated fine, as have HV servers. Phew. Am guessing Microsoft were confident this wasn't a 2016 issue even though some people's posts on Reddit seem to suggest it was.
Ertech Posted January 31, 2022 Posted January 31, 2022 Has this been resolved for 2012r2/2016? - I am planing to release all Jan updates at once.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now