Skip to content

Android Studio Emulator HAXM Error Fix

DodaTech Updated 2026-06-24 4 min read

In this tutorial, you'll learn about Android Studio Emulator HAXM Error Fix. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Your Android Studio emulator fails to start with HAXM is not installed, VT-x is disabled, or Emulator: Process finished with exit code 1 — the emulator cannot use hardware acceleration because virtualization is disabled or the HAXM driver is not installed.

Step-by-Step Fix

1. Check virtualization status

# On Linux: check if virtualization is enabled
grep -E '(vmx|svm)' /proc/cpuinfo

# On macOS:
sysctl -a | grep -E '(vmx|avx)'

# On Windows (PowerShell as Admin):
systeminfo | findstr "Virtualization"

Expected output:

flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves arat avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq

If vmx (Intel) or svm (AMD) is not present, virtualization is disabled in BIOS.

2. Enable virtualization in BIOS

# Reboot and enter BIOS/UEFI:
# - Press F2, F10, Del, or Esc during boot (varies by manufacturer)

# Look for:
# Intel: "Intel Virtualization Technology" (VT-x) > Enable
# AMD: "SVM Mode" > Enable

# Also enable:
# "Intel VT-d" > Enable
# "Execute Disable Bit" > Enable

# Save and reboot

3. Install or reinstall HAXM

# Install via Android Studio:
# Tools > SDK Manager > SDK Tools > Intel x86 Emulator Accelerator (HAXM installer)

# Or download from Intel and install manually
# On Linux:
sudo dpkg -i haxm-linux-*.deb

# On macOS:
sudo /usr/local/android-sdk/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh

# On Windows:
# Run: /path/to/sdk/extras/intel/Hardware_Accelerated_Execution_Manager/intelhaxm-android.exe

4. Use Windows Hyper-V instead of HAXM

# Windows: use Hyper-V as an alternative to HAXM
# 1. Enable Windows Hyper-V Platform
# PowerShell as Admin:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

# 2. Configure Android Studio to use Hyper-V
# In Android Studio: File > Settings > Appearance & Behavior > System Settings > Android SDK
# Enable "Use Hyper-V for x86 Emulators"

5. Use ARM-based emulator image

# If HAXM is not available, use an ARM emulator image:
# In Android Studio Device Manager:
# Create Device > Select a system image > Choose "ARM64" variant

# ARM images work without HAXM but are slower than x86 with HAXM

# For Apple Silicon Macs:
# Use the ARM64 emulator image (no HAXM needed)

6. Fix HAXM memory allocation

# HAXM may fail if there isn't enough contiguous memory

# On Windows, reduce HAXM memory in the HAXM installer
# Run the installer and set memory to 1024 MB or 512 MB

# Or configure it via command line:
# /path/to/sdk/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.exe -m 1024

7. Verify HAXM installation

# Check if HAXM kernel module is loaded
lsmod | grep kvm

# Check HAXM status
# On Windows:
sc query intelhaxm

# On Linux:
sudo modprobe kvm
sudo modprobe kvm_intel

Prevention

  • Check BIOS virtualization settings when setting up a new development machine.
  • Keep HAXM updated via Android Studio's SDK Manager.
  • Use ARM emulator images on Apple Silicon Macs (no HAXM needed).
  • Allocate at least 2 GB of RAM for the emulator.
  • Close other virtualization software (VirtualBox, Docker) when running the emulator.

Common Mistakes with studio emulator

  1. Non-exhaustive pattern matches that compile with warnings then crash at runtime
  2. Misunderstanding that String is [Char] with poor performance for large text operations
  3. Using foldl instead of foldl' causing stack overflow on large lists

These mistakes appear frequently in real-world Android code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

What is HAXM and why does the emulator need it?

HAXM (Hardware Accelerated Execution Manager) is Intel's virtualization engine that accelerates Android emulator performance by 10-50x. It requires VT-x support in your CPU and BIOS. |||Can I run the emulator without HAXM? Yes, but it will be extremely slow (software rendering). On modern systems, use the ARM emulator image or enable Hyper-V on Windows as alternatives to HAXM. |||Why does HAXM fail to install on Windows? Common causes: Hyper-V is enabled (conflicts with HAXM), virtualization is disabled in BIOS, or Windows Defender is blocking the driver. Disable Hyper-V, enable VT-x, and temporarily disable Windows Defender.

← Previous SharedPreferences — Complete Guide Next → Android View Binding — Complete Guide

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro

Home Browse Quick Fix