Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Android Studio says the emulator process for the AVD has terminated

ErrorThe 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.

  • Applies to Android Emulator 36.x, Android Studio current stable, Windows 11, macOS 26, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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 -verbose
  2. 2Match what you see, then jump to its fix

    1. 1The 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. 2Fails only on Windows, mostly when many programs are openWindows cannot reserve the emulator's memory (commit limit)Fix
    3. 3vulkan-1.dll cannot be foundvulkan-1.dll cannot be foundFix
    4. 4Emulator terminated with exit code -1073741511Exit code -1073741511 on Windows: runtime DLLs are missingFix
    5. 5The verbose output stops after GPU or Vulkan lines, or the app renders wrongly on Apple SiliconThe graphics mode crashes the emulatorFix

What does the error look like?

  • The emulator process for AVD <name> has terminated.
  • vulkan-1.dll cannot be found
  • Emulator 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 Explorer

2Fix

Free disk space on the drive that holds the AVD and SDK folders, then start it again.

emulator -avd Pixel8_API_34

3Verify

The emulator window opens and stays open.

adb devices

Confirmed by developer.android.com

Did this fix it?

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

2Fix

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 size

3Verify

The AVD starts with the same settings as before.

emulator -avd Pixel8_API_34

Confirmed by developer.android.com

Did this fix it?

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

2Fix

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

3Verify

The AVD boots.

adb devices

Confirmed by developer.android.com

Did this fix it?

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*.dll

2Fix

Install or reinstall the optional Windows Media Feature Pack, following Microsoft's instructions, then restart.

# Windows: Settings > Optional features > Windows Media Feature Pack

3Verify

The emulator starts instead of exiting.

emulator -avd Pixel8_API_34

Confirmed by developer.android.com

Did this fix it?

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

2Fix

Run with software rendering, or switch the AVD's graphics setting to software.

emulator -avd Pixel8_API_34 -gpu swiftshader_indirect

3Verify

The AVD boots and stays running.

adb devices

Confirmed by developer.android.com

Did this fix it?

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

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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.