Hyper-V Controller

Fix "Hyper-V is still enabled" for Android emulators on Windows.

Open-source console tool to disable or enable Hyper-V, Windows Hypervisor Platform, Virtual Machine Platform, and Windows Sandbox in one step.

Built for people who need LDPlayer, BlueStacks, Nox, MSI App Player, or other Android emulators to run with better performance when Windows virtualization blocks them.

Download

Latest release (Windows x64):

https://github.com/denufka/hyper-v-controller/releases/latest

Files:

• hyper-v-controller.exe
• hyper-v-controller-windows-x64.zip

Run as Administrator, then reboot.

Why this exists

Windows features like Hyper-V, WSL2, Virtual Machine Platform, and Memory Integrity / VBS often break or slow down Android emulators.

Common symptoms:

• Hyper-V is still enabled
• emulator asks to disable virtual machine service
• VT-x / SVM unavailable while Hyper-V is on
• hypervisorlaunchtype still set to Auto

Vendors sometimes ship closed tools such as LDPlayer DisableHyperVRelatedFeatures.exe. This project does the same job with:

• open source code
• colored live status in the console
• enable and disable modes
• in-process DISM API (fewer slow dism.exe launches)

Features

• Colored status: ENABLED (green) / DISABLED (red)
• 0 = disable Hyper-V related features
• 1 = enable Hyper-V related features
• Updates DISM features, bcdedit, HvHost / vmms, and VBS-related registry keys
• Tells Hyper-V apart from third-party hypervisors (VMware, VirtualBox, KVM, Xen) so running inside a VM is not reported as "Hyper-V enabled"
• Optional one-key restart after applying changes
• Requires Administrator
• Restart required to fully apply

What it changes

Area	Details
DISM features	Microsoft-Hyper-V-All, HypervisorPlatform, VirtualMachinePlatform, Containers-DisposableClientVM
Boot config	bcdedit /set hypervisorlaunchtype off (both {current} and default entry) and vsmlaunchtype off
Services	HvHost, vmms start type
Registry	turns off VBS / HVCI / Credential Guard values in SYSTEM\...\DeviceGuard, disables the Windows Hello VBS dependency (24H2+), opts out of automatic VBS enablement (HyperVVirtualizationBasedSecurityOptout=1), and clears SOFTWARE\Policies\Microsoft\Windows\DeviceGuard (Group Policy can force VBS back on)

Usage

1. Download hyper-v-controller.exe from Releases
2. Right-click -> Run as administrator
3. Read the status list
4. Press 0 to disable or 1 to enable
5. Restart Windows

Warning

Disabling these features can also disable:

• WSL2
• Windows Sandbox
• Windows Hello (face / fingerprint) in some setups
• Memory Integrity / virtualization-based security

Use only if you need emulator compatibility more than those features.

Troubleshooting

After disabling, Hyper-V hypervisor should show DISABLED (not running) after a reboot. If it does not:

• Microsoft Hv, guest VM — this Windows runs as a Hyper-V virtual machine (on the host PC, Azure, Windows Sandbox, etc.). The hypervisor belongs to the host machine and cannot be disabled from inside the guest — disable Hyper-V on the host.
• 3rd-party: VMware / VirtualBox / KVM / Xen (VM guest?) — you are running inside a non-Hyper-V virtual machine; the host hypervisor sets the CPUID flag, not Windows Hyper-V. Nothing to disable on the guest.
• Hyper-V hypervisor ENABLED with hypervisorlaunchtype Off after a reboot:
  1. You did not reboot yet — changes apply only after restart.
  2. Memory Integrity shows on — toggle it off in Windows Security -> Device security -> Core isolation (or run the tool again as Administrator).
  3. VBS policy (GPO) shows on — Group Policy forces VBS: check gpedit.msc -> Computer Configuration -> Administrative Templates -> System -> Device Guard.
  4. VBS auto-enable shows on (Windows 11 24H2/25H2) — Windows turns VBS back on by itself on every boot, even with all other switches off. The tool opts out (HyperVVirtualizationBasedSecurityOptout=1); run it again as Administrator and reboot.
  5. Windows Hello VBS shows on — the Windows Hello security backend keeps VBS alive on 24H2+; the tool disables that dependency (PIN login keeps working).
  6. Windows Update may re-add virtualization features — run the tool again as Administrator.
  7. On Windows 11 Pro, Secure Boot alone does not force the hypervisor; but Core Isolation / Memory Integrity does — keep it off.

Build from source

Open Hyper-v-controller.slnx in Visual Studio 2022+ and build Release | x64.

Or:

msbuild Hyper-v-controller\Hyper-v-controller.vcxproj /p:Configuration=Release /p:Platform=x64

Output: build\hyper-v-controller.exe

Keywords

disable hyper-v, hypervisorlaunchtype off, Windows Hypervisor Platform, Virtual Machine Platform, Windows Sandbox, VBS, Memory Integrity, LDPlayer, BlueStacks, Android emulator Windows 11, Hyper-V is still enabled

License

MIT