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

thx m8 for share.

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

Thx for sharing, experienced it myself...

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. 

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:

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 

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

problem, and correction in record time. Thank you for sharing

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!

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.

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 

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 :)

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!