Android Emulator issues in new versions - The emulator process has terminated

Question

After updating to Android Studio 2020.3.1 canary 15, when I try to run an emulator, it gets killed with this error:

The emulator process for AVD Pixel_4_API_30 has terminated.

It was working correctly in the previous version (4.1.3), but now after installing the new one, it shows the same error.

---

I've tried some solutions had suggested in almost similar cases; however, It still doesn't work.

1. I deleted my emulator (also I cleared inside of directory: /.android/avd/) and created a new one again
2. I updated the HAXM installer to version 7.6.5
3. I tried to run an emulator with lower APIs but...

---

Image of the error:

Answer 1

I encountered this issue after installing Android Studio. None of the solutions worked for me that are listed above. I can't open the emulator in android studio but I can open it in command prompt by navigating to emulator location. I resolved it by installing "Microsoft Visual C++ 2015 - 2022 Redistributable". After I installed this it works well.

Download from the links below. x86: https://aka.ms/vs/17/release/vc_redist.x86.exe x64: https://aka.ms/vs/17/release/vc_redist.x64.exe

Answer 2

Apparently, as of 2025 Jan, the Android Studio bumble bee is causing this issue if Intel HAXM is installed. Even if Android Emulator hypervisor driver is installed as indicated in the instructions, I'm still getting the said avd launch error.

I was able to launch the emulator, however using the command line emulator -avd "avd_name" as recommended by many others, during which this pop-up explained the real problem. I guess I will have to uninstall HAXM to be able to launch AVD from within Android studio.

Answer 3

At first you need to check the emulator path is added on evironment variable properly

C:\Users<user>\AppData\Local\Android\Sdk\emulator

This path should give inside environment variable - path

Answer 4

As a last resort, you could always try RTFM. This is what I did, and it turns out that emulators are not currently supported on ChromeOS. It's my fault of course, for not using a MacBook.

Answer 5

A common cause of that issue is lack of free space on your disk

Answer 6

The problem only because of the missing of Microsoft Visual C++ Redistributable.

I have installed using this link and problem solved.

Answer 7

To solve these type of issue, generally you haven't some file, that you need to download it from google and paste. I was facing the same issue. but after a lot of time spent on google finally I have got the solution.

Following are the steps:-

1. Create virtual device using AVD Manager
2. start the emulator
3. if it is showing your emulator has terminated
4. Then go to ("C:\Users\YourUserName\AppData\Local\Google\AndroidStudio2020.3\log\idea.log")
5. check the issue by scroll down(on bottom you can check)
6. If you are getting the same issue
7. Then go to C:\Windows\System32 directory, search here for file called vulkan-1-999-0-0-0.dll
8. If file is already in directory, then just rename the file into "vulkan-1.dll"
9. else download the file from official sources and paste the vulkan-1-999-0-0-0.dll file and perform the step 8.

Answer 8

Fix Android Emulator Process has terminated - Android Studio The emulator may require certains DLLs are not present, this can be fixed by ensuring that you have the Latest Microsoft Visual C++ Redistributable Version :

Answer 9

Simply delete the malfunctioning emulator and create a new one. That was the only solution that worked for me.

Answer 10

I've outlined the steps that fixed the issue for me 1, go to android sdk manager and installed HAXM

2, went to bios and enabled virtualization and enabled hyper-v

3, I then updated my nvidia drivers

• if you want to find which driver works for your system go here and download the drivers you need

These steps are what worked for me. hope this helps.

Answer 11

In my case, I use tools/emulator -avd my_device_name_in_avd_dir, it show err detail, following is my full log, in my case, it's because I use old linux dist with old glibc ver

to fix it:

use new glibc version (upgrade glibc or use latest linux dist)

or use old android emulator https://developer.android.com/studio/emulator_archive, use old emulator replace ~/Android/Sdk/emulator and use old-emulator/emulator -avd device_name

~/Android/Sdk $ ls -al ~/.android/avd/
total 24
drwxrwxr-x 4 roroco i 4096 Nov  4 17:13 .
drwxrwxr-x 7 roroco i 4096 Sep 21  2023 ..
drwxr-xr-x 2 roroco i 4096 Nov  4 17:13 Pixel_6_API_29_2.avd
-rw-r--r-- 1 roroco i  127 Nov  4 17:13 Pixel_6_API_29_2.ini
drwxr-xr-x 2 roroco i 4096 Nov  4 16:54 Pixel_6_API_29.avd
-rw-r--r-- 1 roroco i  123 Nov  4 16:54 Pixel_6_API_29.ini
~/Android/Sdk $ /home/roroco/Android/Sdk/tools/emulator -avd Pixel_6_API_29
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_2.30' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6WebEngineCoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6WebEngineCoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6WebEngineCoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6WidgetsAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6CoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_2.30' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6CoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6CoreAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6GuiAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6QmlAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6PositioningAndroidEmu.so.6)
/home/roroco/Android/Sdk/emulator/qemu/linux-x86_64/qemu-system-aarch64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/roroco/Android/Sdk/emulator/lib64/qt/lib/libQt6QuickAndroidEmu.so.6)

Answer 12

Try finding the root cause of the problem using logs at:

C:\Users\YourUserName\AppData\Local\Google\AndroidStudio2020.3\log\idea.log

I verified my logs and found issue was in:

