Admins report Hyper-V and domain controller issues after first Patch Tuesday of 2022
- Reference: 1642079827
- News link: https://www.theregister.co.uk/2022/01/13/microsoft_patch_tuesday_titsup/
- Source link:
A Register reader got in touch concerning [2]KB5009624 , which they said "breaks hypervisors running on WS2012R2."
"I'm currently dealing with this right now and it's a hassle," our reader said.
[3]
"After several tries and fails, I deinstalled the KB and tadaa! Everything went back to normal."
[4]
[5]
Our reader is not alone. As well as the broken Hyper-V, popular tech blog Born City [6]noted problems with boot loops on domain controllers, with other versions of Windows Server affected.
Posters in a Reddit thread [7]complained that [8]KB5009546 (for Windows Server 2016) and [9]KB5009557 (for Windows Server 2019) were probably also to blame and recommended a swift uninstall of the patches for those affected.
[10]
The breaking of Hyper-V means that virtual machines can't be started on the server. Constant reboots are not... good. Oh, and some users have also [11]reported that Windows Resilient File System (ReFS) volumes are left inaccessible after the update. It's a veritable three-ring circus of fun from your friends at Microsoft.
[12]Microsoft starts 2022 with big bundle fixes for 96 security bugs in its software
[13]Microsoft closes installer hole abused by Emotet malware, Google splats Chrome bug exploited in the wild
[14]There's something to be said for delayed gratification when Windows 11 is this full of bugs
[15]Let us give thanks that this November, Microsoft has given us just 55 security fixes, two of which are for actively exploited flaws
As for the updates, a common thread appears to be an Active Directory fix, although a TITSUP* hypervisor and boot loop problems are not listed as known issues for any.
Still, if you're running Windows Server 2012 R2, you might not have much longer to worry about Microsoft breaking things. Extended support ends next year (although you can prolong the pain with extended security updates into 2026). Windows Server 2016 went out of mainstream support on 11 January 2022.
Going out with a bang in an all too real sense of the word.
While uninstalling the patches appears to resolve the issues for those affected, the patches also contain important security fixes. Their removal should therefore be a last resort and only if the issues are being experienced.
[16]
The Register asked Microsoft if it was aware of the problems and planned to issue further fixes. We will update this piece should the company respond. ®
*Tired IT Staffers Uninstall Patches
Get our [17]Tech Resources
[1] https://www.theregister.com/2022/01/12/january_patch_tuesday/
[2] https://support.microsoft.com/en-gb/topic/january-11-2022-kb5009624-monthly-rollup-23f4910b-6bdd-475c-bb4d-c0e961aff0bc
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YeBat2Fb2nLjpzikZIdxGAAAAMA&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YeBat2Fb2nLjpzikZIdxGAAAAMA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YeBat2Fb2nLjpzikZIdxGAAAAMA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[6] https://borncity.com/win/2022/01/12/windows-server-januar-2022-sicherheitsupdates-verursachen-boot-schleife/
[7] https://www.reddit.com/r/sysadmin/comments/s21ae1/january_updates_causing_unexpected_reboots_on/
[8] https://support.microsoft.com/en-gb/topic/january-11-2022-kb5009546-os-build-14393-4886-0c2cac57-13b6-42e6-b318-41ca32428f91
[9] https://support.microsoft.com/en-gb/topic/january-11-2022-kb5009557-os-build-17763-2452-c3ee4073-1e7f-488b-86c9-d050672437ae
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YeBat2Fb2nLjpzikZIdxGAAAAMA&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[11] https://www.reddit.com/r/sysadmin/comments/s21ae1/comment/hscrsg7
[12] https://www.theregister.com/2022/01/12/january_patch_tuesday/
[13] https://www.theregister.com/2021/12/15/patch_tesuday/
[14] https://www.theregister.com/2021/11/15/windows_11_insiders_bug_fixes/
[15] https://www.theregister.com/2021/11/09/microsoft_spreads_patch_tuesday_joy/
[16] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YeBat2Fb2nLjpzikZIdxGAAAAMA&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[17] https://whitepapers.theregister.com/
Re: Did MS retired the updates?
No, they retired (*Cough*Fired*Cough*) their entire QA testing department to prevent any "features" from preventing the swift deployment of such awesomely produced code.
*Hands you a pint*
Drink up, we'll be shloshed before this is over...
Woohoo! I'm part of the winners
Oh, bugger.
Whilst not condoning MS's issuance of patches that do these nasty things, I have to wonder why they were installed without extensive testing.
Icon chosen because there's nothing like nuking your running system with untested patches.
reality
Very few have the time and resources to run a test environment that replicates everything in production.
Many don't have any resources for testing unless it's code their company has created or commissioned.
Sure, you don't deploy to every box at once and you start with the most trivial but those aren't going to be DC's and HyperV hosts so you'd not find the issue in a low pain fashion.
We expect for the sums of money that we are paying to MS that they do a reasonable degree of testing.
In this case, it's clear they didn't. The scenarios that seem to result in the patch's breaking fundamental windows components are not rare edge cases.
They are being tested - by anyone who installed the patches.
If only it was that simple - some of the issues aren't really noticeable until there is reasonable demand and load and it's pretty hard to simulate real world user demand in test labs and gets harder continually as everything expects to be online and really working all the time.
Except Microsoft themselves must have a pretty good setup, just to support their internal staff. Do they eat their own dogfood? Testing patches "at home" would at least give some soft of indication. Or do they run everything out of AWS?
Text message today
My replacement thanked me for passing on my philosophy of waiting a week, checking El Reg and various other IT news sources for complaints about WU.
Re: Text message today
Really depends on your risk appetite since MS hotfixes are known to often have problems.
But that sort of thing should be brought out during the change management process if it is anything more than a box ticking exercise.
And presumably everybody has pre-release environments to test these things on? :-)
"if it was aware of the problems"
Not until enough beta testers customers had voiced their dissatisfaction.
At The Basic Level
Today after the snafu, sorry update, Firefox was not playing well, but a second restart cleared my issue. Small beer for me and compared with bigger issues elsewhere it pales into the landscape.
Do new problems count as a feature update?
I got hit by the ReFS one on on Server 2022.
I took one of the drives out and tried to mount it on a freshly updated Windows 10 desktop. It didn't work there either.
(Fortunately) it is a backup copy, I still have the original, on a zfs file system.
Did MS retired the updates?
I can't see them in Windows Update now.