bluestacks hyper-v conflict fix

BlueStacks won’t start, or it throws a Hyper-V / virtualization error on launch. This is the single most common Android-emulator failure on Windows 11: BlueStacks and Hyper-V both want the machine’s virtualization layer, and they can’t share it.

What’s actually conflicting

Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, and Core Isolation (Memory Integrity) all turn on the Windows hypervisor. BlueStacks’ engine needs a different mode. When Hyper-V is on, BlueStacks either refuses to launch or runs with no GPU.

Fix it

1. Turn off the Hyper-V-related features
   In Windows Features, uncheck Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform. Also disable Core Isolation / Memory Integrity in Windows Security → Device Security, since it silently keeps the hypervisor on.
   None of the four features is enabled after a reboot.
2. Disable the Hyper-V boot flag with bcdedit
   Windows Features doesn't always clear the underlying boot flag. Run bcdedit /set hypervisorlaunchtype off from an administrator prompt. This is the step people miss — the GUI looks clean but the hypervisor still starts.
   bcdedit shows hypervisorlaunchtype Off.
3. Reboot, then reinstall or repair BlueStacks
   A reboot is required for the flag to take effect. If BlueStacks still errors, run its repair tool or reinstall — a partial install under the conflict leaves broken state.
   BlueStacks launches and the GPU is recognised in its settings.

If you need Hyper-V for something else

1. Use a Hyper-V-compatible engine, or switch per boot
   Some Android emulators offer a Hyper-V-compatible mode; BlueStacks' Nougat 64-bit Pie with the right engine can coexist. Otherwise, toggle the bcdedit flag on or off depending on whether you're emulating Android or running a VM that day.
   The task you need runs without re-installing.

Other Android-emulator launch failures

If virtualization itself is disabled in BIOS, no emulator will open — see the virtualization disabled fix. The MEmu not opening page covers the same class of problem on a different emulator.