You can disable Hyper-V in Windows 11 from Windows Features, PowerShell, or DISM. However, turning off the Hyper-V feature does not always disable every Windows component that can use the Microsoft hypervisor. Features such as Virtual Machine Platform, Windows Hypervisor Platform, Windows Sandbox, and security features can affect virtualization behavior too.
Before changing anything, identify why you need Hyper-V disabled. If you are troubleshooting another virtualization program, changing more Windows security features than necessary is usually a poor first step.
Method 1: Disable Hyper-V in Windows Features
- Press Windows + R.
- Type optionalfeatures and press Enter.
- Find Hyper-V.
- Clear the Hyper-V checkbox.
- Click OK.
- Restart the computer when prompted.
This is the simplest method on Windows editions that expose the Hyper-V feature.
Method 2: Disable Hyper-V with PowerShell
If you prefer an administrative command, open Windows Terminal or PowerShell as an administrator and run Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All. Restart Windows afterward so the change can take effect.
Command-line feature names and availability can vary by Windows edition, so confirm the result rather than assuming the command succeeded merely because it ran.
Method 3: Use DISM
DISM can also manage optional Windows features. Open Terminal or Command Prompt as an administrator and run DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-All, then restart Windows.
Hyper-V Is Off but Another Virtualization App Still Detects a Hypervisor
This is where many older Hyper-V tutorials become misleading. Hyper-V is not the only Windows feature related to the hypervisor.
Depending on what is installed and enabled, you may also see:
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Sandbox
- virtualization-based security features
- security features that depend on virtualization
Do not indiscriminately disable all of these. Determine which component conflicts with the software you are trying to use and follow that software vendor’s current compatibility guidance.
Do You Need to Disable Virtualization in BIOS or UEFI?
Usually, no. Disabling Hyper-V in Windows and disabling CPU virtualization in UEFI firmware are different actions.
Firmware virtualization—often labeled Intel Virtualization Technology, VT-x, AMD-V, or SVM—allows virtualization features to work. Turning it off at the firmware level affects more than Hyper-V and can prevent other virtual-machine and security features from working.
If your goal is simply to stop using Hyper-V, start by disabling the Windows feature rather than changing UEFI settings.
What About Memory Integrity?
Memory Integrity is a Windows security feature associated with virtualization-based security. Do not turn it off solely because an old tutorial says it is required to disable Hyper-V. If a specific application is incompatible, verify the current vendor guidance and understand the security tradeoff before changing it.
How to Turn Hyper-V Back On
- Press Windows + R.
- Type optionalfeatures.
- Select Hyper-V.
- Click OK.
- Restart the PC.
If Hyper-V is unavailable, check your Windows edition, hardware virtualization support, and firmware virtualization setting.
Does Windows 11 Home Include Hyper-V?
The full Hyper-V role is not exposed on every Windows 11 edition. If Hyper-V is missing from Windows Features, do not use unofficial scripts that claim to “unlock” unsupported Windows components without first understanding what they change. Other virtualization technologies may still be present because Windows features use them for purposes beyond the Hyper-V Manager application.
Summary
The safest way to disable Hyper-V is to turn off the Hyper-V Windows feature and restart the computer. If another virtualization program still reports that a hypervisor is active, investigate Virtual Machine Platform, Windows Hypervisor Platform, and virtualization-based security separately rather than disabling every virtualization or security feature at once. Disabling Hyper-V in Windows is also different from disabling CPU virtualization in BIOS or UEFI.