Android Studio says the emulator process for the AVD has terminated
The emulator process for AVD <name> has terminated.Short answer
The emulator started and then exited, so Android Studio only reports that the process ended. Run the same AVD from a terminal to see the real message. Documented causes are less than 5 GB of free disk, Windows running out of commit limit, a missing vulkan-1.dll or msvcp140 DLLs, and a graphics mode the machine cannot run.
Fix it fast
1Find out which cause you have
Start the AVD yourself and read what the emulator prints before it exits. Take the AVD name from the list.
emulator -list-avds emulator -avd Pixel8_API_34 -verbose2Match what you see, then jump to its fix
- 1
The emulator exits at once, and the drive that holds the SDK or the AVD folder is nearly fullLess than 5 GB of free disk spaceFix - 2
Fails only on Windows, mostly when many programs are openWindows cannot reserve the emulator's memory (commit limit)Fix - 3
vulkan-1.dll cannot be foundvulkan-1.dll cannot be foundFix - 4
Emulator terminated with exit code -1073741511Exit code -1073741511 on Windows: runtime DLLs are missingFix - 5
The verbose output stops after GPU or Vulkan lines, or the app renders wrongly on Apple SiliconThe graphics mode crashes the emulatorFix
- 1
What does the error look like?
The emulator process for AVD <name> has terminated.vulkan-1.dll cannot be foundEmulator terminated with exit code -1073741511
Cause 1 of 5
Less than 5 GB of free disk space
1Check
On startup the emulator checks free disk space and does not start unless at least 5 GB is free.
df -h ~
# Windows: check the free space of the drive in File Explorer2Fix
Free disk space on the drive that holds the AVD and SDK folders, then start it again.
emulator -avd Pixel8_API_343Verify
The emulator window opens and stays open.
adb devicesConfirmed by developer.android.com
Cause 2 of 5
Windows cannot reserve the emulator's memory (commit limit)
1Check
The emulator asks Windows to account for the whole guest RAM at start. If that goes over the commit limit, the start fails. Task Manager's Performance tab shows the commit charge.
# Task Manager (Ctrl+Shift+Esc) > Performance > Memory > Committed2Fix
Close unused applications, turn off third-party memory compression or management tools, and set the pagefile to system managed size.
# Windows: System Properties > Advanced > Performance > Virtual memory > System managed size3Verify
The AVD starts with the same settings as before.
emulator -avd Pixel8_API_34Confirmed by developer.android.com
Cause 3 of 5
vulkan-1.dll cannot be found
1Check
The troubleshooting page says this message usually means the emulator itself needs updating.
emulator -version2Fix
Update the emulator in Tools > SDK Manager. If you do not need Vulkan apps, start the AVD with Vulkan switched off.
emulator -avd Pixel8_API_34 -feature -Vulkan3Verify
The AVD boots.
adb devicesConfirmed by developer.android.com
Cause 4 of 5
Exit code -1073741511 on Windows: runtime DLLs are missing
1Check
The docs link it to missing msvcp140.dll, msvcp140_1.dll and msvcp140_2.dll, seen on Windows 10 N editions without the Windows Media Feature.
dir C:\Windows\System32\msvcp140*.dll2Fix
Install or reinstall the optional Windows Media Feature Pack, following Microsoft's instructions, then restart.
# Windows: Settings > Optional features > Windows Media Feature Pack3Verify
The emulator starts instead of exiting.
emulator -avd Pixel8_API_34Confirmed by developer.android.com
Cause 5 of 5
The graphics mode crashes the emulator
1Check
On Apple Silicon, hardware rendering uses MoltenVK, which does not support every Vulkan feature. Software rendering avoids that.
emulator -avd Pixel8_API_34 -verbose2Fix
Run with software rendering, or switch the AVD's graphics setting to software.
emulator -avd Pixel8_API_34 -gpu swiftshader_indirect3Verify
The AVD boots and stays running.
adb devicesConfirmed by developer.android.com
How do I stop it coming back?
- Keep well over 5 GB free on the drive that holds your AVDs.
- Update the emulator in the SDK Manager after Android Studio updates.
- Start a failing AVD from the terminal with -verbose before changing settings.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
The Android emulator never finishes booting in Android Studio
The emulator window stays on the boot logo or a black or white screen
The emulator process started but Android never reported itself ready to adb, so Studio gave up waiting.
4 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix