Disable Hyper-V on Windows

Download the Hyper-V tool, apply DisableVBS.reg, turn off Memory integrity, and restart Windows for tools that require this compatibility setup.

Step 1

BlueStacks download

Hyper-V Tool

HD-DisableHyperV_native_v2.exe

Step 1

Download the Hyper-V tool

Download HD-DisableHyperV_native_v2.exe from the BlueStacks link below. Save your work before continuing. Disabling Hyper-V and VBS reduces Windows security protections and can affect WSL2, Docker, and virtual machines; use this setup only when your tool requires it.

Step 2

Downloads

Hyper-V Tool

Run as administrator

Follow the prompts

Step 2

Run the tool as administrator

Open Downloads, right-click HD-DisableHyperV_native_v2.exe, and select Run as administrator. Approve the Windows permission prompt and follow the tool instructions. If it asks you to restart, do so, then return to this guide.

Step 3

DisableVBS.reg

Back up DeviceGuard first

Merge registry file

Restart to apply

Step 3

Download and merge DisableVBS.reg

Download DisableVBS.reg below. Before importing it, export the DeviceGuard key from Registry Editor as a backup. Double-click the downloaded file, approve the administrator prompt, then choose Yes to merge it. This file sets VBS, platform security requirements, and the DeviceGuard WindowsHello scenario to 0. It does not remove your Windows Hello PIN.

Step 4

Windows Security

Device security

Core isolation

Memory integrity: Off

Step 4

Turn off Memory integrity

Open Windows Security from Start. Select Device security, then Core isolation details. Turn Memory integrity off and approve the administrator prompt if it appears. If it is already off, leave it off for this setup. If the setting is managed by your organization, contact your administrator. Restart in the next step to apply the change.

Step 5

Restart required

Save your work

Apply changes after reboot

Step 5

Restart and check the result

Restart Windows after importing the registry file. Press Win + R, type msinfo32, and check Virtualization-based security in System Summary. If it still shows Running, the changes have not fully taken effect; managed policies or firmware settings may override them. Reopen your tool after the restart. Restore your previous security settings when this compatibility setup is no longer needed.