Skip to main content
  • EN

That was not happening only at VM with the secure boot in the Hyper-V environment. It also impacts VMware.

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. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below.

We may ask customers to put them on hold to install the October patch for Windows Server 2022.

 

Thankfully I don’t run Secure Boot, only have a handful of 2022 servers, and am now on vSphere 8 😊

Thanks for sharing Cary.

@coolsport00 lucky you!😀 You are welcome!

Thankfully I don’t run Secure Boot, only have a handful of 2022 servers, and am now on vSphere 8 😊

Thanks for sharing Cary.

Is this due to compatibility or operational issues @coolsport00? 

Looking at the thread, one person seems to have resolved the issue by removing the RCT related files….I wonder if this has anything to do with the RCT fixes in the October CU

https://learn.microsoft.com/en-us/answers/questions/1390624/virtual-machines-failed-to-start-after-installing

@Iams3le that I don’t run secure boot? I don’t have TPMs in my Host to do so.

That is usually one of the ways to solve problematic updates. I would suggest if this is not a lab environment, fire-up WSUS in order to test and exert control over the update process. I had no choice than to set this up at one time due to similar issues. 

Comment


Terms & Conditions