Emulator not working in Android Studio 2.0

Question

I am using Android Studio 2.0 Stable version. Whenever I click on the play button on the device to run it shows starting AVD progress in android studio and after completing it's progress nothing happened.The app window remains as it shown in screenshot and the emulator doesn't start. I can't find a solution for this issue. I have already tried many solutions which I found on the internet, changing HAXM version android SDK update, changed target API's. But nothing works.

Solution 1

Try edit AVD Settings -> Emulated Performance -> Graphics. Set Software - GLES 2.0.

Solution 2

Installing the Android Emulator (marked in to the image) solved my problem. If still you face face problem install API simulator and DHU emulator too. But only AE will solve the issue I guess.

Solution 3

I had the same problem. I just created the AVD with 768 MB RAM and it did run fine!

Solution 4

I had exactly the same issue.

Windows 7 Professional SP1. Installed Android Studio 2.0, new HAXM ver 6.0.1 and updated to all new components like SDK tools 25.1.1.

When started - emulator do not shows up any window. 'emulator.exe' runs in the task manager and eats 25% of CPU.

Deleted all AVDs, re-created new; used AVD Manager directly; used ARM/Atom images (with/without HAXM); tried AVD with different API level - nothing helps.

Reverting to Android SDK Tools 24.4.2 helps - I can run emulator as usual - so, looks this is not the issue of new HAXM 6.0.1.

After day fighting finally got resolution:

I have removed C:Windows\System32\Wbem from system PATH variable.

View more solutions

Comments

[Burhanuddin Rashid]

What is the solution for this if we want the new emulator to work in android studio 2.0?

[Burhanuddin Rashid]

i am not able to find C:Windows\System32\Wbem this path variable my environmental variables

[Burhanuddin Rashid]

Yeah..its working..but emulator is too slow...i am using HAXM x86

[Dmitry]

My PATH variable is very long. Many programs at install adds there something. At some point it starts conflicting. What i did initially is just removed almost everything from PATH. I have created 'run.bat' file with 2 lines like followed: 'set path C:\WINDOWS\system32;C:\WINDOWS' 'D:\Java\android-sdk\tools\emulator.exe -avd Nexus5_API_N -verbose' Then emulator started showing window. Later i have incrementally added parts of PATH back and realized that for my setup problematic was 'C:Windows\System32\Wbem'. In your case can be something else.

[Smokin Joe]

I keep trying to do the same but the Virtual Device manager just bumps it up to 1GB on me automatically. Is the same happening to you?

[joaco1977]

Thanks! great help!!