Microsoft's February update caused Windows Server 2022 to fail to start the virtual machine

CTOnews.com, February 17, according to foreign science and technology media NeoWin, Windows Server 2022 devices failed to start the virtual machine after installing the KB5022842 released on the activity day of the February patch Tuesday. Currently, VMWare has confirmed that the problem is caused by Secure Boot.

VMware issued an announcement today, and CTOnews.com translated as follows:

Symptoms:

After the Windows Server 2022 device installs the KB5022842 update (system build 20348.1547), the guest system fails to boot on a Secure Boot-enabled virtual machine on vSphere ESXi 6.7 U2 / U3 or vSphere ESXi 7.0.x.

In VM vmware.log, the following "Image DENIED" message appears:

2023-02-15T05:

34Rom 31.379Z In (05) vcpu-0-SECUREBOOT: Signature: 0 in db, 0 in dbx, 1 unrecognized, 0 unsupported alg.2023-02-15T05:34:31.379Z In (05) vcpu-0-Hash: 0 in db, 0 in dbx.2023-02-15T05:34:31.379Z In (05) vcpu-0-SECUREBOOT: Image DENIED.

Solution:

There is currently no virtual machine solution for this issue on vSphere ESXi 6.7 U2 / U3 and vSphere ESXi 7.0.x. However, this problem does not exist for virtual machines running on vSphere ESXi 8.0.x and later.

Temporary solution:

Upgrade ESXi hosts running related virtual machines to vSphere ESXi 8.0

Disable "Secure Boot" on VM.

Do not install the KB5022842 patch on any Windows 2022 Server virtual machines until the issue is resolved.