Fixing VMware “hv.capable was 0” and VT-x Support Errors on Windows

by

When running high-performance virtual machines in VMware Workstation, especially for macOS or nested virtualization, you may encounter critical errors that prevent the VM from booting. These errors occur because Windows is “locking” the CPU’s hardware virtualization features (VT-x/AMD-V) for its own security sub-systems, such as Hyper-V or Credential Guard.

The Problem

When you enable “Virtualize Intel VT-x/EPT” in your VM settings, you may see:

  • Feature 'hv.capable' was 0, but must be at least 0x1.
  • Virtualized Intel VT-x/EPT is not supported on this platform.
Feature "hv,capable" was 0, but must be at least 0x1.Module "FeatureCompatLate"
Virtualized Intel VT-x/EPT si not supported on this platfor error

To verify the conflict, open System Information (Win + R -> type msinfo32). Scroll to the bottom. If you see “A hypervisor has been detected”, it means Windows is running as a guest under its own Hyper-V layer, blocking VMware from accessing the hardware directly.

Level 1: Standard Component Deactivation

Before moving to advanced tools, ensure all standard Windows virtualization components are fully disabled.

1. Windows Features GUI Open “Turn Windows features on or off” and uncheck:

  • Hyper-V (all sub-items)
  • Virtual Machine Platform (the engine behind WSL 2)
  • Windows Hypervisor Platform
  • Windows Sandbox
  • Windows Subsystem for Linux (to ensure no background dependencies)

Note: Disabling these features will temporarily break WSL and Windows Sandbox functionality. You can always re-enable them later if needed.

Turn off windows features that uses virtualization

2. Core Isolation (Memory Integrity) Navigate to Windows Security > Device Security > Core Isolation details.

  • Toggle Memory Integrity to Off.
disabling memory integrity in core isolation settings

3. Comprehensive PowerShell Cleanup Standard GUI toggles sometimes leave “orphaned” services. Run these commands in PowerShell as Administrator to ensure all virtualization platforms are decommissioned:

# Disable core Hyper-V and Sandbox components
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Disable-WindowsOptionalFeature -Online -FeatureName Containers
Disable-WindowsOptionalFeature -Online -FeatureName Windows-Sandbox

# Disable platforms and WSL
Disable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform
Disable-WindowsOptionalFeature -Online -FeatureName Windows-Hypervisor-Platform
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

# Finalize by ensuring the hypervisor is off in the bootloader
bcdedit /set hypervisorlaunchtype off

Level 2: BIOS/UEFI Verification

Ensure your hardware is configured to allow third-party virtualization access.

  • Intel VT-x / AMD-V: Must be Enabled.
  • VT-d: Should be Enabled.
  • Secure Boot: If Level 1 fails, try disabling Secure Boot temporarily. Secure Boot can force Windows to enable Virtualization-Based Security (VBS) despite OS settings.

Level 3: The “Nuclear Option” (Device Guard Readiness Tool)

If msinfo32 still reports a detected hypervisor, Windows is likely running Credential Guard or Device Guard. These features are deeply embedded in the kernel and often ignore standard command-line fixes.

1. Download the Tool:
Download the Device Guard and Credential Guard hardware readiness tool (dgreadiness_v3.6.ps1) from Microsoft’s official site:

https://www.microsoft.com/en-us/download/details.aspx?id=53337

2. Execute the Disable Command:
Run PowerShell as Administrator, navigate to the folder where you extracted the script, and execute:

.\DG_Readiness_Tool_v3.6.ps1 -Disable

Note: If restricted by execution policy, run Set-ExecutionPolicy Unrestricted first.

3. Confirm in UEFI (The Critical Step) Restart your computer. Before Windows loads, you will see a black-and-white text prompt from the UEFI.

  • You must press the required key (usually F3 or Y) to confirm the deactivation. If you miss this prompt or ignore it, the script will have no effect.

Level 4: Rare Edge Cases

If the issue persists after the final reboot, check these rare conflicts:

  • Third-Party Antivirus: Avast, AVG, or Kaspersky often use hardware-assisted virtualization for sandboxing. Disable “Enable hardware-assisted virtualization” in your AV settings.
  • Windows Fast Startup: This feature hibernates the kernel and may prevent changes from applying. Always use Restart or hold Shift while clicking Shut Down to ensure a deep hardware reset.
  • Side-Channel Mitigations: In VMware, go to VM Settings > Options > Advanced and check “Disable side channel mitigations for ITL enabled virtual machines”.

Final Verification: The “Four Yes” Rule

Open msinfo32 again. Scroll to the bottom. The “Hypervisor detected” warning should be gone. Instead, you should see four specific Hyper-V requirements (SLAT, Monitor Mode Extensions, etc.), and all must show Yes.

Once you see the four “Yes” results, you can safely enable “Virtualize Intel VT-x/EPT” in your VMware settings, and your virtual machine will boot with full hardware acceleration.

Leave a Comment