Development of mobile applications for Android is inextricably linked with regular testing of code on virtual devices. However, many developers, from beginners to professionals, periodically encounter a scary error message Android Studio could not start AVD. This problem completely paralyzes the work process, since without running the emulator it is impossible to check the layout, application logic or performance on different hardware configurations.
The reasons for the failure can be very diverse: from a simple lack of RAM to conflicts in virtualization technologies in the operating system kernel. Often the situation is aggravated by the fact that the error message in the console looks like a bunch of incomprehensible codes or general phrases that do not directly indicate the source of the problem. In this article, we will analyze in detail all possible failure scenarios and offer proven methods for restoring functionality Android Virtual Device.
Diagnostics of the primary causes of emulator failure
Before proceeding with complex manipulations with system settings, it is necessary to carry out basic diagnostics. Most often, the error Android Studio could not start AVD occurs because the system image is damaged or incompatible with the current version of the emulator. Check whether the system image has been fully loaded and whether its download has not been interrupted previously.
Pay attention to the logs that it produces Event Log at the bottom of the studio window. There is often a clue hidden there. If you see a mention of missing system images or corrupt files, the solution is to reinstall the image via SDK Manager. Delete the old image and download it again, making sure that the selected API version meets the requirements of your project.
It is also worth checking the settings of the virtual device itself. Sometimes users accidentally change graphics or memory settings, making it impossible to launch. Try creating a completely new AVD with minimal settings to understand whether the problem lies in a specific device profile or in the global configuration of the development environment.
Virtualization technology conflicts: HAXM, Hyper-V and WHPX
The most common and complex reason, why Android Studio the emulator cannot run is a conflict between different virtualization technologies. This is especially true on computers running Windows. Historically, the Android emulator used Intel HAXM for acceleration, but modern versions of Windows actively use the built-in Hyper-V.
These two technologies cannot run simultaneously on the same processor core. If you have Hyper-V enabled (which often happens automatically after installing Docker or WSL 2), then HAXM simply will not be able to initialize the drivers. As a result, you will receive an error stating that the virtual machine cannot be started. The solution is to either disable Hyper-V completely or switch the emulator to use Windows Hypervisor Platform (WHPX).
⚠️ Warning: Disabling Hyper-V may affect the operation of other applications such as Docker Desktop or VirtualBox virtual machines. Make sure you really don't need these services before changing kernel settings.
To switch to WHPX you need to go to Windows components and make sure the checkbox is checked Windows hypervisor platform. After that, in the emulator settings in Android Studio, you should select a graphics mode that is compatible with WHPX. If you use AMD processors, then using Intel HAXM is impossible in principle, and it is critical for you to configure the correct work with the native virtualization tools of your OS.
How to check whether virtualization is enabled in the BIOS?
Go to BIOS/UEFI at boot computer (usually the Del or F2 key). Find the Advanced or CPU Configuration section. Make sure that Intel Virtualization Technology (VT-x) or AMD-V is set to Enabled. Without this, not a single emulator will start.
Problems with paths to the SDK and environment variables
Sometimes the problem is prosaic in nature and is related to paths to files. Android Studio is sensitive to the presence of Cyrillic characters or spaces in the directory path Android SDK. If your Windows user has a name in Russian, the path may look like C:\Users\Ivan\Android\Sdk, which often causes failures in the emulator's native libraries.
In such a situation, it is recommended to move the SDK to the root of the disk, for example, to C:\Android\Sdk, and update the path in the studio settings through the menu File → Settings → Appearance & Behavior → System Settings → Android SDK. After moving the files, you should also check the system environment variables.
- 🔍 Make sure that the variable
ANDROID_HOMEpoints to the new folder. - 🔍 Check that the path to
platform-toolshas been added to the system variablePath. - 🔍 Restart Android Studio after making changes to the environment variables.
Incorrect SDK folder permissions can also block the creation of temporary files needed to run the AVD. Try running Android Studio as administrator. If this helps, then the problem is in file system access rights, and it is worth checking the properties of the SDK folder by removing the “Read-Only” attribute for all subdirectories.
Setting up graphics acceleration and rendering mode
The emulator's graphics subsystem is another common source of errors. By default, Android Studio tries to use hardware acceleration through your graphics card. However, video card drivers may be incompatible with the current version of the emulator, especially if you are using older GPU models or specific driver versions.
In the virtual device settings (pencil button in AVD Manager), find the section Emulated Performance. Try changing the parameter Graphics. The value Automatic does not always work correctly. Switch it to Software - GLES 2.0. This will force the emulator to use the processor to render graphics, which will significantly reduce performance, but will allow the device to run for debugging logic.
| Graphics mode | Performance | Stability | Recommendation |
|---|---|---|---|
| Hardware - GLES 2.0 | High | Medium | For powerful PCs with fresh drivers |
| Software - GLES 2.0 | Low | High | For old PCs or with startup errors |
| Automatic | Depends on the system | Unstable | Use with caution |
If switching to software graphics helped the emulator run, try gradually updating your video card drivers to return to hardware acceleration in the future.
Clearing the cache and resetting the emulator state
Over time, emulator snapshot files (snapshots) may become damaged. If you are used to using the Quick Bootfunction, which allows you to instantly load the saved state of the device, then this file may be the culprit of the "Could not start AVD" error. The emulator tries to load a broken memory file and immediately exits.
To fix this, you need to perform a cold boot. In the AVD Manager window, click on the down arrow next to the Play button and select Cold Boot Now. This will force the system to ignore the saved snapshot and boot from scratch, as when you first turned on the phone. If this does not help, you can delete the user data completely.
For a radical solution, open the folder with the emulator data. Usually it is located along the C:\Users\YourUser\.android\avdpath. Find the folder with the name of your device and delete the file with the extension .ini or the folder snapshots inside it. This will delete all installed applications and data inside the emulator, but will return it to functionality.
☑️ Checklist for cleaning the emulator
Lack of resources and memory allocation settings
Modern Android images, especially versions 11, 12 and higher, require significant resources. A startup error may occur simply because the emulator does not have enough RAM or disk space. By default, the studio may allocate too little RAM for heavy system images.
Go to the AVD settings and increase the amount of memory. However, you should not allocate more than 50% of the total available RAM on your computer, otherwise the main operating system will start using the page file, which will lead to severe slowdowns. Also check the free disk space: for the emulator to work, it requires not only space for the image, but also a significant reserve for the swap file of the emulator itself.
⚠️ Attention: Android Studio interfaces and emulator versions are regularly updated. The location of memory settings or menu item names may differ in new software versions. Always check Google's official documentation if the interface seems to have changed.
If you have less than 8 GB of RAM, using heavy images with Google Play Services may not be possible. In this case, try downloading system images like x86 Images without pre-installed Google services. They weigh less and require fewer resources to start, which often helps to bypass the error on weak machines.
The optimal balance between performance and stability is achieved by allocating 2-4 GB of RAM for the emulator and using an SSD drive to store image files.
Solving problems with network settings and proxies
On corporate networks or when using specific Internet settings, the emulator may not start due to the inability to check the license or download the necessary components at startup. Although this is less common than problems with virtualization, this scenario should be ruled out.
Check your proxy settings in Android Studio itself. Go to Settings → Appearance & Behavior → System Settings → HTTP Proxy. If you are using a proxy, make sure the information you entered is correct. Sometimes setting the mode helps No proxyif you work from home to avoid conflicting settings.
You should also pay attention to the Windows firewall or antivirus software. They can block the network activity of the process qemu-system-x86_64.exewhich is the kernel of the emulator. Add an exception for the Android SDK folder and the emulator process itself in the settings of your security software.
Frequently asked questions (FAQ)
Why does the emulator crash immediately after the Android logo appears?
Most often this indicates a conflict in graphics drivers or insufficient video memory. Try switching the rendering mode to Software in the AVD settings or updating your video card drivers to the latest version.
Is it possible to run AVD without virtualization enabled in the BIOS?
Technically, this is possible in pure processor emulation mode, but the operating speed will be extremely low (one frame every few seconds). For normal development, virtualization (VT-x or AMD-V) is required.
Which version of Android works best on an emulator?
Usually Android 10 and 11 images show the best balance between stability and performance. The newest versions may contain emulation bugs, and the older ones may not support the necessary APIs.
How to reset the emulator to factory settings?
In the AVD Manager, click on the three dots next to the device and select Wipe Data. This will delete all user data and return the device to its original state.
Error "Emulator: ERROR: x86 emulation currently requires hardware acceleration." What to do?
This is a direct indication that virtualization is disabled in the BIOS or blocked by other software (for example, Hyper-V). Check the BIOS settings and make sure that VT-x is enabled and conflicting hypervisors are disabled.