---
title: "Android emulator won't start — \\"Virtualization (VT-x/SVM) is disabled\\""
canonical_url: https://emudesk.com/issues/emulator-virtualization-disabled-vt-x-svm-fix
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.582Z
freshness_status: fresh
---

# Android emulator won't start — \"Virtualization (VT-x/SVM) is disabled\"

The "virtualization is disabled" warning means VT-x (Intel) or SVM (AMD) is turned off in your PC's BIOS, so the emulator can't use hardware acceleration and either refuses to boot or limps along at 1–2 FPS. The fix is two steps in order: enable the virtualization setting in BIOS/UEFI, then make sure a Windows feature (Hyper-V / Memory Integrity) isn't grabbing it back. The BIOS steps below are grouped by laptop brand.

You install GameLoop, BlueStacks, LDPlayer or MEmu, and instead of the game you get a warning that virtualization is disabled — worded as "VT-x is not enabled", "Enable Virtual Technology (VT)", "AMD-V / SVM is disabled", or a yellow banner telling you to turn on virtualization for better performance. Either the emulator refuses to boot, or it limps along at 1–2 FPS and games are unplayable.

Cause: Android emulators run a real virtual machine. To do that with acceptable speed they need your CPU's hardware virtualization extension — Intel VT-x (often shown as Intel Virtualization Technology or VMX) or AMD SVM (AMD-V). On most laptops and many prebuilt PCs this extension ships turned off in the BIOS/UEFI by default. Without it, the emulator either can't create the VM at all, or falls back to slow software emulation.

There are two distinct reasons the warning appears, and they need different fixes: (1) virtualization is genuinely off in BIOS, or (2) it's on in BIOS but Windows itself is holding it — Hyper-V, the Virtual Machine Platform, Core Isolation/Memory Integrity, or Credential Guard can claim the virtualization layer so no third-party emulator can use it. The fixes below cover both, in order.

This is a one-time hardware/OS setting, not a corrupt install. Reinstalling the emulator, switching game versions, or updating drivers will not fix it — the VM can't start before any of that matters.