VMware Workstation Error: Virtualized AMD-V/RVI Is Not Supported on Windows 11

I am trying to run Cisco Modeling Labs (CML) using VMware Workstation on a Lenovo laptop running Windows 11 Pro.

When I power on the VMware virtual machine, I receive this exact message:

Virtualized AMD-V/RVI is not supported on this platform. Continue without virtualized AMD-V/RVI?

I need nested hardware virtualization for my CML environment. Continuing without virtualized AMD-V/RVI is not an acceptable solution for my intended setup.

Microsoft Support previously recommended resetting Windows. I completed the reset, but the problem persists.

System information

• Manufacturer: Lenovo
• Model: 21CRS10100
• Operating system: Windows 11 Pro
• OS build: 10.0.26200
• RAM: 16 GB
• Device is a standalone workstation.

Troubleshooting and evidence

1. Microsoft hypervisor is still present

Command:

Get-CimInstance Win32_ComputerSystem | Select-Object Manufacturer, Model, HypervisorPresent

Result:

HypervisorPresent = True

2. Virtualization-based security remains active

The Win32_DeviceGuard query returns:

• VirtualizationBasedSecurityStatus = 2
• SecurityServicesConfigured = {2, 3}
• SecurityServicesRunning = {0}
• RequiredSecurityProperties = {1, 2, 3}

System Information also reports that virtualization-based security is running and that a hypervisor has been detected.

Memory Integrity is Off.

3. Microsoft VBS platform policy remains enforced

CiTool.exe --list-policies lists the following policy:

• Friendly name: Microsoft Windows Virtualization Based Security Policy
• Policy ID: a072029f-588b-4b5e-b7f9-05aad67df687
• Platform policy: True
• Signed: True
• Authorized: True
• Currently enforced: True

This policy was present before and after the Windows reset.

I am not assuming that the policy alone is responsible for starting the hypervisor.

4. Other checks

• No Group Policy Objects are applied.
• No work or school account is shown in Windows Settings.
• VBS is enabled in the system and policy registry locations.
• The current Windows boot entry does not explicitly list hypervisorlaunchtype or vsmlaunchtype.
• Previously setting both BCD options to Off did not resolve the problem.