Virtualized AMD-V/RVI is not supported on this platform.

[william23]

I get this message when I try to open my old Win 11 image:

 

Virtualized AMD-V/RVI is not supported on this platform.

Continue without virtualized AMD-V/RVI?

 

and if I press yes I get error

 

Error while powering on: VMware Player does not support nested virtualization on this host.

Module 'HV' power on failed.

Failed to start the virtual machine.

 

I made sure hypervisior not installed and SVM enabled in the bios what else I can do ?

[Breno_Andrade]

I still having the same problem here. [SOLVED] 

[intunericitul]

Disable Hyper-V from Windows Features
Disable Virtual Machine Platform and Windows Hypervisor Platform options from Windows Features
Disable Core Isolation from Windows Security Settings

How to Disable or Remove Hyper-V in Windows 11 (makeuseof.com)

[Breno_Andrade]

I found something new that worked for me.

After confirming that my BIOS processor virtualization setup was correctly enabled and tried "bcdedit /set hypervisorlaunchtype off" without effect in my machine, I found another info that solved my problem here.

"Disable Turn on virtualization Based Security"

Go to Local Group Policy Editor > Computer Configuration > Administrative Templates > System > Device Gaurd

Disable Turn On Virtualization Based Security.

[AreJAyEm]

I'm having exactly the same problem with VMware Workstation Player 16 and ESXi 7, unfortunately editing the "Turn on virtualisation based security" to disabled in the Local Group Policy as suggested by Breno_Andrade has not worked 

Any other suggestions appreciated.

[AreJAyEm]

Disabling Windows Subsystem for Linux from the Programs and Features > Turn Windows Features On or Off menu solved this for me.

[jjfad]

Thank you. Removing the Linux Subsystem worked for me. 

[ChHi]

With the latest OS you need every time to decide.

Security Features for Functional Features

 

If security features enabled you can't use all features in VMware Player.

So the virtual machine will never have the possibility to enable the same security features as on the physical device.

In Windows you will need to have a the possibility to use HyperV to enable the same security features as on your physical device.

 

Hopefully it will be changed anytime

[shallu]

hello,

I have windows 11 and i do not see an option to open this local group policy editor. Could you please suggest what am i missing

[PleasantDay]

I could be wrong but I think GPO is not on Windows 11. I think I have previously tried a add-on GPO download.

[Jack Edwards]

This just worked for me after trying everything else on the first 5 recommendations on Google. Thanks. 

[Sybassion]

All above solutions didn't work for me (I use AMD Ryzen 5 2600 with Windows 10 Pro 22H2 and VMware Workstation Pro 17). But this action solved my problem:

Execute this command in windows command-line with Administrator privilege and reboot system:

bcdedit /set hypervisorlaunchtype off

---

[Duong_NguyenT]

It works for me to (I use Ryzen 7 4800H) Thank you so much.

[Moon9Shadow]

this suggestion worked for me. thank you bro.

[PleasantDay]

this worked for me. TY Heaps & Kind regards.

 

running AMD Ryzen 7 3700X 8-core

VMware 17 - esxi 6.7.0

[Bhanu Naik]

Issue has been fix by below URL

https://bhanuwriter.com/virtualized-amd-v-rvi-is-disabled/

[VMware Community Member]

Thanks a lot, this worked for me too

[rehanj]

Disabling Side channel mitigations for Hyper-V enabled hosts worked for me.

VM Settings -> Options -> Advanced

My System: Workstation 17 Pro on Windows 11 Pro with WSL on Ryzen 7 Pro.

[sophin123]

Enabling Side channel mitigation and Enabling Secure boot under UEFI worked for me.

 

[lucianoevazquez]

My CPU AMD Ryzen 7 5700G, my OS WIN 10 22H2, I had to make 3 things: 

bcdedit /set hypervisorlaunchtype off

Disable Turn On Virtualization Based Security

Disabling Windows Subsystem for Linux 

after a reboot, I could run the VM successfully. thanks a lot!

[Olafha]

I had the same issue, my vm player was running ok, but, suddenly it wasn't. So it happened me before, then I remembered it, so, I left the picture about it. Just unselect the green box.

 

[TechDevil84]

Worked for me, thx a lot.

[backend@dat]

But then you can't run nested VMs like ESXi-8 with more VMs in there ... Worked for years, was great for testing / home lab. Now gone thanks to MS.