Win 10 19045 22H2 kb5018410 BlueScreen (KMODE EXCEPTION NOT HANDLED)

[tzjtzjtzj]

There is an issue that Windows 10 19045 22H2 displays a BlueScreen (KMODE EXCEPTION NOT HANDLED)

when installing in VMWare. 

Only the x86 variant is affected here.

CU 09/2022 Preview (2075)

CU 10/2022 kb5018410 (2130)

Tested with integrated iso.

Previous versions work.

If this Windows version is installed in VMWare with a Windows 8.x profile, it works.

Oh yes, your email address does not work: ws-beta@vmware.com

[BenoitGygax]

This issue could been worked around by convert the virtual system boot disk from "NVMe" type to "SATA" type (the problem seems to be in NVMe driver...) .

Backup and edit manually the .VMX file like this:

Old:
nvme0.present = "TRUE"
nvme0:0.present = "TRUE"
nvme0:0.fileName = "Windows 10 x32 22H2-000001.vmdk"

New:                                                                                 
sata0:0.present = "TRUE"
sata0:0.fileName = "Windows 10 x32 22H2-000001.vmdk"

Note:
"nvme0:0.fileName" and "sata0:0.fileName" value may be different depending of your virtual disk storage file name....)

[surestor]

Hello,

i tested it but the following happens:

Error while opening the virtual machine: VMX file is corrupt.

Best regards Greg

[xwildx]

I had the same issue with Win 10 19045 22H2 x86 (10.0.19045.2251) / on VMWare 16 Pro - 16.2.4 build 20089737

I created a VM Windows 8.x (that use scsi instead of nvme) and it worked

Many thanks,