Solving Android Emulator Execution Error: Enabling Windows Hypervisor Platform

Problem Scenario

  • Symptoms: Android Emulator terminates with code 1 immediately after starting.
  • Error: Exits after netsimd (Network Simulator Daemon) execution.
  • Environment: Windows 11 Pro, Hyper-V enabled.

Solution

POWERSHELL
# 1. Check current status (Administrator PowerShell)
Get-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform

# 2. Enable Windows Hypervisor Platform
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All

# 3. Reboot
Restart-Computer

Why is this setting required?

Relationship between Hyper-V and Android Emulator

  1. When Hyper-V is enabled, Windows itself runs on a Type-1 hypervisor, so other hypervisor drivers (AEHD, formerly Intel HAXM) can't run alongside it.
  2. In that case, the Android Emulator gets acceleration through WHPX (Windows Hypervisor Platform).
  3. So if Hyper-V is on but Windows Hypervisor Platform is off, the emulator has no acceleration method it can use.

Role of Windows Hypervisor Platform

  • An API that exposes Hyper-V virtualization features to third-party applications.
  • Tools such as the Android Emulator, VMware Workstation, and VirtualBox use it for virtualization when Hyper-V is on.

When should you apply this setting?

When it's needed

When Hyper-V is already enabled

  • Using WSL2, Docker Desktop, etc., on Windows 11 Pro/Enterprise.
  • Development environments where Hyper-V cannot be disabled.

When the Android Emulator fails with these symptoms:

  • netsimd related errors.
  • "emulator exited with code 1".
  • Hyper-V related warning messages.

When it's not needed

When Hyper-V is disabled

  • AEHD (Android Emulator Hypervisor Driver) can also provide acceleration. Intel HAXM support ended in emulator 33.x and was replaced by AEHD.
  • Windows 10 Home edition (Hyper-V not supported).

When the emulator is working normally

  • No need to change settings.

Key Point: To use the Android Emulator while Hyper-V is on, you also need to enable the Windows Hypervisor Platform.