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.

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

Image of the error:

Can you also add what OS you are using? I have just tried it on MacOS Big Sur 11.3 and it worked. Maybe "Invalidate Caches / Restart" would help. — Efe Budak, May 01 '21 at 22:47
Not having enough disk space could give the same error message. Best way to find the correct cause is to look into log file at "C:\Users\\AppData\Local\Google\AndroidStudio2020.3\log" — Deshan, Jan 26 '22 at 17:00
Also, if you just installed Android SDK Studio, rebooting your machine might help, this fixed the issue for me ^^' — kaiya, May 03 '22 at 09:49
Related: https://stackoverflow.com/questions/17024538/how-do-i-fix-failed-to-sync-vcpu-reg-error — gaborous, Dec 25 '22 at 03:02
My C drive did not have free space to run the emulator I freed up some space on the C drive — Esmaeil Ahmadipour, Feb 27 '23 at 09:30
Android Studio Electric Eel | 2022.1.1 Patch 2: the only solution in my case is sign out Windows profile and then go back. I hate this — Konstantin Konopko, May 30 '23 at 16:20
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 — alibttb, Jul 02 '23 at 18:20

score 361 · Answer 1 · answered Aug 06 '21 at 14:09

361

The main root cause of that issue is lack of free space on your disk

answered Aug 06 '21 at 14:09

Anatolii Shuba

4,614
1
16
17

8

Do you know how much space do you need to run the emulator? I have 7 GB Free Space and it doesn't work – Mauro Stancato Nov 19 '21 at 19:27
2

It depends on emulator type. Several are below from my setup (x86_64): Pixel_5_API_31 - 3.6GB, Nexus_7_API_28 - 2.4GB, Nexus_4_API_22 - 5.5GB, Nexus_5X_API_26 - 5.2GB, Nexus_5X_API_28 - 2.7GB, Pixel_API_21 - 5.6GB – Anatolii Shuba Nov 20 '21 at 21:00
5

@MauroStancato Failed to work with 1.2GB, worked with 6GB, took 100 MB of space on running. ¯\\_(ツ)_/¯ – reducing activity Feb 03 '22 at 18:28
@AnsalAli Lack of space is a main root cause but not the only one. Probably you have faced other root cause – Anatolii Shuba Feb 15 '22 at 14:16
right answer, something had taken almost all of the device internal storage. Recreated a new device with higher internal storage memory solved it, obviously depends on the actual available disk storage your computer has – mightyandweakcoder Apr 13 '22 at 14:54
21

I have more than 20 GB of free space. Still, it is not working. – Zafar Imam Jun 23 '22 at 13:38
Thank you so much. In the Device Manager, I had specified 256 GB space thinking that is what my oneplus phone has. But the space is for the emulator to use. So, even 2GB is more than enough. – Tarun Aug 30 '22 at 20:48
6

lol I just noticed that I have 100MB empty space – midou Oct 08 '22 at 08:54
1

Size is not the issue. I have 32GB Free space. Wrong answer – Nik Dec 06 '22 at 14:01
@Nik This is the correct answer. Please read it more accurately. The "main root cause" means most likely you affected by that root cause. Less likely with other reasons – Anatolii Shuba Dec 07 '22 at 00:05
2

I was able to retrieve GBs of free space after deleting the unused Emulators. – aareeph Dec 13 '22 at 17:11
How do you know my computer so well? :) This was it. – gthuo Dec 31 '22 at 07:06
1

that's a bolt assumption based on nothing since the error does not show anything else – MwBakker Jan 25 '23 at 22:14
The problem with the how much you assigned the internal storage and how much you actually have on the disk so make internal storage then problem will resolved – Akshay Gupta Mar 02 '23 at 09:17
1

This has solved my problem. For me this has to be the correct answer – Tenesuzun Mar 21 '23 at 06:21
2

I have 6.95TB of free disk space and still have this error. – user-123 Mar 29 '23 at 16:29
1

I downvoted because even if I still have 700+ gb left, I still encounter this error. The answer is formatted in a away that is very disingenuous as it appears it shifts the blame to the user devices. – Neon Warge Apr 21 '23 at 08:13
I'm on Ubuntu 20.04, I had this error with 7+ GB free, it went away after I freed up more space up to 15+ GB. It did mention on the [official install page](https://developer.android.com/studio/install) that about 16GB of free space is needed, I guess I overlooked that information. – xodeeq Jun 05 '23 at 16:29
1

How can you explain that this also occurred on a 1tb SSD with still 500tb free? Answers like this makes my blood boil because here are again always blaming the devices of the developers for this issue. I wish I can downvote this answer a thousand times. – Neon Warge Jun 13 '23 at 14:52
@NeonWarge Please read the answer more accurately before your blood completely boiled out. The "main root cause" means most likely you affected by that root cause. Less likely you affected with other reasons. Probably thisi is the correct answer and 300+ upvoters confirmed it. – Anatolii Shuba Jun 17 '23 at 17:55
2

I was extremely sceptical but it did work immediately. I had to free up a bit more than 10GB to make it working on a Mac. Thanks a lot @AnatoliiShuba you saved me hours of no sensical debugging !!! – Stefano Tuveri Jun 27 '23 at 11:24

score 118 · Answer 2 · edited Apr 12 '23 at 07:31

118

Faced this issue after update to arctic fox.

