"disable virtualization checkboxes" is the final solution that worked fine in our case.

we did:

1) bcdedit /set hypervisorlaunchtype off

2) uncheck checkboxes

Thanks!

Hi,

This is not solve at all...

You are just disabling  the nested (VT-X), i can't do that because i need it.

It happen after windows update 2004.

VMWare 1 6 Pro still get tehhe same error on Virtualization Counters. Only way to have it work is to disable Virtualization options.

Very bad

Your screenshot just helped me fix both of my Linux distros!! I unchecked all three and I'm in!

You can run vmware and hyper-v together now since 15.5. I had to make sure that "Virtualize Intel VT-x/EPT or AMD-V/RVI" was NOT CHECKED. It's a beautiful thing

Any update on this? As it stands now (February 16, 2021), the following setup is NOT possible

* Host: Intel XEON 

* Host: Windows 10 20H2 

* Host: Windows Subsystem for Linux (a.k.a WSL2) enabled

* VM: Windows 10 20H2

* VM Run something that needs virtualization (like Docker). 

---

The only way to restore the VM's ability to run docker is to completely disable WSL on the host. This is not an acceptable compromise. A developer should not have to choose between WSL and VMware

Can anyone here confirm if Parallels or VirtualBox is capable of nested virtualization when the host has either Hyper-V or WSL enabled?

Highlight the guest, Edit Virtual Machine Settings, Device: Processors, untick Virtualise Intel VT-x/EPT or AMD-V/RVI should also do the trick.

As per my message: I'm not interested in a "simple" VM. I need one that can run a virtualization layer (like Docker) inside of it. In other words, that is not a viable solution for a lot of developers

Last time I could run nested was back around 6.5 which was a long time ago.

You take a noticeable performance hit without Virtualize Intel VT-x/EPT or AMD-V/RVI

it works now

Yes , its slow . This might be due to 32 bit support

Thanks man for that command, u saved the day

Exactly this: Happend after WSL installation. I forgot about HyperV being installed when doing that, and so I ran into that problem. 
This solved it. Thanks.
When I just clicked agreed to not using VT-X when it prompted me, during startup of the machin, it threw an HV error. 
"VMware Workstation does not support nested virtualization on this host."

Try to replace Workstation versions, I hope this will work.

Making setting under option tab -Virtualization engine in existing workstation will make you VM working slow

You must remove Hyper-V from (Control panel) ----> (Program and features) ---->(Turn windows features on or off) then remove click on (Hyper-V).

Thank you so much @sachira! I unchecked all three virtualization engines and it worked for me! Now I can finally get back to my virtual machine after months of searching for solutions!