C:\Android\android-sdk\system-images\android-35\google_apis_playstore\x86_64\ is not a valid directory.
PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT

these errors were coming. I tried adding ANDROID_SDK_ROOT in environmental variables and not worked for me. Then, verified SDK location and found the following path:

C:\Users\YourUserName\AppData\Local\Android\Sdk\system-images\android-35\google_apis_playstore\x86_64

Copied this path.

1. went to C:\Users\YourUserName.android\avd folder.
2. Open the folder of your emulator
3. find the file called config.ini and search for 'image.sysdir.1'
4. Replace the path with copied path.

Emulator should work, small suggestion is to create a virtual device with more space than available by default. Also, please do restart the android studio.

Answer 13

After trying a few options, adding emulator's folder to system variables is what worked for me. Folder was at C:\Users\Username\AppData\Local\Android\Sdk\emulator.

After adding to path, run emulator from cmd with emulator -avd name-of-emulator

Answer 14

I encountered this issue after updating Android Studio to version 2024.1.2. None of the solutions worked for me. I tried uninstalling Android Studio and completely deleting all the related files before installing a fresh version. The emulator wasn't working for me either from Android Studio or VS Code (Flutter); it was giving me the error code -1073741515. if I started the emulator from the terminal using these commands:

cd C:\Users\<Your_Username>\AppData\Local\Android\Sdk\emulator
.\emulator.exe -avd Pixel_4a_API_34 -verbose

the emulator worked without any issue. So, what I did was add an environment path for the emulator:

path: C:\Users\<Your_Username>\AppData\Local\Android\Sdk\emulator

After adding the path, I was able to successfully start the emulator from both Android Studio and Flutter.

Answer 15

Android studio automatically updated its version, and made this issue. So, I am going to disable "auto updating" function.

Answer 16

I had the same problem with Windows 11, Android 2024.1.1 API 35 what I did is to

i. enable hyper-v as others suggested,

ii. tracing the log from the path

C:\Users\YourUserName\AppData\Local\Google\AndroidStudio2024.1.1\log\idea.log" as others suggested

iii. Clearing the content of idea.log to make it plain .. reboot the OS then everything works fine

Answer 17

I changed the the device to Medium Phone API 32, it works. Although the emulator is slow and laggy.

Answer 18

The trick for me the version compatibility between :-

1-android studio

2-platform-tools

3-Emulator

after upgrading android studio every thing went wrong, adb stopped working, emulator stopped working.

solved the problem by:

1- downgrading platform-tools to version 34.0.0. can be downloaded from here

2- downgrading emulator version to 34.1.1, can be downloaded from here

Answer 19

In my case the log has this line right before termination:

2024-07-22 10:25:58,295 [  27889]   WARN - Emulator: Pixel 3a API 34 - It seems too many emulator instances are running on this machine. Aborting.

Then in Windows command line do this works for me:

net stop winnat

It is always better to check the log to find out the cause. Althought above message is not clear.

Answer 20

I've just got this message after update of Android Studio to 2023.2.1 Patch 2.

As a temporary workaround, I can still run an emulator by the command line on Windows 10

cd C:\Users\YOUR_USER\AppData\Local\Android\Sdk\emulator
emulator -list-avds
emulator -avd Pixel_6_API_26

Answer 21

Open the directory in which os is installed. Then Users > <YOUR_USERNAME> >.android/avd/<AVD_NAME>.avd/

Delete all files ending .lock extension

Answer 22

Win7 x64 + Android Studio 2023.1: killing process tree for qemu-system helped. This one left in the process list even after IDE closed.

Answer 23

I tried all the methods described here, but it did not help to fix the error.

I installed the emulator manually. I used the emulator from the official resource developer.android.com.

I chose an emulator with a date that roughly corresponded to the version of Android Studio. I did everything as written in the instructions.

My Android Studio 2022.1.1

Chose Emulator 32.1.12

For example video youtube video

Answer 24

Lake of disk space in my hard drive was the root cause. Make sure that the amount of free space in your hard drive is greater than the amount of internal storage of your Virtual Device.

https://developer.android.com/studio/run/emulator-troubleshooting#disk-space

Answer 25

I resolved this issue by wiping the user data of emulator. Simply go to Device Manager then click on the device menu and Wipe Data, and then again run the app on that emulator.

Answer 26

Try to kill the emulator process and then you can reboot the emulator.

On Windows, bring out Task Manager and find the emulator process (you can find it starts with qemu-xxx, it might be wrapped inside Android Studio or IntelliJ IDEA category), then click end task to kill the process.

Answer 27

Delete other unused devices which are using disk space and free them up.

Answer 28

I tryied all possiblilities,Just Make 6-7 gb space on drive worked for me.If you don't have enough space on disk might cause this issue too.

Answer 29

I solved my problem with kill adb and start again it:

go to adb.exe in => C:\Users\simab-lenovo\AppData\Local\Android\Android\Sdk\platform-tools , and start cmd and write below command adb kill-server adb start-server

Answer 30

Please check if you have Windows Media Pack installed, this is required to run emulator, it's not documented and not may users notice, I have Windows 11 Enterprise N which is the N variant that does come without Media Pack and emulator didn't work until I installed it.

Apps > Optional Features > Add feature > Windows Media Pack

Please post the system type and version from now on.