> ## Content Index > Fetch the complete content index at: https://elevendecoded.com/llms.txt > Use this file to discover other available public pages before exploring further. # How to Disable Hyper-V on Windows 11 Fast and Easily - URL: https://elevendecoded.com/disable-hyper-v-windows-11/ - Published: 2026-09-17T13:21:23.000Z - Updated: 2026-10-22T18:39:02.000Z - Author: Md Fakharuddin - Tags: Windows Tips, Virtualization, Hyper-V, Windows 11 Disabling Hyper-V can help diagnose a virtualization compatibility problem, but it also affects features that depend on the Windows hypervisor. Check your VM software's current requirements before changing Windows. ### Why Disabling Hyper-V Requires More Than Just Unchecking a Box The Hyper-V optional feature, the running Windows hypervisor, and virtualization-based security (VBS) are related but different. Memory integrity and Credential Guard can use the hypervisor even when you have not created a Hyper-V VM. Windows 11 Home does not include the full Hyper-V role, but it can still use hypervisor-based features. It is also inaccurate to say that every third-party VM application is blocked whenever Hyper-V runs. Recent VirtualBox versions can use a Hyper-V backend on supported Windows hosts, although performance and compatibility can differ. Consult the [Oracle VirtualBox documentation](https://docs.oracle.com/en/virtualization/virtualbox/7.2/user/EN-VBOX-7-2-USER.pdf?ref=elevendecoded.com) and the support instructions for your installed product and version. ### Check the Current State First Run `systeminfo` in Command Prompt. A message that a hypervisor has been detected indicates a running hypervisor; it does not identify which optional feature or security setting started it, and it is not itself an error. Open System Information with `msinfo32` and review the virtualization-based security entries in System Summary. Also check Windows Security > Device security > Core isolation for memory integrity, where available. Record the current settings and the exact VM error. Update the VM application and check its supported Windows backend before deciding to disable anything. ### Understand the Consequences Stopping the Windows hypervisor can stop Hyper-V VMs, WSL 2, Windows Sandbox, and Docker configurations that depend on Hyper-V or WSL 2\. It can also prevent hypervisor-based security protections from running. Removing an optional feature is not the same as deleting a VM's files, but back up important VM data before changing the host. On a work or school device, consult the administrator about required security and virtualization policies. Do not repeatedly override a setting that management restores. ### Remove Only the Optional Features You No Longer Need 1. Open Control Panel > Programs > Turn Windows features on or off. 2. To remove the Hyper-V role, clear Hyper-V if it is present and enabled. 3. If your VM vendor specifically requires the Windows hypervisor to be absent, review Virtual Machine Platform and Windows Hypervisor Platform as well. Leave them enabled when required by software you intend to keep using. 4. Apply the selected changes and restart when prompted. Unchecking Hyper-V alone does not prove that VBS or every other hypervisor-dependent feature has stopped. Review the running state again after restarting. Disabling memory integrity or Credential Guard has separate security consequences; use the relevant Microsoft and administrator instructions rather than indiscriminately turning off protections. ### Optional Boot Configuration Test Use this only when you have decided to stop the hypervisor for troubleshooting and understand the dependencies. Save your work, back up important data, and make sure the BitLocker or Device Encryption recovery key is available. Boot configuration changes can trigger recovery or cause startup problems. In an **administrator Command Prompt inside the affected Windows installation**, first record the current boot entry: ``` bcdedit /enum {current} ``` Then, if appropriate, prevent hypervisor launch for that Windows entry: ``` bcdedit /set {current} hypervisorlaunchtype off ``` Restart to apply the change. This controls launch; it does not uninstall optional components or permanently remove security policies. Do not paste this command into Windows Recovery Environment and assume that `{current}` identifies the installed Windows system. Microsoft documents the setting and boot-editing cautions in [BCDEdit /set](https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--set?ref=elevendecoded.com). Do not disable Secure Boot or clear the TPM simply to troubleshoot a VM. ### Verify and Restore After restarting, check `systeminfo`, System Information, and the VM application's own logs or status. Test the same workload. Hypervisor absence alone does not guarantee that a VM will start or run faster: firmware virtualization, host resources, VM configuration, and drivers can still matter. Keep Intel VT-x or AMD-V enabled in firmware when your VM software requires it. To allow Windows hypervisor launch again for the same entry, use an administrator Command Prompt inside that Windows installation: ``` bcdedit /set {current} hypervisorlaunchtype auto ``` Restart, re-enable any required optional features you removed, and restore the security configuration you recorded. The Auto setting allows launch; required components and policies must also be in place. Check that dependent applications and intended security services are actually running. If Windows itself fails to start, use Windows recovery options and diagnose the specific failure. A WSL or Docker dependency failure alone does not establish the cause of a Windows boot failure. For further diagnosis, see the [Hyper-V troubleshooting guide](https://elevendecoded.com/troubleshooting-hyper-v-windows-11).