Skip to main content

Windows Server 2022 update KB5022842 issue


marco_s
Forum|alt.badge.img+8

Not Veeam related..but be careful guys! :)

https://kb.vmware.com/s/article/90947

15 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8528 comments
  • February 17, 2023

Yes, this seemed to be a nasty one for sure.  Hope no one here is affected.


Link State
Forum|alt.badge.img+11
  • Veeam Legend
  • 614 comments
  • February 17, 2023

thx m8 for share.

 


Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1395 comments
  • February 17, 2023
Chris.Childerhose wrote:

Yes, this seemed to be a nasty one for sure.  Hope no one here is affected.

Yes, it is. This is one reason why one shouldn't directly apply patches on production servers without first testing them... 


Nico Losschaert
Forum|alt.badge.img+12
  • On the path to Greatness
  • 681 comments
  • February 18, 2023

Thx for sharing, experienced it myself...


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • 1354 comments
  • February 21, 2023

VMware has released 7.0 U3k which should solve this issue: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3k-release-notes.html

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8528 comments
  • February 21, 2023
regnor wrote:

VMware has released 7.0 U3k which should solve this issue: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3k-release-notes.html

 

Wow that was a quick fix.  Nice to see this out there now.  Time to test. 😎


vAdmin
Forum|alt.badge.img+2
  • Influencer
  • 169 comments
  • February 22, 2023

Yes, I have experienced this myself too, looks like the Windows Server update has made it more secure by failing to boot up :-)

 

My workaround was to change the boot mode into disabled like this:

 


Forum|alt.badge.img
  • Comes here often
  • 29 comments
  • February 22, 2023

VMware released a patch yesterday to fix this issue:

 

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3k-release-notes.html

 

Edit: sorry - already posted by @regnor 


Scott
Forum|alt.badge.img+9
  • Veeam Legend
  • 1009 comments
  • February 22, 2023

Quick fix. always need to run test systems in the cycle to not get caught by these. 


jc.grellet
Forum|alt.badge.img
  • New Here
  • 5 comments
  • February 22, 2023
problem, and correction in record time. Thank you for sharing

coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4162 comments
  • February 23, 2023

Nice of MS to tell partners they were changing their digital signature. 🙄 Glad to at least see VMW get this taken care of quickly. Thanks for sharing!

Cheers!


Scott
Forum|alt.badge.img+9
  • Veeam Legend
  • 1009 comments
  • March 1, 2023

My second environment caught me off guard installing a new server and it grabbed updates from MS, (lucky it wasn’t PROD)

 

I disabled secureboot andit didn’t resolve the issue either!. So much for a work around. After updating the hosts things are running good.

 

7.0.3k is working fine at least. This issue IS going to affect a ton of people in the next few weeks depending on their WSUS patching schedule. I know many approve at the end of the month and reboots will be starting right away.

 

This is serious for a large environment because it can take some time to update many hosts/clusters, and depending on change management, i suggest bringing this up ASAP. 

 

https://support.microsoft.com/en-au/topic/february-14-2023-kb5022842-os-build-20348-1547-be155955-29f7-47c4-855c-34bd43895940

 

 

After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up.

 “Some versions” “Might”? Way to downplay it MS lol 😂  How about every version prior to 7.0.3k and wont.


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4162 comments
  • March 1, 2023

We don’t implement newest Windows version straight away thankfully. We do have a few of 2022, but ironically I didn’t see this issue surface. However, I did update my ESXi Hosts regardless. MS is good at downplaying the serverity of the issues they tend to cause. Latest reference before this? Printing Nightmare 🙄


Scott
Forum|alt.badge.img+9
  • Veeam Legend
  • 1009 comments
  • March 1, 2023

We didn’t see the issue YET. Our approval for WSUS lags slightly for some environments for this reason. However, while installing a system a coworker updated direct from MS and received the patch. 

If any does the ol “APPROVE ALL” method, they will get hit soon :)

 

 


coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4162 comments
  • March 1, 2023

We use WSUS, and I do the approvals there as well, but I just did the ole ‘check for udpates online’ bit before WSUS approval to install updates on several machines initially, a couple of which were 2022. Glad I wasn’t affected straight off!