VM Workstation 15: The VM will not run if more than 1 processor or 1 core

[Tammer1]

The vm will begin to start and then shut off.

I'm on windows 11 

Hyper-v has been shut down

Log reports the following:

2024-03-27T08:32:22.967-04:00| vcpu-1| I005: Msg_Post: Error
2024-03-27T08:32:22.967-04:00| vcpu-1| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-1)
2024-03-27T08:32:22.967-04:00| vcpu-1| I005+ Exception 0xc0000005 (access violation) has occurred.

 

What can I do to resolve the issue?

[a_p_]

Which VMwre Workstation version do you use?

Sorry, I missed the title. For Windows 11 you need a newer version.

André

[Tammer1]

Are you saying that VMware 15 cannot run with more than 1 core on windows 11?

Even with Hyper-V disabled?

[bluefirestorm]

There is a known problem when Hyper-V is enabled on the host with newer CPUs it results in crash if more than 1 vCPU is allocated. I think it was for 11th gen or newer Intel CPUs (not sure if it includes 10th gen as well) and certain AMD CPUs. This was fixed in version 16.2.x but not backported to version 15.5.x. So chances are Hyper-V is still enabled or components that rely on Hyper-V such as WSL2, Kernel DMA Protection, Defender Application Guard, VBS, etc are still enabled. At the vmware.log look for "Monitor Mode", ULM means Hyper-V is still enabled on the host.

Your options are
(1) completely remove Hyper-V and stick with version 15.5.x or
(2) or stick with Hyper-V enabled upgrade to version 17.5.x

Whichever option, if this is a new machine with 12th gen or newer Intel CPU, you will also face slow VM problems with only the E-cores being used.

See this post on how to remove Hyper-V, VBS
https://communities.vmware.com/t5/VMware-Workstation-Pro/Disabling-Hyper-V-hypervisor-on-Windows-11-Pro-host-to-get/m-p/2989411#M182968

For Kernel DMA protection, it has to be turned off the host UEFI.

[Tammer1]

My issue is not with Hyper-V

It is not enabled on my machine.

 

 

[bluefirestorm]

Screenshot shows "Windows Hypervisor Platform" as enabled.

Look at the thread I referred you to on how to completely remove Hyper-V and components that enable Hyper-V.

Aside from Monitor Mode showing up as ULM, you can also check msinfo32.

Kernel DMA Protection should be "Off"
Virtualization-based security should be "Not enabled"
Windows Defender Application Guard should not be "Enforced" or not appear at all in msinfo32.

[Tammer1]

I resolved the issue with a change to the bios disabling settings for Virtual CPU security.