How to Disable Hyper-V in Windows 11

Hyper-V is Microsoft's built-in virtualization platform, and on Windows 11 it runs quietly in the background whether you're actively using it or not. That background presence is exactly why some users need to turn it off — and why disabling it isn't always as straightforward as unchecking a box.

What Is Hyper-V and Why Does It Run Automatically?

Hyper-V is a Type-1 hypervisor built directly into Windows. Unlike software-based virtualization tools, it operates at the hardware level, sitting between your physical machine and the operating system. This gives it low-level control over CPU and memory resources.

Windows 11 enables Hyper-V components automatically in certain situations — particularly when features like Windows Sandbox, Windows Subsystem for Linux 2 (WSL2), Virtual Machine Platform, or Device Guard are active. Even if you've never opened a virtual machine, Hyper-V may already be running because one of these dependent features switched it on.

This matters because an active Hyper-V layer can interfere with other hypervisors like VMware Workstation or VirtualBox, reduce performance in certain games or benchmarking tools, and occasionally conflict with low-level hardware access applications.

The Four Main Methods to Disable Hyper-V ⚙️

Method 1: Windows Features (Turn Windows Features On or Off)

This is the most accessible route for most users.

1. Press Windows + R, type optionalfeatures, and hit Enter
2. In the list, locate Hyper-V and uncheck the entire entry — including all sub-items
3. Also uncheck Virtual Machine Platform and Windows Hypervisor Platform if present
4. Click OK and restart when prompted

Important: Unchecking Hyper-V here disables the management tools and platform features, but it may not fully remove the hypervisor from the boot process. A deeper disable requires the next method.

Method 2: BCDEdit (Boot Configuration Data)

This command disables the Hyper-V hypervisor at the bootloader level — the most thorough approach.

1. Open Command Prompt or PowerShell as Administrator
2. Run: bcdedit /set hypervisorlaunchtype off
3. Restart your PC

To re-enable it later: bcdedit /set hypervisorlaunchtype auto

This method is especially relevant for users running VMware or VirtualBox, since those tools need direct hardware access that Hyper-V blocks when active at boot.

Method 3: PowerShell (Disable-WindowsOptionalFeature)

For users comfortable with PowerShell, this command handles the removal cleanly:

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

Run this in an elevated PowerShell window (right-click → Run as Administrator). A restart is required to apply the change.

Method 4: BIOS/UEFI — Virtualization Settings

If software-level disabling isn't enough, or if you're troubleshooting deep compatibility issues, the underlying virtualization support can be toggled in your BIOS/UEFI firmware. Look for settings labeled Intel VT-x, AMD-V, or SVM Mode.

⚠️ Disabling virtualization in BIOS affects all virtualization software, not just Hyper-V. This is a more drastic step and rarely necessary unless you're dealing with a specific low-level conflict.

What Gets Affected When You Disable Hyper-V

Disabling Hyper-V doesn't just turn off the virtual machine manager — it cascades through several Windows features:

Understanding these downstream effects is important before committing to the change, especially in work or development environments where WSL2 or Sandbox may be part of a regular workflow.

Variables That Determine Your Experience 🖥️

Not every user lands in the same place after disabling Hyper-V. Several factors shape the outcome:

• Windows 11 edition — Pro, Enterprise, and Education editions have Hyper-V available; Home does not, though related components like Virtual Machine Platform may still be active
• Security policies — In managed or enterprise environments, Credential Guard and Device Guard may re-enable Hyper-V components through Group Policy, overriding manual changes
• What prompted the disable — Gaming conflicts, VMware installation, and anti-cheat software incompatibilities each point to slightly different steps (some games specifically require the BCDEdit method, not just the features panel)
• Driver and firmware state — Some hardware configurations behave differently, particularly on systems with older UEFI firmware or non-standard virtualization support
• Other installed software — Security tools, sandboxing apps, and certain VPN clients can reactivate virtualization-dependent features

A user disabling Hyper-V to run VMware Workstation smoothly follows a different priority order than someone doing it to fix a game that won't launch. The methods overlap, but the sequence and scope differ based on what's actually causing the conflict.

Re-Enabling Hyper-V

Every method above is reversible. Re-checking the Windows Features boxes, running bcdedit /set hypervisorlaunchtype auto, or using the PowerShell enable command (Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All) restores full functionality after a restart. Nothing is permanently removed.

Whether the full disable, a partial disable, or just isolating one conflicting feature is the right path depends entirely on what's running on your machine and what you're trying to achieve with it.