After seeing error message about termination, open android studio logs

On Windows:

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

Or on all platforms:

Open Help Menu
Select Open Log in Files/Explorer/...

scroll it down and try to find log line with text "Emulator terminated with exit code". Probably, the reason for termination can be found a few lines above this message - for me it was

"Emulator: cannot add library vulkan-1.dll: failed".

If you have the same reason - go to C:\Windows\System32 directory, search here for file called vulkan-1-999-0-0-0.dll and just rename it to vulkan-1.dll (i've made a copy just in case and named it "vulkan-1.dll").

This fixed the issue for me.

edited Apr 12 '23 at 07:31

hb0

3,350
3
30
48

answered Aug 02 '21 at 13:20

DistantBlue

1,424
1
9
14

11

I did not have the same issue but the look into the logs lead me to my solution so +1. For anyone interested mine issue was "Emulator: unknown option: -qt-hide-window" so I ran the command without it. – TheLibrarian Aug 02 '21 at 13:37
9

I was missing this file vulkan-1-999-0-0-0.dll . I downloaded it from the web. And copied the file with this name to System32 and also renamed its second copy to vulkan-1.dll and copied it to the same folder. It helped – Arty Morris Dec 02 '21 at 06:53
After the several hours of trying other possible solutions, only this was worked for me. A closer explanation of the issue and link for DLL download is mentioned on the following topic: https://stackoverflow.com/questions/65696048/android-studio-emulator-cannot-add-library-vulkan-1-dll-failed – redrom Dec 03 '21 at 10:34
8

i got the dll from https://www.dll-files.com/vulkan-1.dll.html hope this helps – Stevo Dec 20 '21 at 04:58
I was missing amdvlk64.dll and also vulkan-1.dll. Got amdvlk64.dll from internet and copied twice to System32 as vulkan-1.dll and amdvlk64.dll and it is okay now. Thanks! – SMhd Asadi Dec 23 '21 at 13:20
2

I didn't have the vulkan-1.dll file, but adding the advancedFeatures.ini file helped: Vulkan = off GLDirectMem = on > https://stackoverflow.com/a/68416846/10749567 – Ola Ström Dec 27 '21 at 16:20
I wonder why would the `vulkan-1.dll` be missing in the `C:\Windows\System32` directory – Chris Claude Jan 05 '22 at 22:41
5

The best solution is to completely skip the use of 'vulkan-1.dll' by adding the advancedFeatures.ini file with: Vulkan=off, GLDirectMem=on | https://stackoverflow.com/a/68344341/11211041 Then you don't have to download an unknown dll-file... – Snostorp Jan 10 '22 at 18:54
Not vulkan for me (`"Not enough space to create userdata partition. Available: 6123 MB at C:\...., need 7372 MB. "`), but big +1 for how to discover what's wrong! – TWiStErRob Feb 05 '22 at 19:29
Upvoting this for the path to the log file which lead to another error message that helped me find the solution here: https://stackoverflow.com/questions/67987153/android-studio-flutter-warning-another-emulator-is-still-running-windows-10. Although, renaming a DLL file seems dangerous. – Code-Apprentice May 22 '22 at 04:49
1

@TheLibrarian could you please share how to configure **Android Studio** to remove the `-qt-hide-window` param when starting the emulator from the IDE? – andreszs Jun 02 '22 at 22:51

Dharmik Thakkar · Answer 3 · 2023-06-19T05:49:19.577

102

Follow below steps to solve the issue:

Go to Tools -> SDK Manager
In SDK Manager Go To SDK Tools Tab and untick the Android Emulator and click on Apply. This step will uninstall the Android Emulator.

After uninstallation completes: Again Open Tools -> SDK Manager -> SDK Tools -> Install the Android Emulator by enabling the check or tick on Android Emulator. This step will install the Android Emulator again.
After successful installation. Restart Android Studio. Create new emulator device and Run it. This should work.

edited Jun 19 '23 at 05:49

answered Aug 25 '21 at 05:36

Dharmik Thakkar

1,650
1
9
18

5

This method works well, but if you want to avoid reinstalling the Android Emulator, just update it and that will work. I'm using Ubuntu 20.04 and I just updated the Emulator API to the newest version. – Loich Mar 14 '22 at 10:05
It worked only once for me. The second time it again failed as described in the question. I will try the 'Wipe Data' method instead, and see if that helps … – Henke Jan 09 '23 at 14:25
already installed, but same issue occurred on 33, below 33 working properly. – Ramesh Bhati Jul 17 '23 at 04:51

Danny Fang · Answer 4 · 2022-11-10T07:27:52.210

67

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 category), then click end task to kill the process.

edited Nov 10 '22 at 07:27

answered Jul 12 '21 at 02:14

Danny Fang

3,843
1
19
25

2

This did it for me, I think I failed to gracefully terminate the previous emulator and the qemu-xxx process didn't stop – Alex Mandelias Jun 05 '22 at 13:40
Finally, It worked for me after trying everything like restarting Android Studio and Cold boot emulator etc. – Zafar Imam Jun 23 '22 at 13:48
This fixed the problem after forgetting to close the emulator before Android Studio – sebastiandoe5 Nov 27 '22 at 14:56
It works for me too. Thank you for a simple solution. – Long Truong Aug 23 '23 at 11:13

Ravi · Answer 5 · 2021-09-16T15:06:37.567

45

