● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Android Studio IDE on a developer laptop showing emulator process terminated error message on a dark desk
Fix It Yourself · Troubleshooting

Android emulator not launching

Published 24 August 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Most cases of Android emulator not launching come down to one of five things, and four of them you can sort yourself in under half an hour. No need to reinstall Android Studio from scratch or spend hours trawling forums. This guide covers every fix in order, from the fastest to the most involved.

TL;DR

If your Android emulator not launching is the problem, start with a cold boot of the AVD and check for SDK updates. If that does not fix it, switch graphics mode to Software and verify virtualization is enabled in BIOS. Persistent crashes after that usually mean corrupted emulator files or outdated GPU drivers.

⏳️ 13 min read ✅ 85% success rate 📅 Updated July 2026

Key Takeaways

  • Android emulator not launching is most often caused by a corrupted AVD snapshot, disabled virtualization, or a GPU driver conflict.
  • Cold booting the AVD and wiping its data fixes the problem in a large number of cases with no other changes needed.
  • Switching graphics mode to Software is the fastest way to rule out GPU driver incompatibility.
  • Hardware virtualization must be enabled in BIOS for the emulator to run reliably. Check this if nothing else works.
  • Reinstalling the emulator package from SDK Manager clears corrupted installation files that other steps cannot fix.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 15 to 30 mins
  • Success Rate: 85% of users

What Causes Android Emulator Not Launching?

The emulator is a fairly complex piece of software. It is spinning up a full virtual ARM or x86 device on your machine, relying on your CPU's virtualization extensions, your GPU drivers for rendering, and a stack of SDK components that all need to be in sync. When any one of those breaks, you get nothing. Sometimes a blank screen. Sometimes the dreaded The emulator process has terminated message. Sometimes the AVD just never appears in the device list at all.

Here are the five root causes that cover the vast majority of cases:

  • Virtualization disabled in BIOS/UEFI: The emulator depends on Intel VT-x or AMD-V to run at usable speed. If these are off, the emulator either fails to start or crawls so slowly it looks broken.
  • Corrupted AVD snapshot or state: Every time you close the emulator, it saves a snapshot. If that snapshot gets corrupted (power cut, crash, bad update), the next launch attempt fails. This is probably the single most common cause.
  • Outdated or broken SDK components: The Android Emulator package, platform-tools, and system images need to stay in sync. A partial update or interrupted download leaves them in a broken state.
  • GPU driver incompatibility: The emulator uses your host GPU for hardware-accelerated rendering. Older drivers, or drivers from certain OEMs, cause repeated crashes. You'll often see a blank emulator window or an immediate termination.
  • Wrong SDK path: If Android Studio is pointing at the wrong SDK location (or none at all), it cannot find the emulator binary. The AVD won't start because Studio literally cannot locate the files it needs.

Worth knowing: these causes are not mutually exclusive. It is entirely possible to have a corrupted snapshot and an outdated emulator package at the same time. Work through the fixes in order and you'll cover all of them.

For context on how the emulator uses hardware acceleration, Google's official emulator acceleration documentation is the clearest reference for understanding what the emulator actually needs from your hardware.

Android Emulator Not Launching: Quick Fixes

Start here. These take five to ten minutes and fix the problem more often than you'd expect.

1

Cold Boot the AVD and Wipe Its Data Easy

  1. Open Device Manager in Android Studio
    Go to Tools > Device Manager. You'll see your list of AVDs.
  2. Cold boot instead of resuming
    Right-click (or click the three-dot menu) on your AVD and select Cold Boot Now. This bypasses the saved snapshot entirely and boots from a clean state. Wait a full 60 to 90 seconds before assuming it has failed.
  3. If cold boot fails, wipe the data
    Right-click the AVD again and select Wipe Data. Confirm, then try launching normally. This deletes the corrupted snapshot and any stale emulator state.
  4. Restart Android Studio if needed
    If the AVD still won't start, close Android Studio completely (check Task Manager on Windows or Activity Monitor on Mac to make sure no studio64.exe or studio processes are still running), then reopen it and try again.
