How to Disable Hyper-V in Windows 11 24H2

[pepe gonzales]

In this guide, I will explain how to disable Hyper-V in Windows and use Intel VT-x/EPT or AMD-V/RVI in any virtualization program, such as VirtualBox or VMware (in my case). The final step (6) is the key to disabling it in version 24H2, which has a bug that prevents it from being disabled.

---

Step 1: Stop Any Currently Running Hyper-V Services

1. Click on the Start menu.
2. Type services (without quotes) and press [ENTER].
3. In the Services window, browse through the list and look for any services that include "Hyper-V" (e.g., "HV Host Service").
4. If any of these services are running, right-click on them and select Stop.
5. Close the Services window.

---

Step 2: Ensure Hyper-V and Related Features Are Not Installed

1. Click on the Start menu.
2. Type Features (without quotes) and select "Turn Windows Features on or off".
3. In the Windows Features window, ensure the following options are unchecked:
• Hyper-V (including all sub-items).
• Windows Hypervisor Platform.
• Linux subsystem for windows
4. Click OK and wait for the changes to apply.
5. Restart your computer if prompted.

---

Step 3: Disable "hypervisorlaunchtype"

1. Click on the Start menu.
2. Type powershell (without quotes), right-click on Windows PowerShell, and select Run as administrator.
3. In the PowerShell window, type the following command and press [ENTER]:
4. bcdedit /set hypervisorlaunchtype off
5. Close the PowerShell window.

---

Step 4: Disable Device Guard (If Applicable)

Note:

• This step may not apply to all versions of Windows.
• The Group Policy Editor (gpedit.msc) is not available in Windows 11 Home.

1. Click on the Start menu.
2. Type gpedit.msc (without quotes) and press [ENTER].
3. In the Group Policy Editor, navigate to:
4. Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard
5. Double-click on "Turn on Virtualization Based Security".
6. Select Disabled and click OK.

---

Step 5: Disable "Memory Integrity" in Core Isolation

1. Click on the Start menu.
2. Type core isolation (without quotes) and press [ENTER].
3. In the Core Isolation window, ensure that "Memory Integrity" is turned Off.
4. Close the window.

---

Step 6: Mandatory step for Windows 11 24H2

Windows 11 24H2 has a known issue where Hyper-V might still interfere even after following the above steps. To resolve this, you'll need to use the Microsoft Device Guard and Credential Guard Hardware Readiness Tool:

1. Download the Device Guard and Credential Guard hardware readiness tool from Microsoft.
• https://www.microsoft.com/en-us/download/details.aspx?id=53337
2. Extract the downloaded ZIP file.
3. Use the tool to disable Device Guard and Credential Guard:
• Open PowerShell window as an administrator.
• Navigate to the folder where you extracted the tool.
• Firs run this command to get Execution Policy:
• Set-ExecutionPolicy Unrestricted -Scope Process
• Now run the script with the -disable parameter to disable Device and Credential Guard
• DG_Readiness_Tool_v3.6.ps1 -Disable
4. Reboot your computer.
5. During the boot process, Windows will ask you to confirm the changes. Follow the on-screen instructions to proceed (Just press F3).

Note: Disabling Device Guard and Credential Guard will temporarily disable your Windows Hello PIN. However, you can re-enable it later without any issues.

---

Step 7: Confirm Hyper-V is Fully Disabled

1. After rebooting, open a PowerShell window as an administrator.
2. Run the following command to ensure Hyper-V is fully disabled:
3. bcdedit /set hypervisorlaunchtype off
4. Reboot your computer again.

---

Additional Notes

This method worked for me on Windows 11 24H2 for VMware Workstation and Virtualbox After completing these steps. I hope this actually helps someone, because I almost lost my mind trying to fix this

As far as I understand, this happens because in the new version, the security of the Windows Hello PIN and others things are based on the hypervisor, although it should be disabled if you want to disable the hypervisor, Microsoft should provide a simpler option to disable it completely and take the risks.

