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
- Click on the Start menu.
- Type services (without quotes) and press [ENTER].
- In the Services window, browse through the list and look for any services that include "Hyper-V" (e.g., "HV Host Service").
- If any of these services are running, right-click on them and select Stop.
- Close the Services window.
Step 2: Ensure Hyper-V and Related Features Are Not Installed
- Click on the Start menu.
- Type Features (without quotes) and select "Turn Windows Features on or off".
- In the Windows Features window, ensure the following options are unchecked:
- Hyper-V (including all sub-items).
- Windows Hypervisor Platform.
- Linux subsystem for windows
- Click OK and wait for the changes to apply.
- Restart your computer if prompted.
Step 3: Disable "hypervisorlaunchtype"
- Click on the Start menu.
- Type powershell (without quotes), right-click on Windows PowerShell, and select Run as administrator.
- In the PowerShell window, type the following command and press [ENTER]:
- bcdedit /set hypervisorlaunchtype off
- 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.
- Click on the Start menu.
- Type gpedit.msc (without quotes) and press [ENTER].
- In the Group Policy Editor, navigate to:
- Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard
- Double-click on "Turn on Virtualization Based Security".
- Select Disabled and click OK.
Step 5: Disable "Memory Integrity" in Core Isolation
- Click on the Start menu.
- Type core isolation (without quotes) and press [ENTER].
- In the Core Isolation window, ensure that "Memory Integrity" is turned Off.
- 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:
- Download the Device Guard and Credential Guard hardware readiness tool from Microsoft.
- Extract the downloaded ZIP file.
- 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
- Reboot your computer.
- 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
- After rebooting, open a PowerShell window as an administrator.
- Run the following command to ensure Hyper-V is fully disabled:
- bcdedit /set hypervisorlaunchtype off
- 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
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.
If you need assistance, consider asking ChatGPT, Deepseek, or similar tools, as I'm not an IT professional affiliated with Microsoft.
I can't believe that after all this time, this error and many others are still present in Windows 11 24H2, and they haven't released an update to fix it yet. It's disappointing how lazy the developers at Microsoft are becoming. They haven't made any major changes to the modern architecture of Windows since Windows 7, and yet there are still such nonsensical bugs like this one.