Success: The emulator boots to the Android home screen within 2 minutes. If it gets past the Google logo, you're sorted.
2

Update the Emulator and SDK Tools Easy

  1. Open SDK Manager
    Go to Tools > SDK Manager, then click the SDK Tools tab.
  2. Check for updates
    Look for Android Emulator and Android SDK Platform-Tools. If either shows an update available, tick the checkbox and click Apply.
  3. Restart Android Studio
    Once the download finishes, close and reopen Android Studio. Microsoft's MAUI troubleshooting documentation explicitly recommends applying all SDK updates as a first step when the emulator is not appearing or launching correctly. It's good advice.
Success: The emulator package version in SDK Tools shows as up to date and the AVD launches without errors.
3

Verify the SDK Path Easy

  1. Check SDK location in Android Studio
    Go to Settings (or Preferences on Mac) > Languages and Frameworks > Android SDK. The Android SDK Location field at the top should point to a real folder containing subfolders like emulator, platform-tools, and platforms.
  2. Fix it if it's wrong
    On Windows, the default is usually C:\Users\YourName\AppData\Local\Android\Sdk. On Mac it's typically /Users/YourName/Library/Android/sdk. If the field is blank or points somewhere that doesn't exist, click Edit and point it to the correct location.
  3. Restart and retest
    Save the settings, restart Android Studio, and try launching the AVD again.
Success: The SDK Manager loads without warnings and the emulator binary is found at the corrected path.

More Android Emulator Not Launching Solutions

If the quick fixes above didn't crack it, these intermediate steps cover the next most likely causes. Expect 15 to 30 minutes here.

4

Switch Graphics Mode to Software Easy

This is the fastest way to rule out GPU driver incompatibility. Software rendering is slower, but it bypasses your host GPU entirely, so if the emulator runs fine after this change, you know your drivers are the problem.

  1. Edit the AVD configuration
    In Device Manager, click the pencil (edit) icon next to your AVD.
  2. Change the graphics setting
    Scroll down to Emulated Performance. Change Graphics from Automatic to Software.
  3. Save and relaunch
    Click Finish to save. Launch the AVD and see whether it starts. If it does, your GPU drivers are the culprit. See Solution 7 below for the proper fix.
Note: Software rendering works fine for basic app testing. It is noticeably slower for anything graphics-heavy, so treat it as a diagnostic step or a temporary workaround while you sort the drivers.
Success: The emulator launches and displays the Android UI. Performance may be slower than usual, which is expected in Software mode.
5

Create a Fresh AVD Easy

Sometimes a device profile gets into such a bad state that no amount of wiping fixes it. Creating a new AVD from scratch takes about five minutes and is often more reliable than fighting a broken one.

  1. Open Device Manager and create a new device
    Click the + button (Create Virtual Device). Pick a device definition, such as Pixel 7.
  2. Choose a system image
    Select a system image you already have downloaded, or download a fresh one. API 33 or 34 images are stable choices for most testing.
  3. Name it something different
    Give it a new name so it doesn't conflict with the broken AVD. Click Finish.
  4. Launch the new AVD
    Try launching this fresh device. If it starts without issue, the problem was specific to the old AVD's configuration or state files.
Success: The new AVD boots cleanly. You can delete the old broken one from Device Manager once you've confirmed the new one works.
6

Check Disk Space and AVD RAM Allocation Easy

The emulator needs room to expand its virtual disk and write snapshot files. If your drive is nearly full, the emulator will terminate during startup without much explanation. This one catches people out more than you'd think.

  1. Check free space
    On Windows, open File Explorer and check the drive where your SDK lives (usually C:). You need at least 10 GB free. On Mac, go to Apple menu > About This Mac > Storage.
  2. Free up space if needed
    Clear out old downloads, empty the Recycle Bin, or move large files to an external drive. Old AVD system images in ~/.android/avd/ can be several GB each.
  3. Check AVD RAM allocation
    Edit the AVD and look at the RAM setting under Memory and Storage. Set it to at least 2048 MB. Too little RAM causes instability during startup.
