Workstation 15 fails to load VM on Windows 11

AndyKnipp · ‎02-10-2022

Hi all

Replaced my PC and am trying to get my new Windows 11 to run with Workstation Pro 15.5.7 build-17171714

I get an error on starting any VM, or creating a new one. Same error running as Administrator or myself should have admin anyway)

Am I screwed ? I would hate to bag VMWare and use Hyper-V (currently turned off).

This is in the log:

6384
2022-02-10T16:11:03.710-07:00| vcpu-1| I005: CoreDump: Including thread 17992
2022-02-10T16:11:03.739-07:00| vcpu-1| I005: Backtrace:
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: backtrace[00] frame 0x74526ff2d8 IP 0x000000e7 params 0x7ff75a64b995 0 0x7ff75a631f7f 0x74526ff310 [no module data] ???
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: backtrace[01] frame 0x74526ff2e0 IP 0x00000010 params 0 0x7ff75a631f7f 0x74526ff310 0 [no module data] ???
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: backtrace[02] frame 0x74526ff2e8 IP 0x7ff75a64b995 params 0x7ff75a631f7f 0x74526ff310 0 0x9a8 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff75a600000 0x0001:0x000000000004a995] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x4b995
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: Msg_Post: Error
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-1)
2022-02-10T16:11:03.744-07:00| vcpu-1| I005+ Exception 0xc0000005 (access violation) has occurred.
2022-02-10T16:11:03.744-07:00| vcpu-1| I005: [msg.panic.haveLog] A log file is available in "C:\VMs\New folder\vmware.log".

rickmacd · ‎02-13-2022

Are "me too" comments OK here?

I have a very similar error. I'm moving from an HP host running Win 10 to a new Acer Win 11 machine. Both are Intel CPUs. Both have WorkStation 15.5.7 installed. I have 10 VMs of various versions of Windows. I've only tried a few but they all fail. It complained about nested VMs not support so I had to turn off virtualization in the VM processor settings. I will be upgrading to WS 16 soon. Will that help?

Similar log:

2022-02-13T22:41:32.926-07:00| vcpu-0| I005: AHCI: Tried to enable/disable IO space.
2022-02-13T22:41:32.926-07:00| vcpu-0| I005: AHCI-VMM:HBA reset issued on sata0.
2022-02-13T22:41:32.938-07:00| vcpu-0| I005: DISKUTIL: scsi0:0 : geometry=10443/255/63
2022-02-13T22:41:32.938-07:00| vcpu-0| I005: DISKUTIL: scsi0:0 : capacity=167772160 logical sector size=512
2022-02-13T22:41:33.413-07:00| vcpu-0| I005: BIOS-UUID is 56 4d 85 d1 7a db c5 9e-85 7d 1f 7c f4 29 00 24
2022-02-13T22:41:34.171-07:00| vcpu-0| I005: DDB: "longContentID" = "6372148442e2ac63c2f83b1e03dcab00" (was "077171340bb8e89289da2cb91b801c46")
2022-02-13T22:41:34.176-07:00| vcpu-0| I005: SVGA: FIFO is already mapped
2022-02-13T22:41:34.177-07:00| svga| I005: SVGA enabling SVGA
2022-02-13T22:41:34.178-07:00| svga| I005: SVGA-ScreenMgr: Screen type changed to RegisterMode
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: ExceptionAddress 0x7ff6b9d5b5a4 eflags 0x00010206
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: rwFlags 0 badAddr 0xffffffffffffffff
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: rax 0xffffffffffffffff rbx 0x7ff6b9d9b880 rcx 0x1dd881e2000
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: rdx 0xffffffffffffffff rsi 0x34 rdi 0x10000
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: r8 0x10 r9 0x206 r10 0xffed73b3710
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: r11 0x1ddfc1fa020 r12 0 r13 0xffffd18074bb8000
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: r14 0x1 r15 0x1
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: rip 0x7ff6b9d5b5a4 rsp 0xd520eff460 rbp 0xd520eff5e9
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: LastBranchToRip 0 LastBranchFromRip 0
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: LastExceptionToRip 0 LastExceptionFromRip 0
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: The following data was delivered with the exception:
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: -- 0
2022-02-13T22:41:35.862-07:00| vcpu-0| W003: -- 0xffffffffffffffff
2022-02-13T22:41:35.863-07:00| vcpu-0| I005: CoreDump: Minidump file D:\vms\Windows 10 x64 Pro\vmware-vmx.dmp exists. Rotating ...
2022-02-13T22:41:35.867-07:00| vcpu-0| W003: CoreDump: Writing minidump to D:\vms\Windows 10 x64 Pro\vmware-vmx.dmp
2022-02-13T22:41:35.985-07:00| vcpu-0| I005: CoreDump: including module base 0x0x7ff6b9d50000 size 0x0x015e9000
2022-02-13T22:41:35.985-07:00| vcpu-0| I005: checksum 0x0111aee4 timestamp 0x5facb5f3
2022-02-13T22:41:35.985-07:00| vcpu-0| I005: image file C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe
2022-02-13T22:41:35.985-07:00| vcpu-0| I005: file version 15.5.7.370