For Linux (should be similar for windows)

Locate your Sdk/emulator directory
Run ./emulator -list-avds
Note the AVD name form output eg. 'Pixel_2_API_30'
Run ./emulator @Pixel_2_API_30

This will try to launch the emulator with selected device and show errors if any, in my case it was a disk space issue since I was low on home space.

emulator: ERROR: Not enough space to create userdata partition. Available: 5084.121094 MB at /home/user/.android/avd/Pixel_2_API_30.avd, need 7372.800000 MB.

I had plenty of space in other partition/disk, so I changed the AVD location by setting environment variable 'ANDROID_AVD_HOME' to preferred location, post this started the Android Studio and using the AVD Manager recreated a Device, HTH.

edited Sep 16 '21 at 15:06

answered Sep 16 '21 at 15:01

Ravi

599
4
7

This solution works for me to check how much space was I needing https://developer.android.com/studio/run/emulator-commandline#:~:text=The%20AVD%20data%20directory%2C%20also,android%2Favd%2F%20name%20. – Juan Velasquez Dec 16 '21 at 13:07
ERROR: process is translated under Rosetta. Attempting to replace emulator installation – Justin Dec 19 '21 at 19:39

score 28 · Answer 6 · answered Oct 13 '21 at 13:54

28

After going through all answers.

This answer can help you finding the root cause. clear the below file and restart the device to know the problem

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

My problem came as

2021-10-13 19:11:54,776 [1564693]   INFO - manager.EmulatorProcessHandler - Emulator: init: Could not find wglGetExtensionsString! arbFound 0 listarbNull/empty 1 0 extFound 0 extNull/empty 1 0 remote 0

On further search i found the this which points out changing advanced settings (Ram size) and Graphics configuration

Step 1 :- while setting up device click on advanced settings

Step 2 :- Change the 2 setting as highlighted. make it 512 and Automatic to Software GLES

answered Oct 13 '21 at 13:54

Gaurav Khurana

3,423
2
29
38

4

To find the location of your logs on the Mac, go to Help -> Show Log in Finder – shagberg May 11 '22 at 18:26
3

Perfect Answer! :) after searching and trying a multiple suggestions, only this suggestion works for me. Thank You. – Tariq Murtuza Jul 25 '22 at 05:48
This works great for emulators that don't have the google play store icons, what about those that do? – Goblinkiller Aug 28 '22 at 23:22
1

This worked when I selected Graphics as Software. Thanks dude – Durgesh Kumar May 09 '23 at 04:59
1

Also works with 1024 MB. However, now I have the "System UI isn't responding" error. – andreszs Jul 20 '23 at 14:48

score 18 · Answer 7 · edited May 14 '22 at 00:57

18

This solved the same issue for me:

Open text editor (eg. notepad)
Type this code:

Vulkan=off
GLDirectMem=on

Save the file as "advancedFeatures.ini" in .android directory. If your user is named Admin, under windows it would be: C:\Users\Admin\.android\advancedFeatures.ini.
Run your app.

edited May 14 '22 at 00:57

Sarthak Raval

1,001
1
10
23

answered Dec 28 '21 at 06:26

Birendraa sharmaa

329
2
5

Where can I find this directory on MacOS 12.0.1 (Monterey)? – user408108 Apr 04 '22 at 15:17
/Users/user/.android, if this file is not available simply create a text file called advancedFeatures.ini and add above mentioned code save it in /Users/user/.android folder(this folder is hidden) – Vinu K.N Jun 19 '22 at 06:09

score 10 · Answer 8 · answered Jun 20 '22 at 09:49

10

This error also occurs when there is not enough free space left on your computer. be sure to free up some more space.

$ emulator -avd phone2

ERROR   | Not enough disk space to run AVD 'phone2'. Exiting...

answered Jun 20 '22 at 09:49

Gedeon Mutshipayi

2,871
3
21
42

1

have ran `emulator -avd Pixel_API_30_2` and it dropped error something related to image and `Quick Boot / Snapshots not supported on this machine.` . Anyway this answer headed to right way – CodeToLife Jul 31 '22 at 07:04

score 9 · Answer 9 · answered Jul 18 '22 at 20:46

9

In Windows, open the Task Manager and kill the process "qemu-system"

answered Jul 18 '22 at 20:46

Adrian

197
1
8

score 8 · Answer 10 · edited Aug 14 '21 at 22:23

8

I updated and had the same problem. I solved the problem by changing the Multicore CPU and memory

image description here

edited Aug 14 '21 at 22:23

enzo

9,861
3
15
38

answered May 02 '21 at 14:25

Julio

97
2

score 8 · Answer 11 · edited Sep 16 '21 at 04:32

8

I faced the same issue. Fixed it by enabling the Hyper-V on my Windows 10 OS. I just typed Hyper in the Start menu and went to Turn Windows features on or off menu and ticked all the Hyper-V checkboxes like this:

edited Sep 16 '21 at 04:32

ZygD

22,092
39
79
102

answered Sep 16 '21 at 02:43

Nina

81
1
3