Success: At least 10 GB free on the SDK drive and at least 2 GB RAM allocated to the AVD. Relaunch and test.

Advanced Android Emulator Not Launching Fixes

These take longer and require more access to your system. But if you've got through everything above and the emulator still won't start, one of these will be the answer.

7

Enable Hardware Virtualization in BIOS/UEFI Medium

This is the fix that gets overlooked most often, especially after a BIOS update or on a machine that's been reimaged. Virtualization gets disabled silently and nobody notices until the emulator stops working. On Intel systems it's called VT-x. On AMD systems it's AMD-V. Without it, the Android emulator either refuses to launch or performs so badly it appears broken.

  1. Check whether virtualization is currently enabled
    On Windows, open Task Manager, click the Performance tab, select CPU, and look at the bottom right. It will say Virtualization: Enabled or Disabled.
  2. Enter BIOS/UEFI
    Reboot your machine. Press the BIOS key during startup. This is usually Del, F2, or F10 depending on your motherboard or laptop brand. If you miss it, try again.
  3. Find and enable the virtualization setting
    The location varies by manufacturer. Look under Advanced, CPU Configuration, or Security. Enable Intel Virtualization Technology (VT-x) or AMD-V / SVM Mode. On some systems you'll also see a separate VT-d option for I/O virtualization. Enable that too if it's there.
  4. Save and reboot
    Save changes (usually F10) and let the machine boot normally. Check Task Manager again to confirm Virtualization now shows as Enabled.
  5. Relaunch the emulator
    Open Android Studio and try starting the AVD. With virtualization enabled, the emulator should start noticeably faster than before.
Warning: If you're on a Windows machine with Hyper-V enabled (common on Windows 11 Pro), make sure the Android Emulator is configured to use the Windows Hypervisor Platform (WHPX) rather than HAXM, as HAXM and Hyper-V conflict. Check this in SDK Manager under SDK Tools.
Success: Task Manager shows Virtualization: Enabled and the emulator launches without the acceleration warning in the Android Studio event log.
8

Update GPU Drivers Medium

If Solution 4 (switching to Software graphics) stopped the crashing, your GPU drivers are the problem. Software mode is a workaround, not a fix. Here's how to sort the actual cause.

  1. Identify your GPU
    On Windows, right-click the desktop, select Display Settings, then Advanced display. Or open Device Manager and expand Display Adapters.
  2. Download drivers from the manufacturer
    Go directly to the GPU maker's site. For NVIDIA: nvidia.com/drivers. For AMD: amd.com/support. For Intel integrated graphics: intel.com/content/www/us/en/download-center. If you're on a laptop, check your OEM's support page (Dell, HP, Lenovo, etc.) as they sometimes ship customised driver packages.
  3. Install and reboot
    Run the driver installer. A full clean install is better than an update if you've been having persistent issues. Reboot when prompted.
  4. Switch graphics back to Automatic
    Edit the AVD and change Graphics back from Software to Automatic. Relaunch the emulator and test.
Google's own emulator troubleshooting page notes that GPU driver compatibility is one of the most common causes of emulator termination, particularly on systems with integrated Intel graphics or older discrete GPUs.
Success: The emulator runs in Automatic graphics mode without crashing. Rendering should be noticeably smoother than Software mode.
9

Reinstall the Emulator Package and Use Verbose Logging Advanced

If nothing above has worked, the emulator installation itself is probably corrupted. This happens after interrupted updates, failed SDK downloads, or disk errors. A clean reinstall via SDK Manager is the fix. And if you want to know exactly what's failing before you reinstall, the emulator's verbose logging mode will tell you.

  1. Reinstall via SDK Manager
    Go to Tools > SDK Manager > SDK Tools. Untick Android Emulator and click Apply to remove it. Once removed, re-tick it and click Apply again to install a clean copy.
  2. Or launch with verbose logging from the command line
    Open a terminal and navigate to your emulator directory. On Windows this is typically C:\Users\YourName\AppData\Local\Android\Sdk\emulator\. Run:
    emulator -avd YourAVDName -verbose -logcat *:v
    This dumps detailed output to the terminal. Look for lines mentioning HAXM, WHPX, GPU, disk, or snapshot as those pinpoint the failing subsystem.
  3. Target the specific failure
    If the log shows virtualization errors, go back to Solution 7. GPU errors, Solution 8. Snapshot or disk errors, wipe the AVD data again after the reinstall. Path errors, recheck Solution 3.
