The situation when, after a long preparation of a project and writing code emulator in Android Studio simply refuses to start, is familiar to every developer. You press the Run button, see the “Waiting for target device to come online” process, and then either silence occurs or an error occurs with code -1073741819. This can be caused by a dozen reasons: from disabled virtualization in the BIOS to a conflict in antivirus software or lack of RAM.
Most often, the problem lies not in the application code itself, but in the environment configuration or system limitations. Android Virtual Device (AVD) requires certain resources and permissions that may not be activated on your computer by default. It is important not to panic and consistently check the settings, since most errors are corrected in a few minutes.
In this article we will analyze in detail all possible failure scenarios. We'll cover both software conflicts and hardware requirements so you can get your development tool back up and running. Understanding the architecture of the emulator will help you avoid similar problems in the future.
Checking virtualization support in BIOS/UEFI
The most common reason why the emulator does not start is disabled hardware virtualization on the motherboard. Modern emulators use Intel VT-x or AMD-V technologies for acceleration, and without their active status in the BIOS, launch virtual device is impossible. If this feature is disabled, the emulator may either not start at all or run in extremely slow software emulation mode.
To check the status, open the Task Manager in Windows (Ctrl+Shift+Esc), go to the "Performance" tab and select "CPU". On the right side of the screen, find the “Virtualization” line. If it says Disabled, you need to restart your computer and enter the BIOS/UEFI. There you need to find the corresponding item (often called Intel Virtualization Technology, VT-x, SVM Mode) and switch it to the state Enabled.
After enabling virtualization in the BIOS, be sure to completely reboot the computer (switch off and on), and not just restart the system, so that the changes are guaranteed to be applied.
Sometimes antivirus software or other hypervisors can block access to these functions, even if they are enabled in the BIOS. Make sure that you do not have VirtualBox or VMware running in parallel with conflicting settings that can intercept control of VT-x.
Conflicts with Hyper-V and other hypervisors
In the Windows environment, there is often a conflict between Microsoft's own hypervisor Hyper-V and the Android Studio emulator, which traditionally used HAXM (Hardware Accelerated Execution Manager). Although modern versions of the emulator have learned to work through the Windows Hypervisor Platform (WHPX), old configurations or specific settings may cause crashes. If the emulator throws an error about the inability to run x86_64 image, this is almost certainly the problem.
To solve the problem, you can try enabling the WHPX platform. To do this, go to Control Panel → apps and Features → Turn Windows features on or off. Here you need to activate the checkboxes opposite “Hyper-V”, “Virtual machine platform” and “Windows hypervisor platform”. After this, a reboot will be required.
⚠️ Attention: If you are using Docker Desktop or VirtualBox in parallel with Android Studio, enabling Hyper-V may break the operation of these apps. In such cases, it is recommended to use an emulator with compatibility mode or disable Hyper-V if it is not critical for other tasks.
It is also worth checking whether a firewall or antivirus is blocking the process qemu-system-x86_64.exe. Sometimes adding exclusions for the entire SDK folder helps solve the problem instantly.
How to completely disable Hyper-V via the command line
If the GUI does not help, open a command prompt as an administrator and enter the command: bcdedit /set hypervisorlaunchtype off. After running the command, be sure to restart your computer. To return the functionality, use the command: bcdedit /set hypervisorlaunchtype auto.
Lack of system resources and AVD settings
The Android emulator is a full-fledged operating system that runs inside your OS, so it is extremely resource-intensive. If you have low RAM installed (less than 8 GB for comfortable work) or a weak processor, the emulator may simply not start due to a lack of allocated RAM. In the logs, this is often reflected as a sudden termination of the process without obvious errors.
Open AVD Manager in Android Studio, click on the gear icon (Settings) next to your device and select “Edit”. In the configuration window, find the “Memory and Storage” item. Try reducing the RAM value to, for example, 2048 MB or even 1536 MB if the system is unstable.
It is also critical to pay attention to the GPU. In the emulator settings there is a parameter “Emulated Performance” → “Graphics”. By default there is “Automatic”, but often manual setting of the value Software - GLES 2.0 (for weak PCs) or Hardware - GLES 2.0/3.0 (for powerful PCs) solves the problem of a black screen or crashes.
Below is a table of recommended settings depending on the configuration of your computer:
| PC configuration | RAM for emulator | Graphics | Storage mode |
|---|---|---|---|
| Weak (4-8 GB RAM) | 1024 - 1536 MB | Software - GLES 2.0 | Store in memory |
| Medium (8-16 GB RAM) | 2048 - 3072 MB | Hardware - GLES 2.0 | Default |
| Powerful (16+ GB RAM) | 4096+ MB | Hardware - GLES 3.0/Angle | Default |
Problems with paths and access rights (SDK Location)
One of the hidden but common causes of failures is the incorrect location of SDK files or the presence of Cyrillic characters and spaces in the folder path. Android Studio and command line tools may incorrectly process paths containing Russian letters or special characters. For example, the path C:\Users\Name\Android\Sdk often causes errors in loading system images.
It is recommended to move the SDK to the root of the disk or a folder with a simple Latin name, for example, C:\Android\Sdk. After moving, you need to specify a new path in the settings of the studio itself: Tools → SDK Manager → Android SDK Location. Also check the system environment variables if you are using adb from the terminal.
☑️ Checking paths and access rights
In addition, make sure that the antivirus does not quarantine the emulator files. Sometimes, when updating components, an antivirus may consider the emulator executable file suspicious and block its launch without notifying the user.
HAXM / WHPX installation and version errors
The Intel HAXM (Hardware Accelerated Execution Manager) acceleration component often installs incorrectly or conflicts with the current version of Android Studio. If you see errors related to haxmin the logs, try reinstalling this component via SDK Manager. Go to Tools → SDK Manager → SDK Tools, uncheck "Intel x86 Emulator Accelerator (HAXM installer)", apply the changes, and then install it again.
It is important to note that for AMD processors or newer Windows 10/11 systems, it is preferable to use Windows Hypervisor Platform instead of HAXM. In this case, in SDK Tools you need to select “Android Emulator” and “Windows Hypervisor Platform”, and HAXM can be ignored.
⚠️ Attention: The SDK Manager interface and available components may change with Android Studio updates. If you don't find a component, check the official documentation for your version of the IDE, as some tools may have been deprecated or renamed.
It's also worth checking to see if you have an outdated version of the emulator. In the SDK Manager, in the “Updates” tab, patches are often available that fix critical launch bugs on new versions of Windows.
Alternative solutions and physical device
If no methods help to launch the emulator, and you need to write code urgently, the best solution is to use a physical device. Connect your smartphone or tablet via USB, turn it on USB debugging (in the “For Developers” menu) and run the project. This will not only bypass the problem, but will also give a more accurate idea of the application's performance in real conditions.
Use a high-quality cable to connect and make sure that the ADB drivers are installed correctly. At the command line, enter adb devices —if you see the device serial number, the connection is established and you can run the application.
Using a real device for debugging is often faster and more stable than an emulator, especially when testing the camera, GPS and motion sensors.
As a last resort, you can try to create an emulator based on a system image without Google Play Services (marked as “x86” without the Play logo), they often weigh less and launch more readily, although they lack some service functions.
Frequently asked questions (FAQ)
Why the emulator starts but shows black screen?
A black screen most often indicates a problem with graphics rendering. Try changing the Graphics parameter in the AVD settings to “Software” or “Hardware - GLES 2.0”. Also, the problem may be incompatibility of video card drivers, which should be updated.
Is it possible to run the Android Studio emulator on a Mac with an M1/M2 processor?
Yes, but you need to download system images marked “ARM64” or “M1”. x86 emulators on such processors work via translation and may be unstable. Make sure you have the latest version of Android Studio and Android Emulator installed.
How to increase the speed of the emulator?
To speed up, be sure to enable virtualization in the BIOS, use an SSD drive to store the system image and allocate a sufficient number of processor cores (2-4 cores) to the emulator in the device settings.
Where can I find the error logs if the emulator does not start?
The logs can be found in the user folder: .android/avd/[Name_of_Your_Device].avd/. Look for files emulator.log or stderr.logwhere the reason for resetting the process will be described.