vmware workstation pro 16.2.1 无法启动win 10 虚拟机

[tangdongdong]

Spoiler

2021-12-16T02:40:40.451Z In(05) vcpu-0 backtrace[15] frame 0x4f227ff780 IP 0x7ff6a64c0a1c params 0 0 0x60 0x60 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x000000000001fa1c] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x20a1c
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[16] frame 0x4f227ff820 IP 0x7ff6a64ba1ae params 0x2278c545ad0 0x2278c5459f0 0x2278c5459a0 0x2278c5459a0 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x00000000000191ae] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x1a1ae
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[17] frame 0x4f227ff860 IP 0x7ff6a64c11c8 params 0 0x7ff6a70da130 0 0 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x00000000000201c8] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x211c8
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[18] frame 0x4f227ff890 IP 0x7ff6a64eefed params 0x7ff6a70da130 0 0x2 0x5 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x000000000004dfed] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x4efed
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[19] frame 0x4f227ff8c0 IP 0x7ff6a64b83cc params 0x2278a5de058 0 0x22788cf8ec0 0xf25df62ec76 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x00000000000173cc] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x183cc
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[20] frame 0x4f227ff8f0 IP 0x7ff6a6a2e0d9 params 0 0 0 0 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x000000000058d0d9] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x58e0d9
2021-12-16T02:40:40.452Z In(05) vcpu-0 backtrace[21] frame 0x4f227ff980 IP 0x7ff6a6bbd124 params 0 0 0 0 [D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff6a64a0000 0x0001:0x000000000071c124] <D:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x71d124
2021-12-16T02:40:40.453Z In(05) vcpu-0 backtrace[22] frame 0x4f227ff988 IP 0x7ffcf6fe1350 params 0 0 0 0 [C:\WINDOWS\System32\KERNEL32.DLL base 0x00007ffcf6fd0000 0x0001:0x0000000000010350] BaseThreadInitThunk
2021-12-16T02:40:40.456Z In(05) vcpu-0 backtrace[23] frame 0x4f227ff9b8 IP 0x7ffcf8a5208b params 0 0 0 0 [C:\WINDOWS\SYSTEM32\ntdll.dll base 0x00007ffcf8a00000 0x0001:0x000000000005108b] RtlUserThreadStart
2021-12-16T02:40:40.456Z In(05) vcpu-0 Msg_Post: Error
2021-12-16T02:40:40.456Z In(05) vcpu-0 [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2021-12-16T02:40:40.456Z In(05)+ vcpu-0 Exception 0xc0000005 (access violation) has occurred.
2021-12-16T02:40:40.456Z In(05) vcpu-0 [msg.panic.haveLog] A log file is available in "D:\Users\Administrator\Documents\Virtual Machines\Windows 10-x64\vmware.log".
2021-12-16T02:40:40.456Z In(05) vcpu-0 [msg.panic.requestSupport.withoutLog] You can request support.
2021-12-16T02:40:40.456Z In(05) vcpu-0 [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2021-12-16T02:40:40.456Z In(05)+ vcpu-0 To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2021-12-16T02:40:40.456Z In(05)+ vcpu-0 You can also run the "vm-support" script in the Workstation folder directly.
2021-12-16T02:40:40.456Z In(05) vcpu-0 [msg.panic.response] We will respond on the basis of your support entitlement.
2021-12-16T02:40:40.456Z In(05) vcpu-0 ----------------------------------------
2021-12-16T02:40:40.469Z In(05) mks MKS-VMDB: VMDB requested a screenshot
2021-12-16T02:40:40.470Z In(05) svga MKSScreenShotMgr: Taking a screenshot
2021-12-16T02:40:40.911Z Wa(03) vmx 2 /vm/#_VMX/mks/window/#0/ = (null) [2]
2021-12-16T02:40:40.911Z Wa(03) vmx [Vmdb_Unset] Stale data for path: /vm/#_VMX/mks/window/#0/ (current value unset) [0->2]
2021-12-16T02:40:40.913Z In(05) mks KHBKL: Unable to parse keystring at: ''
2021-12-16T02:40:40.925Z In(05) vmx Vix: [mainDispatch.c:4657]: VMAutomationProcessMessage: Postpone the command. VM not running (opcode 151)
2021-12-16T02:40:40.997Z Wa(03) mks Panic in progress... ungrabbing
2021-12-16T02:40:40.997Z In(05) mks MKS: Release starting (Panic)
2021-12-16T02:40:40.997Z In(05) mks MKS: Release finished (Panic)

[bluefirestorm]

From the vmware.log

In(05) vmx IOPL_Init: Hyper-V detected by CPUID
In(05) vmx Monitor Mode: ULM

It looks like with version 16.2.x, something goes wrong when Hyper-V is enabled/detected.

Turn off Hyper-V, follow this KB
https://kb.vmware.com/s/article/2146361

Make sure that Memory Integrity is also OFF.

Windows Security -> Device Security -> Core Isolation details