The Android Emulator lets developers test apps on virtual devices without needing physical hardware, but it can fail without warning. When the “Emulator Process for AVD Has Terminated” error shows up, the AVD either closes seconds after launching or refuses to start at all, stalling any testing you had planned. The fixes below walk through the real causes behind this crash, from low disk space to a corrupted snapshot, so you can get the emulator running again on Windows 10 and Windows 11.

What Causes the Emulator Process for AVD Has Terminated Error
A few underlying issues are typically responsible for this crash.
- Low free disk space on the drive hosting the AVD’s system files, cache, and snapshots
- Missing or outdated Microsoft Visual C++ Redistributable files required by the emulator
- A corrupted AVD snapshot, damaged configuration file, or a stuck leftover emulator process
- Hardware virtualization disabled in BIOS, GPU driver issues, or a Hyper-V conflict
Fix 1: Close Stuck Processes and Check the Log
A leftover emulator process from a previous crash can block the AVD from launching again, and the log confirms the real cause before you try anything else.
- Close Android Studio, open Task Manager, and end any
qemu-systemoremulatorprocesses still running under the Details tab. - In Android Studio, go to
Help > Show Log in Explorerand openidea.log, then check the most recent entries near the crash timestamp for messages about storage, a missing file, or a specific component. - Restart your computer, then launch Android Studio and the AVD again.
Fix 2: Free Up Disk Space
Low disk space on the drive hosting your AVD files is one of the most frequently reported causes of this error.
- Check free space on the drive under
C:\Users\<username>\.android\avd, since the emulator needs room for system images, cache, and snapshot data beyond the base install. - Delete unused AVDs, old snapshots, or unrelated large files to free up space.
- Launch the AVD again once space is freed.
Fix 3: Install or Repair the Visual C++ Redistributable
The emulator depends on files from the Microsoft Visual C++ Redistributable, and a missing or outdated version is a frequent cause of an immediate crash on launch.
- Go to the official Microsoft Visual C++ Redistributable download page.
- Download both
vc_redist.x64.exeandvc_redist.x86.exefor full compatibility. - Run each installer. If a version is already installed, choose Repair when prompted instead of skipping it.
- Restart your PC after installation finishes, then launch the AVD again.
Fix 4: Cold Boot, Wipe, or Recreate the AVD
A corrupted snapshot or damaged AVD configuration file can terminate the emulator process immediately, and resetting the AVD’s state in escalating steps usually resolves it without starting from scratch.
- Open Device Manager, click the three-dot menu next to the crashing AVD, and select Cold Boot Now instead of the regular launch. This skips the saved snapshot, which is often the actual source of corruption.
- If that doesn’t help, select Wipe Data from the same menu to reset the AVD’s stored state while keeping its configuration.
- If the error persists, delete the AVD entirely and click Create Device to set it up again, choosing a system image with the same or a newer API level.
Fix 5: Update or Reinstall Emulator and SDK Components
Outdated or corrupted emulator and SDK files can prevent the AVD from starting, and updating or reinstalling them clears out the damaged files.
- Go to
Tools > SDK Manager > SDK Toolsand update Android Emulator, Android SDK Platform-Tools, and Android SDK Build-Tools if newer versions are listed. - If the AVD still won’t launch, uncheck Android Emulator in the same list to uninstall it, apply the change, then recheck and apply again to reinstall it fresh.
- Restart Android Studio and launch the AVD.
Fix 6: Switch Graphics Rendering and Update the GPU Driver
Graphics rendering conflicts and outdated GPU drivers are a common cause of the emulator terminating right after it opens.
- Open Device Manager, edit the affected AVD, and under Emulated Performance switch the Graphics setting between Hardware and Software rendering to test which one launches successfully.
- Update your graphics driver from the manufacturer’s site (NVIDIA, AMD, or Intel), or through Device Manager > Display adapters on Windows.
- Restart your computer and launch the AVD again.
Fix 7: Enable Hardware Virtualization and Resolve Hyper-V Conflicts
Hardware virtualization must be active for the emulator to run, and Windows features like Hyper-V or Device Guard can block it even when it’s enabled in BIOS.
- Restart your PC and enter BIOS/UEFI settings (usually
Del,F2, orF10during boot). - Locate the virtualization setting, often labeled Intel VT-x, AMD-V, or SVM Mode, and set it to Enabled.
- Save changes and reboot.
- On Windows, open
Turn Windows features on or offand uncheck Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform if you don’t need them for other tools. - Open Command Prompt as Administrator and run
bcdedit /set hypervisorlaunchtype off, then restart.
If Hyper-V is required for other software like WSL2 or Docker, use Android Emulator’s Hyper-V-based acceleration instead of disabling it entirely, since newer emulator versions support running alongside Hyper-V.
The “Emulator Process for AVD Has Terminated” error usually comes down to a handful of causes: low disk space, a missing Visual C++ Redistributable, a corrupted AVD snapshot, outdated components, graphics conflicts, or disabled virtualization. Working through the fixes above in order, starting with the quickest checks like closing stuck processes and freeing up space, resolves the issue for most setups without needing a full reinstall of Android Studio.
Frequently Asked Questions
Why does my Android emulator crash right after opening?
This usually happens when the AVD’s drive is low on space, the Visual C++ Redistributable is missing or outdated, or the AVD’s saved snapshot has become corrupted, all of which stop the emulator process from staying active after launch.
Does antivirus software cause this error?
Some antivirus and endpoint protection tools block the emulator’s virtualization access. Temporarily disabling real-time protection or adding an exclusion for the Android SDK folder can confirm if this is the cause.
Do I need to delete all my AVDs to fix this?
No. You only need to delete and recreate the specific AVD that’s crashing. Other virtual devices on the same system are not affected.
Why does cold booting fix the emulator when a normal launch doesn’t?
A normal launch tries to resume from the AVD’s saved snapshot, and if that snapshot is corrupted, the process crashes immediately. Cold boot skips the snapshot entirely and starts the emulator fresh, which bypasses the corrupted data.
Can outdated Android Studio itself cause this error?
Yes. An outdated IDE version can ship with emulator or SDK Tools compatibility issues that were already fixed in later releases. Updating Android Studio through Help > Check for Updates rules this out alongside updating the emulator components separately.
