Troubleshooting and known issues for Android Emulator and system images

    If you encounter an issue not listed here or are unable to successfully use aworkaround listed here, please .

    To avoid crashes and hangs caused by not having enough free disk space, theemulator checks for sufficient free disk space on startup, and will not startunless at least 2 GB is free. If the emulator fails to start for you, check tosee that you have adequate free disk space.

    Because many security and antivirus software packages work by monitoring everyread and write operation, use of such software can decrease performance of toolslike the Android Emulator.

    Many antivirus packages provide the ability to whitelist specificapplications, which enables these applications to operate without performancedegradation. If you are experiencing poor performance with saving or loading ofAVD snapshots, you may improve this performance by whitelisting the AndroidEmulator application in your antivirus software.

    Some antivirus software may be incompatible with the Android Emulator.

    If you're using Avast software and are having trouble running the AndroidEmulator, try disabling Use nested virtualization when availableand Enable Hardware assisted virtualization in the Avast Troubleshootingsettings. In addition, after Avast hardware virtualization is disabled, ensurethat HAXM is set up properly again with a full re-installation of the latest HAXMfrom the SDK Manager.

    If you are using Android Emulator on older, unsupported versions of Mac OS X(such as 10.9), then you may need to use an older version of HAXM (6.1.2), too.

    A number of external factors can cause the Android Emulator to begin runningslowly after an update. To begin troubleshooting, we recommend thefollowing steps:

    • If you are running Android Emulator on Windows, check to see if you haveinstalled Windows UpdatesKB4013429and.Some users reported improved Android Emulator performance after uninstallingthese updates. Users also reported improved Emulator performance afterinstalling Windows UpdateKB4015438.
    • If you have an Intel GPU (and in particular, the Intel HD 4000), ensure youhave downloaded and installed the latest Intel graphics driver.
    • Try running the emulator using the , , or modes. For more information about configuring graphicsacceleration options on the command line, see.
    • Ensure that your router is not using IPv6 addresses if you do not have anIPv6 connection.
      If you are still experiencing problems with the Android Emulator runningslowly, Report a bug, including thenecessary Android Emulator Details so we can investigate.

    Sometimes, when the emulator asks Windows to account for this full guest memorysize, the request exceeds the current commit limit, which is the total of theavailable physical RAM and pagefile. In this case, Windows can't guarantee thatthe worst-case working set will fit in either physical RAM or pagefile, and theemulator fails to start.

    In typical cases, the amount of hard drive space allocated for the pagefile plusphysical RAM is more than enough for most use cases of the emulator. However, ifyou experience failures to start the emulator because of exceeding the commitlimit, we recommend examining the current commit charge, which can be seen inthe Performance tab in the Windows Task Manager. (To open the Task Manager,press Ctrl+Shift+Esc.)

    You can lower the likelihood of exceeding the commit limit in various ways:

    • Free physical RAM before launching the emulator by closing unused applicationsand files.
    • Use a system managed size for the Windows pagefile, which can more flexiblyand dynamically increase the pagefile size (and therefore the commit limit) inresponse to increased demand from the emulator and other applications.

    For more information on commit charges and why a flexible setting works best,see .