Yes, enabling Hyper-V on my Windows 10 64-bit system stopped the "The emulator process for AVD" ... "has terminated" crashes for me too! I'm baffled, because instructions at https://developer.android.com/studio/run/emulator-acceleration indicate the exact opposite, namely that one should disable Hyper-V instead of enabling it. I had also tried HAXM v7.7.0 from https://github.com/intel/haxm/releases instead of the HAXM v7.6.5 that was in my \C:\Android\extras\intel\Hardware_Accelerated_Execution_Manager folder, but that did not work either, only enabling Hyper-V worked thus far. – seeingwithsound Sep 21 '21 at 21:29
checkin both Hyper-V options, worked for me thanks – Muhammad Abdullah Jan 19 '23 at 02:25

score 7 · Answer 12 · answered Jan 12 '22 at 05:45

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:-

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

score 6 · Answer 13 · answered Feb 24 '22 at 18:27

6

This might sound like a joke but restart the computer maybe? I had some emulator processes hanging in the task manager. Restarted the computer and it worked. Maybe it is an android studio bug.

answered Feb 24 '22 at 18:27

Numan Karaaslan

1,365
1
17
25

1

Worked for me. Restarted Android Studio several times, but still no solution. Restarted the computer and DONE! – Xalo Carvalho Jun 23 '22 at 10:56
1

If you have VirtualBox or some other VM software you may discover you cannot run Android Emulator at the same time. I think mine was hung up and hadn't stopped, so reboot did the trick. – raddevus Apr 07 '23 at 14:27

score 6 · Answer 14 · answered Jun 10 '22 at 08:09

6

Check if your disk space of computer is full or not. In my case C:// was full

answered Jun 10 '22 at 08:09

Jack

1,825
3
26
43

Joao Brasil · Answer 15 · 2021-08-19T23:48:27.163

5

OK I fixed my problem like the one above by:

I removed the emulator in the AVD manager and reinstalled it. I also deleted the ANDROID_HOME environment variable and it worked again for me in Artic Fox

I am on the latest version of Android Studio Artic Fox 2020.3.1 Patch One on Windows 10 and I upgraded the emulator yesterday 8/18/21 and it completely broke functioning emulators.

edited Aug 19 '21 at 23:48

answered Aug 19 '21 at 22:35

Joao Brasil

66
1
4

jaiminkumar patel · Answer 16 · 2021-12-14T05:02:20.880

5

I would like to mention something about this,

The mentioned solutions works, however, if none works then please make sure you have sufficient space where AVDs are generated.

If system do not find the enough space to operate, it will give this error too, same as in my case.

If space is not an issue for you then mentioned other solutions must work.

edited Dec 14 '21 at 05:02

answered Dec 14 '21 at 04:57

jaiminkumar patel

111
2
5

One last thing... Take a look at the Event Log if the Issue is related with Vulkan download and install the Vulkan Runtime: https://vulkan.lunarg.com/ – zion Dec 27 '21 at 12:06
after decreasing internal storage space emulator launched. – Yestay Muratov Jun 10 '22 at 10:46

score 5 · Answer 17 · edited Apr 06 '22 at 14:08

5

Was facing similar issue while launching arm64 emulator. I had enough disk space and tried uninstalling the emulator and reinstalling it. But this didn't help.

I was able to figure out the issue by running the below commands:

emulator -list-avds
emulator @NameOfAvd

This assumes you've emulator on the path. Executing the last command showed me the below errors which weren't visible when running from Android Studio:

[4453299712]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/Users/username/../emulator/qemu/darwin-x86_64/qemu-system-aarch64': No such file or directory

Executing the command emulator @NameOfAvd from the Android/sdk/tools path allowed me to start the arm64 AVD.

edited Apr 06 '22 at 14:08

halfer

19,824
17
99
186

answered Apr 06 '22 at 11:06

Mahendra Liya

12,912
14
88
114

This helped. This is Android Studio bug imo. I have my Android SDK location set up as `C:\SDKs\android-studio-canary\SDK\ ` , so running `emulator -avd my_image` should run my image from `C:\SDKs\android-studio-canary\SDK\system-images\android-29\..`, but terminal says `C:\Users\Developer\AppData\Local\Android\Sdk\system-images\android-29\android-automotive-playstore\x86\ is not a valid directory.` So it is simply using a wrong directory here. Maybe it's because I'm using both normal AND canary version of Android Studio. – Starwave Dec 27 '22 at 11:49
It is because the paths for AVD's are generated from system variable `ANDROID_SDK_ROOT`. Currently mine is the non-canary version `C:\Users\Developer\AppData\Local\Android\Sdk`, hence why it shows up on the terminal as an active path. Changing it out with canary sdk path worked! – Starwave Dec 27 '22 at 12:00

score 4 · Answer 18 · answered Jan 10 '22 at 07:09

4

In case if anyone facing this issue. I solved it by:

Go to C:\Users\YourUserName\.android
Create a file named advancedFeatures.ini
Then add the following lines of code in the file:
```
 Vulkan = off
 GLDirectMem = on
```

answered Jan 10 '22 at 07:09

Arun K Babu

113
1
10

score 3 · Accepted Answer · answered May 02 '21 at 01:20

3

It's an issue of latest Emulator.

I upgraded to v30.6.4 last night and got the same issue.

Please use Genymotion instead before Android Studio Emulator issuing its next update.

It's free for personal use.

https://www.genymotion.com/download/

answered May 02 '21 at 01:20

bhw1899

87
4

@IgorLevkivskiy can you explain how to downgrade emulator version? – basilkot May 03 '21 at 18:16
@basilkot find a download link of an older version and then replace android_sdk/emulator folder with the downloaded one. – Primož Ivančič May 03 '21 at 20:55
1

