1

EDIT : This issue has been resolved, please see https://stackoverflow.com/a/61048046/5522344 . It needs Windows 10 1903 or above.

I am trying to run Android Emulator on Windows 10 1803, as per the post here.

The requirements are

  1. AMD Ryzen processors - mine is Ryzen 1600
  2. Virtualization enabled - yes checked that
  3. Hyper-V turned off - yes
  4. The emulator version is 29.2.3 or later

I can run the emulator using the Hyper-V enabled.

But I am unable to run the emulator after going through the mentioned steps.

  • This is the Android Studio version

My Android Studio version

  • Current Settings as per the post settings

  • Emulator Version emulator

  • Success message after installing the driver result

  • Emulator fails to run issue

Can anyone point out what I missed here?

Doc
  • 10,831
  • 3
  • 39
  • 63
  • Not sure, did you make sure windows sandbox is unchecked? Also why are you getting two service name: gvm when you run that bat? – Richard Dapice Oct 30 '19 at 20:55
  • This issue has been solved. I cannot delete this post. The only issue was version conflict which is now resolved. – Doc Apr 14 '20 at 20:59

2 Answers2

2

IMHO It is not the right android version:

https://github.com/google/android-emulator-hypervisor-driver-for-amd-processors#download-and-install

Android Emulator Hypervisor Driver for AMD Processors is released through android-studio. However, only Android Studio with version 4.0 canary 5 or above can both download and install/update the driver. Otherwise, the Android Studio will only download the driver package without performing installation. In the latter case, users are required to install the driver manually.

Looks like android-studio 3.2.1 will only download the driver.

The link to download preview versions is:

https://developer.android.com/studio/preview

I tried with 4.1 CANARY 5 and it works

Sanhaji Omar
  • 192
  • 1
  • 8
  • 1
    This issue has been solved. I cannot delete this post. The only issue was version conflict which is now resolved. – Doc Apr 14 '20 at 21:00
0

The best you can do is filing a bug to google. This is not a suitable question to address at Stackoverflow. - from Author of the Software.