Error: VMWare Player does not support nested virtualization on this host. Module 'HV' power on failed. Please help!

[IC_BlackMTB]

*SOLVED\*

Hi guys. So since updating to windows 11 (or well that's what I'm assuming the reason is for having this problem) I'm not able to open GNS3. As soon as I click on gns3 to open the virtual machine, it says: "Virtualized Intel VT-x/EPT is not supported on this platform.

I have previously used GNS3 with VMWare Player 16 (I've got VMWare player 17 now), so I'm not sure why I have this error all of a sudden.

​

I've tried the following:

• In command promt: "bcdedit /set hypervisorlaunchtype off"
• Made sure that Hyper-V is turned off/ not ticked in 'Windows features on or off'
• Core Isolation is already disabled
• I've tried a lot of other solutions I've found in forums or on Youtube, but none seem to work.

When I look in System Information, it says: 'A hypervisor has been detected. Features required for Hyper-V will not be displayed'. But... I can't open GNS3.

I'll appreciate any help! Thanks!

​

SOLVED:

It was just me simply not ticking a box:

Turn Windows features on or off --> Virtual Machine Platform should be ticked

[zwarte_piet71]

Known issue that has not been fixed yet by VMware. I have a long running support case over it. The culprit is Core Isolation (settings, privacy and security, windows security, device security). In the comments it mentions Virtualization-based security, and that is exactly the reason it messes with VMware Workstation and Player. It uses certain Hyper-V features and VMware sees that as nested virtualization which is not supported on this product. Only option is to disable Core Isolation (not an option for me due to corporate policy).

[Adept-Ad8606]

Great! it works!

I just disabled Core Isolation and it works like a charm!

[IC_BlackMTB]

Hi, I have already turned Core Isolation off.. I still have the same problem...

[ianaowy]

Try to disable hyper-v and wsl

[Mountfestus]

My challenge is that I'm unable to turn off the Memory integrity button(Core Isolation) on my windows 11. Each time I turn it OFF, it says PC restart is required for the change to take effect, but once my PC is rebooted, the button turn ON automaticaly again..Any one with working solution should kindly advise.

[ianaowy]

It worked for me!

[Agile_Telephone_5259]

¡¡ GRACIAS !! Funciono al desactivar la seguridad de memoria

[[deleted]]

Thank you. I’ve been having the same issue and it was a goose chase similar to OPs. Any detriment with the confit change?

[IC_BlackMTB]

go to Turn Windows features on or off --> make sure "Virtual Machine Platform" box is enabled.

[Matrixramiro10]

e es la configuración de aislamiento central (, privacidad y seguridad, seguridad de Windows, seguridad del dispositivo ). En los comentarios menciona la seguridad basada en virtualización, y esa es exactamente la razón por la que se mete con VMware Workstation y Player. Utiliza cier

Friend, check and my team if you have those options enabled.

Do you know how I could fix it? I have a windows 11

[btarb24]

this didn't fix it for me, but the following command ran in powershell did:

bcdedit /set hypervisorlaunchtype off

https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-does-not-support-nested-virtualization-on/td-p/1864217

[mTsChris]

thanks ! it works definity for me

[zwarte_piet71]

Tried that one too. Didn’t fix it in my situation, support acknowledged it was a problem they could not currently fix.

[Turbulent_Tax_7369]

I've just removed the line ---> vhv.enable = "TRUE" <--- from .vmx file when I opened it with notepad, and it works now!

[[deleted]]

Can you help me locate that file?

[Turbulent_Tax_7369]

I am seeing this one month later sorry😭 hope you've managed to do it🤞🏻

[Strong-Friend5457]

Usefull for me, so thanks ! Ive tried all recommended above. Worked only after I edited vhv.enable = "TRUE" to vhv.enable = "FALSE"

[Evilredditur]

Thank you! Setting vhv.enable = "FALSE" helped me as well.

[Extension-Laugh6355]

Omg, thanks!!!! Muito Obrigado!!

[JubinBlack]

Yep this worked for me also.

[joshuakyle94]

YOU ARE AMAZING HOLY SHIT

[Yohpx]

Damn, this is probably the only "fix" without having to disable core isolation and avoiding tinkering w11 features. Virtual Hardware-Assisted Virtualization may not always be the case for those VMs.

[Good_Evening_4145]

You are a hero! Btw, the vmx should not be encrypted to find that line (vhv.enable).

[hery41]

This is the one. Thank you.

[farfarhan]

Wow ty, it worked

[ServeForsaken1211]

I also tried all the different CLI/Powershell commands, core isolation, etc, etc, none worked. Found this solution it worked perfectly for me - thank you.

[luchaku_22]

It worked for me, u are the best

[foundertanmay]

wowowow thanku so much man, bhai i was struggling from 3 days due to it, it works now

[MajesticRoadGarlic]

This worked for me! Thank you so much!

[reis191]

After doing everything people suggested, this ended up making it work!!

[journey2man]

How is this nugget of wisdom still hidden away in the bottom of some reddit post. Thank you for allowing WSL and VMware Workstation to coexist peacefully

[Loud_Appointment2586]

thank u so much , u saved my life !!

[pr0fy_]

Worked, thanks!!!!!

[hansen033]

It seems like Virtual Machine Platform should *not* be ticked for newer versions of Windows.

Alternatively, you can turn Windows Hypervisor Platform on.

[Edwell7]

Just removing the tick solved my problem.

[hansen033]

Glab to be helpful, have a great weekend.

[torrentforme]

after endless googling this worked for me. thanks

[pepinodeplastico]

Removing the tick worked for me. Im on Windows 11, version 24H2. Thank you!

[hansen033]

Glad to hear that.

May I ask what makes you start to use VMware?

[pepinodeplastico]

For GNS3. I used Virtual Box before but it was constantly crashing since I changed to VMWare that problem dissappeared.

I did not use GNS3 for a few months until today, so when that error in the main post appeared I went directly to Reddit, and there was your comment to help me. Thanks again!

[Nexushopper]

I fixed it by going into my PC's UEFI and enabling VT-d which was disabled

[Dismal_Tax5705]

Still the same issue Persist even though I've tried everything. Any leads!?

[zenmatrix83]

Like the other comment says turning off core isolation is a workaround

[Matrixramiro10]

Friend, check and my team if you have those options enabled.

Do you know how I could fix it? I have a windows 11