I can't find download link of an older version of emulator , I updated to latest which does not work , Can you please provide me with a download link of an older version of emualator ? – Waqas Tahir Jul 08 '21 at 10:44
2

I'm a little bit confused... so it's half a year and the main core feature of android studio doesn't work without any official fix? Am I missing something here? – Michael Chen Sep 05 '21 at 17:14

score 3 · Answer 20 · answered Aug 04 '21 at 11:01

3

I Remove the Emulator folder from the SDK path and download the new component. It's working fine.

answered Aug 04 '21 at 11:01

Shobana Velmurugan

506
2
18

score 3 · Answer 21 · edited Aug 29 '21 at 10:04

3

My issue is resolved when I changed the CPU/ABI setting from "armeabi-v7a" to "x86_64".

edited Aug 29 '21 at 10:04

halfer

19,824
17
99
186

answered Aug 25 '21 at 19:48

Sajawal Bashir

41
3

Aren't arm emulators slower than x86_64? (it kind of sort of says so when you select arm while creating virtual device). I use MacBook Pro 2021, M1 Pro – Johnny Five Jan 23 '22 at 11:40

score 3 · Answer 22 · answered Dec 06 '21 at 10:54

3

In my MacbookPro M1 Pro, The issue was I had selected the x86 image while creating the emulator device.

Changing this setting and using the image from the recommended images resolved my issue.

answered Dec 06 '21 at 10:54

Sameer Shelar

118
6

Sarthak Raval · Answer 23 · 2022-10-15T10:10:43.683

3

Go to Device Manager on Android Studio
Click Drop Menu on Action Panel
Click Wipe Data
Launch your AVD Manager Again OR Restart Your computer

edited Oct 15 '22 at 10:10

answered May 06 '22 at 05:02

Sarthak Raval

1,001
1
10
23

this method works, but it wipe data and it is not the best – JeckOnly Apr 14 '23 at 03:34

score 2 · Answer 24 · answered Sep 13 '21 at 18:41

2

I was not able to start API_30 devices.

I had to install the latest hardware accelerator version (HAXM v7.7.0) from https://github.com/intel/haxm

Then

answered Sep 13 '21 at 18:41

Sebastian

63
5

Fingers crossed, but upgrading to the latest HAXM v7.7.0 seemed to be the trick for me. So far so good. AVD crashed again the first load but now is loading on the fresh boot. – drewid Nov 15 '21 at 01:23

score 2 · Answer 25 · answered Nov 26 '21 at 17:59

2

The simple solution was to free up some space from the hard-disk
In my case, only 2gb space was available in the hard-disk.
I made some space by emptying the bin, and now available space was 22gb.

Then I just started the emulator normally ( didn't uninstall or deleted anything) and it started.

answered Nov 26 '21 at 17:59

Akshay Chopra

1,035
14
10

In my case, try Cold Boot Now after free up – Paul Han Mar 10 '23 at 08:48

score 2 · Answer 26 · answered Dec 14 '21 at 16:15

2

I face same kind of issues... After increase free space of machine its working fine...

answered Dec 14 '21 at 16:15

Piyush

1,156
12
20

score 2 · Answer 27 · answered Feb 28 '22 at 05:24

For those who running flutter/Dart in android studio. Here are the step on how I solved this:

Go to any of your current device in Device manager.
Click the edit icon (Pen Icon). Then dialog for edit will open.
Now change the "Graphics" property in the AVD under Emulated Performance from automatic to "Software-GLES 2.0". it works for me.

Note: Am using android studio Bumblebee | 2021.1.1 patch 2

score 2 · Answer 28 · answered Jun 30 '22 at 11:07

2

The problem might be due to some corrupted data during saving the state. Cold start the VM will solve the problem.

answered Jun 30 '22 at 11:07

Uvan Shankar

71
4

score 2 · Answer 29 · answered Jan 12 '23 at 06:55

2

In my case i has error in log which is located:

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

My error:

PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT

This answer helped me

answered Jan 12 '23 at 06:55

Aden Kurmanov

101
8

score 1 · Answer 30 · edited Aug 08 '21 at 13:12

Really, I had same issue. I had tried over 10 times..im not professor but I found finally. It was a tough time for me.

Try again follow next.

If you install Android again again, I think import setting has problem. wrong Path on android screen. not environment Path Because automatically it is determined old path(when it installed first)

and Choose a lower API if possible in my case, when I use API 17, the emulator acted. but API 30, The emulator has terminated...so, I think if you use windows 7 or low spec, use low API environment. In addition, I needed installing emulator-windows_x64-7491168,zip (In my case)

enter image description here

score 1 · Answer 31 · answered Oct 11 '21 at 12:01

1

After having tested solutions suggested in this forum, the only one which solved the problem to me is to free space in my hard disk. In my case I needed at least 7 GB to make it work.

answered Oct 11 '21 at 12:01

Juliana Melo

19
2

I had 6GB free, After clearing another 4GB, I was able to run the emulator – vijayst Nov 01 '21 at 06:26

redballtoy · Answer 32 · 2021-11-17T00:52:12.700

1

In my case, lowering the API version to 28 for System Image x86 helped when creating new Virtual Device.

edited Nov 17 '21 at 00:52

answered Nov 17 '21 at 00:43

redballtoy

21
4

score 1 · Answer 33 · answered Dec 07 '21 at 16:26

1

I select configuration of the emulator graphics "Hardware-GLES 2.0", it worked

answered Dec 07 '21 at 16:26

FlutterCyber

11
1

score 1 · Answer 34 · answered Jan 06 '22 at 06:08

1

I had the same issue and i had tried all the above solution but couldn't succeed. finally i have got rid of this issue in my HP PC by uninstalling the pre installed program hp wolf security.

answered Jan 06 '22 at 06:08

Linendra Soni

170
1
10

This is working. After I uninstall all the HP related softwares from the machine, the Emulator started working. None of the other solutions worked for me Except this. – Reddy Raaz Aug 23 '22 at 09:47

score 1 · Answer 35 · answered Jan 10 '22 at 06:51

1

In my case, i solved it by delete existing AVD and create new one.

answered Jan 10 '22 at 06:51

amerw

357
2
12

As easy as this. In my case, I created the device and I couldn't complete the configuration because virtualization in the BIOS wasn't enabled. I enabled it and I continued the configuration of the device. I guess that's why I was getting the error. Removing it and creating it again solved the issue. – Tonatio Jul 31 '22 at 09:09

score 1 · Answer 36 · answered Feb 01 '22 at 06:17

1

Open "Edit this AVD".
In the section "Emulator Performance" change Graphic type to another (for example, Software - GLES 1.1).

I have an old video card and this is work in my case.

answered Feb 01 '22 at 06:17

kirkadev

355
4
10

the dropdown list is disabled, I cannot change to anything else. – C.K. Mar 07 '22 at 23:38

score 1 · Answer 37 · answered Feb 10 '22 at 10:52

If emulator is terminating and it was properly running earlier and even if you have enough disk space. You can delete and create a new Virtual device which is almost same as "Wipe Data" action on existing Emulator. But if you do not want to wipe data and loose any kind of progress made on the Emulator, There is a "Cold Boot" option for you which helps. It actually solved the problem for me.

score 1 · Answer 38 · answered Sep 23 '22 at 04:45

1

Open device manager
Click menu
run cold boot

answered Sep 23 '22 at 04:45

Kabilan

83
1
8

score 1 · Answer 39 · answered Sep 23 '22 at 04:49

1

I removed one previous emulator and then run the new one it worked for me :)

