BlueStacks Hyper-V error code
The hyper_v_enabled error code means Windows kept Hyper-V on. Disable Hyper-V and Core Isolation, then restart BlueStacks.
What the code means
hyper_v_enabled is not a BlueStacks bug. It is BlueStacks telling you that a Windows hypervisor already owns the CPU’s virtualisation extensions, so BlueStacks cannot start its own Android VM on top.
Windows can hold that layer through several features at once, which is why turning off one and rebooting often changes the code instead of fixing it:
- Hyper-V (the Windows feature itself)
- Virtual Machine Platform and Windows Hypervisor Platform
- Windows Sandbox and WSL2
- Core Isolation → Memory Integrity
- Windows Subsystem for Android, if it was ever installed
Turn the competing layer off
- Press Start, type Turn Windows features on or off, open it.
- Clear Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform.
- Open Windows Security → Device Security → Core Isolation details and switch Memory integrity off.
- Restart fully — sign-out is not enough, the hypervisor only releases on reboot.
- Launch BlueStacks again. It should pick a fresh Android image.
If you actually need Hyper-V
Developers running Docker Desktop, WSL2, or Android Studio cannot just delete Hyper-V. In that case install the BlueStacks 5 Android Pie or Nougat 64-bit instance, which can share the hypervisor, or keep Hyper-V off and run those tools inside a VM instead. Trying to keep both and forcing BlueStacks usually ends with the same code after a driver update.
Related codes on the same screen
| Code | What it points at |
|---|---|
virtualization_disabled | VT-x / AMD-V switched off in BIOS |
hyper_v_enabled | A Windows hypervisor feature is holding the layer |
glibc / graphics errors | GPU driver too old for the chosen renderer |
For the BIOS side of the same family of failures, see virtualization disabled in BIOS.