'Virtualized Intel VT-x/EPT is not supported on this platform. Continue without virtualized Intel VT-x/EPT'
If you're not planning to run nested VMs (VMs inside your VMWare VM), just disable the "Virtualize Intel VT-x/EPT or AMD-V/RVI" checkbox in VM Settings→CPU, and the message will go away; if you do plan to run nested VMs, you will have to disable Hyper-V on the host.
If you're not planning to run nested VMs (VMs inside your VMWare VM), just disable the "Virtualize Intel VT-x/EPT or AMD-V/RVI" checkbox in VM Settings→CPU, and the message will go away; if you do plan to run nested VMs, you will have to disable Hyper-V on the host.
Hi ender_,
I received this message too. Is this because I have Hyper V enabled?
Also, I was reading some info online and apparently VMware and Microsoft worked together in order to allow users to use VMware Workstation Player when Hyper-V was enabled.
Surely, I shouldn't be having these issues since I am using both: VMware Workstation 16 Player and am running Windows 10 20H2.
Link to Blog -> https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html
Regards,
Tamoor
Which Windows version do you have? VMWare supports Hyper-V API on Windows 10 2004 and newer only.
I am using Windows 10 Pro
There are currently 11 major versions of Windows 10 Pro (3 of which are supported) - right-click the Start button, select Run from the menu and run winver, that will tell you the exact version you're running.
The part in red is your Windows 10 version - if it's 1909 or older, VMWare won't work if Hyper-V is enabled.
Hi ender_,
This is the current version that my system is running.
OK, this is new enough to support Hyper-V. I missed nested virtualization part of the error in your first image - disable that in the VM settings, and it should work.
But, I am intending to use 3 other VM's within my main VM. So I can't do that.
If you want to do nested virtualization, you will have to disable Hyper-V on the host - follow the link in my first message. Hyper-V API currently doesn't support nested virt, so you can have one or the other.
I see. I'll follow the steps you gave earlier tomorrow morning and let you know how I get on.
Thanks for the help so far ender_
Just want to add that for me running this command:
bcdedit /set hypervisorlaunchtype off
resolved the nested virtualization issue for me (required a reboot to take affect though). Of course I can no longer use WSL2/Docker/etc.. on the host machine until I revert the setting back to 'auto'.
Hi ender_,
Sorry for no updates. I followed the instructions you sent and my VM seems to be working okay. If anything goes wrong I'll be sure to post something on the community page.
Thank you once again.
Take care and Happy New Year!
Please check my tutorial to resolve this issue which i have in this page
Hi @hunk1989, I tried with all possible options. Nothing worked.
You may try the solution https://github.com/paolo-projects/auto-unlocker/issues/31
It's worked for me in Windows 10 Home edition
Many thanks, this worked for me!
This might be due to a Windows virtual machine configuration that you mistakenly set or a software you installed changes it. Don’t waste your time into install a new virtual machine or reconfigure your VMWare machine because the last time you still started it successfully and it may cause the problem go further and other problems may arise.
Last time, we face this issue after installing the Docker Desktop software which is also a virtualization software
Try solution below:
https://mayviti.com/vmware-virtualized-intel-vt-xept-is-not-supported-pc-fixed/
Hello
I didnt have this issue before uninstalling Vmware workstation pro and reinstall it again.
Now, I disabled Hyper-V on Windows 10 and still have the same issue.
Any solution for that ?
Kind regards
This command followed by a reboot of the workstation worked for me.