... ... ...

2022-02-13T22:41:35.989-07:00| vcpu-0| I005: CoreDump: Including thread 3132
2022-02-13T22:41:36.276-07:00| vcpu-0| I005: Backtrace:
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: Msg_Post: Error
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2022-02-13T22:41:36.280-07:00| vcpu-0| I005+ Exception 0xc0000005 (access violation) has occurred.
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: [msg.panic.haveLog] A log file is available in "D:\vms\Windows 10 x64 Pro\vmware.log".
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: [msg.panic.requestSupport.withoutLog] You can request support.
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2022-02-13T22:41:36.280-07:00| vcpu-0| I005+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2022-02-13T22:41:36.280-07:00| vcpu-0| I005+ You can also run the "vm-support" script in the Workstation folder directly.
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: [msg.panic.response] We will respond on the basis of your support entitlement.
2022-02-13T22:41:36.280-07:00| vcpu-0| I005: ----------------------------------------
2022-02-13T22:41:36.673-07:00| mks| W003: Panic in progress... ungrabbing
2022-02-13T22:41:36.673-07:00| mks| I005: MKS: Release starting (Panic)
2022-02-13T22:41:36.673-07:00| mks| I005: MKS: Release finished (Panic)
2022-02-13T22:42:31.999-07:00| vmx| I005: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2022-02-13T22:44:32.074-07:00| vmx| I005: GuestRpcSendTimedOut: message to toolbox timed out.
2022-02-13T22:44:32.074-07:00| vmx| I005: Vix: [guestCommands.c:1942]: Error VIX_E_TOOLS_NOT_RUNNING in VMAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest
2022-02-13T22:47:07.676-07:00| mks| I005: MKSGrab: Grab attempt while in Panic. Ignored.

AndyKnipp · ‎02-14-2022

Thanks. doing more research this seems like a known issue.

Choices are run VMs with 1 CPU, or buy an upgrade to 16 and turn off Hyperthreading.

rickmacd · ‎02-14-2022

Yes, I'm also now finding many other reports of our problem. I do have Hyper-V and virtualization turned off everywhere that I can find it, and I have only one processor and 1 core, but the problem persists. I haven't yet determined if v15.5.7 will ever work on Win 11 or I must upgrade to v16.1.2. It seems 16.2 is broken for snapshots and other issues. I do plan to upgrade to v16, even before this issue arose.

AndyKnipp · ‎02-14-2022

Bummer. I did a 30 trial for 16. Haven't decided if I will move to Player or just us the internal Hyper-V (this PC is my personal one but the company I work for uses Hyper-V), so I will figure if I keep paying for WS Pro or if I just move the the MS tools. $100 vs rebuilding my Linux VMs (which I tend to do anyway cause I am a geek).

SCL2IBM · ‎04-18-2023

I had exactly the same problem after my Lenovo P15 laptop host updated to Windows 11.

After that I could not start VM Machines that previously worked perfectly OK on Windows 10 before the update.

VMware log included the same error as posted.

I tried all the suggestions about disabling Windows Hyper-V and Virtualization Based Security, but none of this made any difference.

I eventually made changes in the Host BIOS to disable DMA protection (in section: Security - Virtualization) leaving Intel Virtualization and Intel VT-d enabled.

Looks like Win 11 enforces some changes in DMA protection

SCL2IBM · ‎04-18-2023

Try disabling DMA protection in the HOST BIOS. On my Lenovo P15 it is in the section - Security - Virtualization.

I tried all the blog suggestions about disabling Windows Hyper-V and VBS but it didn't change anything.

Worked for me.

I am using Workstation Pro 15.5.7 which is supposed to work with Win 11 and co located with Hyper-V, but I do not use Windows Hyper-V, only VMWare workstation.

@AndyKnipp

All

Workstation 15 fails to load VM on Windows 11