Success: The emulator reinstall completes without errors in SDK Manager, and a fresh AVD launches cleanly.

Preventing Android Emulator Not Launching in Future

Most of these problems are avoidable. Here's what actually makes a difference, in order of importance:

  1. Keep the emulator and SDK tools updated. Open SDK Manager every couple of weeks and apply any pending updates to Android Emulator, platform-tools, and your system images. Stale components are the most common cause of sudden breakage after an Android Studio update.
  2. Leave at least 10 GB free on your SDK drive. The emulator's virtual disk expands dynamically. If the drive fills up mid-session, you get a crash and a corrupted snapshot. Set a reminder to check disk space if you're on a tight drive.
  3. Cold boot periodically, don't always resume from snapshot. Snapshots are convenient but they accumulate stale state over time. After major SDK updates, do a cold boot to clear it out. Takes an extra 30 seconds and saves you an hour of debugging later.
  4. Create a new AVD rather than patching a broken one. If an AVD starts behaving oddly after an update, don't spend time trying to fix its configuration. Create a fresh one with a clean system image. It takes five minutes and is almost always more reliable.
  5. Check virtualization after BIOS or Windows updates. Both can reset or change hypervisor settings without warning. If the emulator suddenly stops working after a system update, check Task Manager's CPU tab first.
  6. Use Software graphics on older or problematic machines. If your workstation has older GPU drivers and you've had crashes before, just leave Graphics set to Software. The performance hit is real but the stability is worth it for daily development work.

If you're also dealing with other Android development environment issues, our Android Studio troubleshooting guide covers IDE-level problems that sit alongside emulator issues. And if you're seeing broader SDK or build tool failures, the Android SDK repair guide is worth a look too.

Android Emulator Not Launching: Summary

The Android emulator not launching is almost always one of five things: a corrupted AVD snapshot, outdated SDK components, a wrong SDK path, GPU driver incompatibility, or virtualization disabled in BIOS. Start with a cold boot and SDK update. If that doesn't fix it, switch to Software graphics and check your BIOS virtualization settings. Persistent crashes after all of that usually mean a corrupted emulator installation, which a clean reinstall via SDK Manager will fix. For ongoing stability, keep your SDK updated, leave adequate disk space, and verify virtualization settings after any major system update.

The Android emulator not launching problem is fixable in the vast majority of cases without reinstalling Android Studio or touching your project files. Work through the solutions in order and you'll get there.

Frequently Asked Questions

The most common causes are GPU driver incompatibility, corrupted AVD state, or disabled virtualization. Start by cold booting the AVD from Device Manager. If that does not help, change Graphics mode to Software in the AVD settings. If it still crashes, check that virtualization is enabled in your BIOS or UEFI firmware.

This error usually points to GPU, virtualization, or storage problems. Try wiping the AVD data, increasing RAM allocation in the AVD settings, and switching Graphics mode to Software. Also check you have at least 10 GB of free disk space. If it keeps happening, enable virtualization in BIOS and update your graphics drivers from the manufacturer's website.

First, verify the SDK path is correct in Android Studio under Settings > SDK Manager. Update the Android Emulator package and all SDK tools from SDK Manager. Restart Android Studio and your computer. If the emulator still does not appear, create a new AVD using a different system image.

Technically yes, but it will be very slow and may fail to start entirely. Hardware virtualization is what gives the emulator acceptable performance. If virtualization is disabled in BIOS, enable it. If your CPU does not support it at all, use a physical Android device for testing instead.

If the emulator crashes with blank screens, rendering glitches, or repeated terminations, switch Graphics mode to Software in the AVD configuration. If that stops the crashing, your GPU drivers are the problem. Update them from your GPU manufacturer's website (Intel, NVIDIA, or AMD) or your laptop OEM's support page.