How to Install and Set Up an Android Emulator on Windows 11

Google’s Android Emulator is a supported option for Android development on Windows 11. Set up the IDE, SDK components, system image, and acceleration path separately; an AVD is a device configuration, not a package containing every Android image.

Check the Host Requirements

Google currently lists at least 16 GB RAM for Android Studio plus Emulator on Windows, with 32 GB recommended. Its Windows requirements also specify compatible x64 hardware and graphics; Windows on Arm is not currently supported by that Studio installation guidance. Check the current installation requirements before downloading.

If the host has limited resources, consider testing on a supported physical Android device instead of allocating most of Windows’ memory to a virtual device. Larger projects and multiple emulators need more capacity than a minimum setup.

Install Android Studio and SDK Components

Download from Android Developers. Run the installer and setup wizard, then use SDK Manager for the required Android SDK platform, platform tools, Android Emulator, and system images. Missing components can be installed later without reinstalling the whole IDE.

Use a stable emulator release appropriate to your project. The installer’s optional AVD component does not mean every phone profile or Android version is already downloaded.

Configure Current Windows Acceleration

On supported x64 Windows hosts, Google recommends Windows Hypervisor Platform (WHPX). Enable Intel VT-x or AMD virtualization/SVM in the computer’s firmware if needed, then enable Windows Hypervisor Platform in Turn Windows features on or off and restart as directed. Follow the exact model’s firmware instructions rather than changing unrelated security or storage options.

HAXM is deprecated and no longer used by emulator 36.2 and later. The alternative Android Emulator hypervisor driver (AEHD) is scheduled to sunset on December 31, 2026. Do not disable Hyper-V to chase HAXM performance. Google’s acceleration guide explains the supported path and the emulator -accel-check diagnostic.

Task Manager > Performance > CPU can indicate firmware virtualization status, but Enabled alone does not verify that the emulator has a usable hypervisor. Record the actual acceleration-check result if startup fails.

Create a Device in Device Manager

Open Tools > Device Manager in Android Studio, or the virtual-device option under More Actions on the welcome screen. Older versions called this AVD Manager.

Choose a profile and API level matching your testing needs, then download a supported system image. Google APIs images provide Google Play services; a Google Play-marked device/image provides the Play Store app as well. These labels are not interchangeable. The API level must meet the app’s minimum requirement, and its native libraries must support the image’s ABI.

Finish the configuration and launch it. See Google’s AVD and system-image guide. A Pixel hardware profile does not reproduce every manufacturer’s firmware or physical hardware behavior.

Tune From a Measured Workload

Begin with the supported defaults and Automatic graphics mode. If a particular rendering problem appears, compare the current hardware and software graphics options, checking host GPU-driver compatibility. Old labels such as “Hardware - GLES 2.0” are not universal current choices.

Do not assume more RAM or more virtual CPUs always improves performance. Keep capacity for Windows, the IDE, and builds, and compare the same workload before and after a change. For more detail, see emulator performance tuning.

Install and Test Your App

Use Android Studio’s Run action for your project. A compatible APK can also be installed with adb install followed by its actual file path, or by dropping it onto the emulator where supported. Play Store installation requires an appropriate Play image and account access.

Not every app works in an emulator: API/ABI mismatches, service dependencies, integrity checks, or hardware requirements can restrict it. Test on physical devices too. A successful app launch is not complete compatibility coverage.

Verify the Setup and Diagnose Failures

Check that the emulator reaches a usable state, the app installs and behaves correctly, and orientation or supported simulated inputs match your tests. There is no universal requirement to boot in under 60 seconds; cold boots, image changes, and snapshots differ.

For failures, save the exact error, emulator version, image/API/ABI, hypervisor result, and host resource use. Check one layer at a time rather than reinstalling repeatedly or assuming every problem is firmware virtualization. See the emulator troubleshooting guide for symptom-specific checks.

Snapshots can speed later sessions, but do not replace a reproducible clean test. Use the emulator’s extended controls for supported simulated location or network conditions, and validate hardware-specific results on real devices.