I am not responsible if someone breaks their system or creates a security breach. I'm just trying to help, something Microsoft doesn't do, considering that the original deactivation guide is the same as always.

[Cfgtech Cfgtech]

Hi, I created an account just to thank you ! As this was also driving me nutz and I had tried all the settings except for Step 6 and ultimately that is what fixed it. I have 1 PC with Win10 and 1 with Win11 the other thing that tripped me was Win11 had player when I installed Vmware workstation Pro it could not find vmnetbridge.dll point it to C:\Program Files (x86)\VMware\VMware Workstation\ and it will go thru. Everything is working perfectly now Thanks Again!

[RaSystemlord]

This looks like a very comprehensive answer. Thanks!

[Massimo Andriotto]

Many MANY thanks for sharing. 

-------------------------------------------

[Yevhen Lezniuk]

Thanks man, Step 6: Mandatory step for Windows 11 24H2, which only helped me. So many time missed trying to do it before I found your post. Get registered only to thanks you

-------------------------------------------

[ANTHONY SITI]

You have no idea the amount of hair I pulled out to get this working right and I can confirm that this work. I have searched the internet for answers and kept getting a "disable this or disable that". I almost gave up until I found this post. Thank you so much. One last thing, do you see Microsoft releasing a patch or update that would cause this to break or revert back the default settings?

-------------------------------------------

[Nicolas Soto]

In step 6 this happens to me:

PS C:\Users\Sonda\Downloads\dgreadiness_v3.6> DG_Readiness_Tool_v3.6.ps1 -Disable
DG_Readiness_Tool_v3.6.ps1 : El término 'DG_Readiness_Tool_v3.6.ps1' no se reconoce como nombre de un cmdlet, función,
archivo de script o programa ejecutable. Compruebe si escribió correctamente el nombre o, si incluyó una ruta de
acceso, compruebe que dicha ruta es correcta e inténtelo de nuevo.
En línea: 1 Carácter: 1
+ DG_Readiness_Tool_v3.6.ps1 -Disable
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (DG_Readiness_Tool_v3.6.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: No se encontró el comando DG_Readiness_Tool_v3.6.ps1, pero existe en la ubicación actual. Windows PowerShell no carga comandos de la ubicación actual de forma predeterminada. Si confía en este comando, escriba ".\DG_Readiness_Tool_v3.6.ps1". Vea "get-help about_Command_Precedence" para obtener información más detallada.
PS C:\Users\Sonda\Downloads\dgreadiness_v3.6>

any suggestions?

-------------------------------------------

[Morc001]

Did you actually read the error message, especially the Suggestion part? The answer is literally in there.

-------------------------------------------

[Nicolas Soto]

I've already found the "detail," and it's basically how to run the script in the folder...

It doesn't run as
"DG_Readiness_Tool_v3.6.ps1"

This is how it should run:
".\DG_Readiness_Tool_v3.6.ps1 -Disable"

-------------------------------------------

[Alc Alc]

Hi,
unfortunately not worked for me. Maybe is because my windows version is already the 25h2...
Does someone have solutions?

-------------------------------------------

[Dr Dv]

I'm running 25H2 as well and it worked. step 6 was what i was missing.
My only problem is my with Windows Hello PIN -> i can't use it (re-enable).The remove button is grayed. for now i didn't figure out how to re-enable PIN. anyone?

BEFORE:
```
C:\Users\admin>systeminfo | findstr "Hyper-V" Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
```

AFTER: (not detected anymore)
```
C:\Users\admin>systeminfo | findstr "Hyper-V"
Hyper-V Requirements:          VM Monitor Mode Extensions: Yes
```

-------------------------------------------

[Morc001]

As far as I know Windows Hello requires VBS on Windows 11.

-------------------------------------------

[Dr Dv]

Actually, Windows Hello PIN is working now..

-------------------------------------------

[James Mauser]

Fantastic!  Thanks for the comprehensive steps.  

-------------------------------------------

[Jake Moore]

Thanks for this - very detailed and helpful - worked for me too!

-------------------------------------------