answered Sep 23 '22 at 04:49

Muhammad Usama

21
1

This was the same issue I had, I had two different .android locations with avd. deleted the old one and the issue resolved by itself – xrayian Jun 08 '23 at 16:11

score 1 · Answer 40 · answered Oct 11 '22 at 09:06

As this issue took me quite some time to resolve, I want to share my solution on OSX as well. To be honest, in my case the problem was that I had previously used the Android SDK without Android Studio and thus an environment variable was not configured correctly.

Checking the idea.log (Help > Show Log in Finder) I realized those error details:

PANIC: Cannot find AVD system path. Please define  ANDROID_SDK_ROOT

I quickly added the environment variable to my .zshrc (Prefernces > ... > Android SDK), in my case:

export ANDROID_SDK_ROOT=/Users/felixgeissler/Library/Android/sdk

But to this point the problem persisted:

PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [/Users/felixgeissler/Library/Android/sdk]!

After that I realized that I had defined the ANDROID_HOME variable in my .zshrc as well. Removing this entry somehow resolved issue! I assume that the removed variable interfered with the SDK root.

This blog post pointed me in the right direction: https://betamode.de/2018/11/16/android-emulator-panic-broken-avd-system-path-check-your-android_sdk_root-value/ — F. Geißler, Oct 11 '22 at 09:06

score 1 · Answer 41 · answered Feb 17 '23 at 14:48

Simply try to disable emulator VM acceleration.

You can force the use of the soft x86 emulator by running it from the command line and using the -no-accel option.

i.e. from the SDK/tools directory on Windows :

To list available AVDs:

C:\Users\<YOUR_USER_NAME>\AppData\Local\Android\Sdk\emulator>emulator -list-avds

To disable VM acceleration:

C:\Users\<YOUR_USER_NAME>\AppData\Local\Android\Sdk\emulator>emulator -avd Pixel_4_API_29 -no-accel -no-boot-anim

Reference: https://developer.android.com/studio/run/emulator-commandline#common

score 1 · Answer 42 · answered Mar 03 '23 at 12:30

1

Be sure that you had ANDROID_SDK_ROOT with a valid SDK path in your system environment. that happens when you move your SDK folder.

answered Mar 03 '23 at 12:30

Tamer Sy

26
1
2

score 0 · Answer 43 · answered Aug 02 '21 at 17:15

0

