Virtualization Based Security is preventing VMware Workstation from using Intel VT-x/AMD-V. Hyper-V appears disabled but virtualization is still unavailable.

Question

Virtualization Based Security is preventing VMware Workstation from using Intel VT-x/AMD-V. Hyper-V appears disabled but virtualization is still unavailable.

Answer 1

Hi,

Besides the Q&A Assist procedure, you can disable the

Virtual Machine Platform

Windows Hypervisor Platform

Press the Windows key + R, type optionalfeatures and press Enter.

Open Command Prompt (admin) and run the command:

bcdedit /set hypervisorlaunchtype off

Check if VT-d is enabled in the BIOS.

Please consider rating the question (accepting the answer or not) and visiting the Microsoft Q&A community if you have further questions.

Thanks

Answer 2

This is expected behavior when Virtualization-Based Security (VBS) or other Hyper-V-dependent security features are still active. Third-party virtualization apps such as VMware Workstation can’t use Intel VT-x or AMD-V alongside Hyper-V, Memory Integrity, or Credential Guard because only one software component at a time can use the hardware virtualization extensions.

Use this check first:

1. Open msinfo32.exe.
2. In System Information, look for: A hypervisor has been detected. Features required for Hyper-V will not be displayed.

If that message appears, the Hyper-V hypervisor is still running even if the Hyper-V feature looks disabled.

To make VMware Workstation use VT-x/AMD-V again, disable the Hyper-V hypervisor and the dependent VBS features:

1. In Control Panel → Programs and Features → Turn Windows features on or off.
2. Expand Hyper-V → Hyper-V Platform.
3. Clear Hyper-V Hypervisor.

Or use an elevated PowerShell window:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

Or use an elevated Command Prompt:

DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-Hypervisor

Also disable the security features that depend on Hyper-V:

• Memory Integrity
• Credential Guard

These features can be disabled by using Microsoft Intune, Group Policy, or registry entries. Disabling them reduces security protections, so this change should be made only if VMware access to hardware virtualization is required.

If VBS must remain enabled, the supported alternative is to use Hyper-V instead of VMware Workstation, because Hyper-V is designed to operate with VBS enabled.

---

• Virtualization applications don't work together with Hyper-V and Hyper-V-based features
• Virtualized Intel VT-x/EPT is Not Supported on this Platform when Device Guard and Credential Guard are enabled on Surface Pro 8 - Microsoft Q&A