I had the same problem when I upgraded the Emulator, the solution that worked for me is: -updating windows -and remove all the AVDs then I installed a new one.(release name:Pie,

answered Aug 02 '21 at 17:15

Yassine BENNKHAY

89
1
10

score 0 · Answer 44 · edited Aug 29 '21 at 02:36

0

I solved this by clearing data of the emulator, and then restart the emulator. Finally the emulator has not terminate when launched

edited Aug 29 '21 at 02:36

Avinash Kumar Singh

735
6
19

answered Aug 28 '21 at 10:10

Reksa Fitrananda

21
6

score 0 · Answer 45 · answered Sep 05 '21 at 08:14

0

It's an issue of latest Emulator .

I upgraded to v30.6.4 last night and got the same issue.

Team fixed issue and released new version do update it , https://i.stack.imgur.com/mXYJs.png

well its working now

answered Sep 05 '21 at 08:14

kumar

11
2

score 0 · Answer 46 · answered Oct 20 '21 at 19:49

0

I had to remove the Android Emulator and reinstall it. Also I freed up some space to get it to work!

answered Oct 20 '21 at 19:49

Anil Sapkota

35
2

score 0 · Answer 47 · answered Dec 04 '21 at 15:47

0

For me unchecking the "Multi-Core CPU" option in the virtual device configuration did the job. It is listed under "Advanced Settings".

answered Dec 04 '21 at 15:47

MrMois

1

score 0 · Answer 48 · answered Dec 06 '21 at 17:13

0

I had the same issue. From the logs, the error code pointed to a lack of space for creating userdata. So, deleting caches of previously deleted VDs did the job for me. Go to C:\Users\user.android\avd and delete any unused files.

answered Dec 06 '21 at 17:13

Mohammed Hammad

43
8

score 0 · Answer 49 · answered Dec 09 '21 at 00:11

0

In my case, this happened when I tried to start a second Virtual Device (VD). I was able to resolve the issue by, simply, closing the currently running VD. Once I did this, I was able to run multiple VDs.

answered Dec 09 '21 at 00:11

Bink

1,934
1
25
41

score 0 · Answer 50 · edited Dec 26 '21 at 14:48

0

this is how I solved this issue. I created an AVD with API 28 [ Non google play version] . Choose x86 64 version. Increase the RAM size of AVD to 2 GB Choose Graphic - Hardware GLES 2.0

with this i could able to launch the the AVD and it is much faster than previous one

edited Dec 26 '21 at 14:48

Dharman

30,962
25
85
135

answered Dec 26 '21 at 14:43

Rajesh Kumar Yadav

111
2
5

score 0 · Answer 51 · answered Dec 31 '21 at 19:56

0

For myself, I had a mismatch in my $ANDROID_HOME envvar.

It was pointed to an old location before I had downloaded Android Studio. Updated to $HOME/Library/Android/sdk and we are good.

answered Dec 31 '21 at 19:56

ether_joe

1,068
1
13
32

score 0 · Answer 52 · answered Jan 26 '22 at 17:27

0

To me, the solution was executing the VulkanRT-Installer.exe

answered Jan 26 '22 at 17:27

excitedWithin

41
6

score 0 · Answer 53 · answered Feb 05 '22 at 17:24

android studio has issue with special characters where the issue could be due to the mapping where the emulator runs. I had this problem where I was running on my C:/User that had 'ã' and with that the same error occurred. To fix change the Windows environment variable 'ANDROID_USER_HOME' to a folder with a common name for example C:\Android\sdk

score 0 · Answer 54 · answered Feb 09 '22 at 03:01

I had this issue, running Android Studio Bumblebee 2021.1.1 on Ubuntu 20.04.3 LTS.

Issue in my case was a mismatch between NVideo kernel module and NVideo client libraries, as noted from dmesg output (these log entries appeared each time an AVD was restarted and failed):

NVRM: API mismatch: the client has the version 470.103.01, but
NVRM: this kernel module has the version 470.86.  Please                           
NVRM: make sure that this kernel module and all NVIDIA driver                           
NVRM: components have the same version.

Solution in my case was to upgrade the NVidia drivers to package nvidia-driver-510 using the Additional Drivers dialog of Ubuntu. Then reboot.

score 0 · Answer 55 · answered Feb 11 '22 at 12:35

0

change the "Graphics" property in the AVD,choose "Soft ware --Gles2.0". it works for me.

answered Feb 11 '22 at 12:35

YJ.XU

11
4

score 0 · Answer 56 · answered Feb 17 '22 at 16:40

Short story long

I came into this issue two weeks ago on Windows 11. I haven't performed anything special with my setup over the weekend. But on Monday I could not run emulator. I tried Updating/Reinstalling Android Studio and it's modules via SDK manager. Nothing helped.

In C:\Users<User>\AppData\Local\Google\AndroidStudio2021.1\log\idea.log I found some issues with Vulkan during emulator starting.

What helped

Updating Windows and Nvidia drivers to latest version. @Darren Smith fixed this issue for Ubuntu by updating Nvidia drivers too. If it won't help you can at least enjoy latest bugs for your hardware...

score 0 · Answer 57 · answered Feb 24 '22 at 13:38

0

I solved the problem by updating Android Emulator and Intel x86 Emulator Accelerator (HAXM installer) version in Android Studio. Both these components were outdated after update of android studio.

answered Feb 24 '22 at 13:38

Muhammad Aasharib Nawshad

136
9

score 0 · Answer 58 · answered Mar 11 '22 at 13:01

In my case the problem happened on a MacBook Pro with an Apple silicon CPU (m1, arm64), because I've migrated the Android Studio and Android SDK from an older MacBook Pro with Intel CPU. I've re-installed the ARM version of Android Studio then and updated the Android SDK, but seems that Intel emulator version persisted. The solution was just uninstall and reinstall the Android Emulator:

Tools -> SDK Manager -> SDK Tools tab

score 0 · Answer 59 · answered Apr 04 '22 at 16:57

0

Go to Task Manager using (Ctrl+Alt+Delete) and check in background processes that emulator is not running in background. If it is running in background, end task and try to start your emulator again.

answered Apr 04 '22 at 16:57

Ahmad hassan

769
4
14

score 0 · Answer 60 · answered May 02 '22 at 12:49

0

goto avd folder

delete all avd's

and relaunch avd

hope you will find avd working fine

answered May 02 '22 at 12:49

sherkhan

811
8
8

score 0 · Answer 61 · answered Jul 11 '22 at 12:58

0

I selected a system image from ARM Images instead of Other Images and the emulator is running fine.

answered Jul 11 '22 at 12:58

Tornike Kurdadze

955
2
10
24

score 0 · Answer 62 · answered Oct 21 '22 at 10:57

0

Everything Fine. Good Work. Just make a little change. If you have 2 different pixel types appearing on Virtual Device section you have to delete any one of the pixel emulator which you do not prefer for your project. Delete it by clicking drop down arrow > Delete. It'll work for you the way it did for me. If you already have 1 pixel emulator, I might be wrong in telling you that the problem is you need SUFFICIENT SPACE where your ADVs generated OR you need to upgrade the HAXM installer to the latest --v

answered Oct 21 '22 at 10:57

Huzaifa Iftikhar

41
4

This answer just refers to the accepted answer: https://stackoverflow.com/a/68682990/1387386 – Anatolii Shuba Dec 21 '22 at 16:38
Thanks for telling. I did not see it when creating solution for the issue. – Huzaifa Iftikhar Dec 22 '22 at 17:40

score 0 · Answer 63 · edited Jan 11 '23 at 17:47

The issue can be due to different reasons; in my case it was due to the path not found to the system-images folder. Somehow my system-images folder inside sdk was missing. Since I had a backup of my sdk, I put the old one into sdk folder and the emulator started to work. If you are seeing something like below in the log file, try this approach.

Emulator: Pixel 2 API 28 - emulator: WARN: path_getAvdSystemPath: ..rootdirectory/Android/sdk/system-images/android-28/google_apis_playstore/x86/ is not a valid directory.

score 0 · Answer 64 · edited Feb 08 '23 at 03:28

0

Open the directory in which OS is installed.
Then go to Users > <YOUR_USERNAME> > .android/avd/ <AVD_NAME> .avd/
Delete all files ending with .lock extension.

edited Feb 08 '23 at 03:28

elpidaguy

624
1
11
25

answered Feb 03 '23 at 09:13

Abdul Hanan

23
4

score 0 · Answer 65 · answered Jun 15 '23 at 08:29

Because i didn't see my solution for this problem yet:

In my case it was a problem with the environment variable ANDROID_SDK_ROOT. I have installed 2 different ANDROID SDKs and the problem was that my environment variable targeted another SDK than my Android Studio SDK Manager.

Turns out you have to set the ANDROID_SDK_ROOT to the same Android-SDK-Path as Android Studio (Android Studio -> SDK Manager) points to.

I found this solution in the android studio logs. See above comment.

score 0 · Answer 66 · answered Jun 28 '23 at 01:21

0

I deleted the emulator folder: ~/Android/Sdk/emulator
Then I opened Android Studio, opened Android SDK Tools: Settings/Appearance & Behavior/System Settings/Android SDK/SDK Tools
I checked the box for Android Emulator then I clicked Apply

answered Jun 28 '23 at 01:21

Samuel Wakoli

41
6

score 0 · Answer 67 · answered Jun 29 '23 at 01:40

This might sound dumb but...

I'm new to Android Studio, and I tried all the tricks listed above with over 100Gb free space. I constantly got the dreaded 'Emulator has been terminated message' every time I tried to create a virtual device. In the same time I also installed on MacOs and I did not have the least issue.

I accidentally stumbled on something solved the issue for me. Since I couldn't create a virtual device, I physically connected my phone via USB. After this I did my first build and during the build I got an error saying that the path to the Android SDK is not writable. For some reason my PATH variable for Android SDK was set to the Program Files directory in Windows. I changed this to the actual location which is c:\users\myuserid\appdata\local\Android\Sdk.

Now my build worked and afterwards I found I could create AVD easily! Phew.

score 0 · Answer 68 · answered Jul 02 '23 at 18:22

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.

score 0 · Answer 69 · answered Jul 15 '23 at 03:51

0

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

answered Jul 15 '23 at 03:51

mahsa k

555
6
9

Kwaku Stiles · Answer 70 · 2021-08-18T08:48:14.597

-1

I just restarted my machine and it worked. And yea! I agree with anatolii-shuba’s answer with the main cause been as a result of lack of free space on your disk

edited Aug 18 '21 at 08:48

answered Aug 18 '21 at 08:42

Kwaku Stiles

9
1

3

Please don't add "I agree with" as answers. They don't actually provide an answer to the question, and can be perceived as noise by its future visitors. Once you [earn](https://meta.stackexchange.com/questions/146472/what-is-the-best-way-to-increase-my-reputation-and-privileges) enough [reputation](https://stackoverflow.com/help/whats-reputation), you will gain privileges to [upvote answers](https://stackoverflow.com/help/privileges/vote-up) you like. This way future visitors of the question will see a higher vote count on that answer. – Tyler2P Aug 18 '21 at 10:20

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

70 Answers70

Short story long

What helped

Linked