IssueTracker

Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information:

1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.

For more information on what’s needed and how to obtain this information please read the guide at https://developer.android.com/studio/report-bugs#emulator-bugs.

stackoverflow
https://stackoverflow.com/questions/68373280/android-studio-emulator-is-not-working-on-windows-11-using-whpx
reddit
https://www.reddit.com/r/androiddev/comments/ovz4g2/android_studio_emulator_in_windows_11/

steps to reproduce:
upgrade windows 11
have virtual machine feature enabled (or hyper v) { in my case i use for windows sub system linux wsl}
other things are usual run emulator from android studio and get error

emulator info:
Name: Pixel_111
CPU/ABI: Google Play Intel Atom (x86)
Path: C:\Users\7abhi\.android\avd\Pixel_111.avd
Target: google_apis_playstore [Google Play] (API level 30)
Skin: 1080x2280
SD Card: 512M
fastboot.chosenSnapshotFile:
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: pixel_4
hw.lcd.width: 1080
hw.initialOrientation: Portrait
image.androidVersion.api: 30
tag.id: google_apis_playstore
hw.mainKeys: no
hw.camera.front: emulated
avd.ini.displayname: Pixel_111
hw.gpu.mode: auto
hw.ramSize: 1536
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.cpu.ncore: 4
hw.keyboard: yes
hw.sensors.proximity: yes
hw.dPad: no
hw.lcd.height: 2280
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
skin.path.backup: C:\Users\7abhi\AppData\Local\Android\Sdk\skins\pixel_4
hw.audioInput: yes
image.sysdir.1: system-images\android-30\google_apis_playstore\x86\
showDeviceFrame: no
hw.camera.back: virtualscene
AvdId: Pixel_111
hw.lcd.density: 440
hw.arc: false
hw.device.hash2: MD5:6b5943207fe196d842659d2e43022e20
fastboot.forceChosenSnapshotBoot: no
fastboot.forceFastBoot: yes
hw.trackBall: no
hw.battery: yes
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
disk.dataPartition.size: 6442450944
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes



PS C:\Users\7abhi\AppData\Local\Android\Sdk\emulator> .\emulator -avd Pixel_111 -verbose -show-kernel
emulator: Android emulator version 30.8.4.0 (build_id 7600983) (CL:N/A)
emulator: Found AVD name 'Pixel_111'
emulator: Found AVD target architecture: x86
emulator: argv[0]: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\emulator.exe'; program directory: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator'
emulator:  Found directory: C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\
emulator: emuDirName: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator'
emulator:  Found directory: C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\
emulator: Probing for C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\kernel-ranchu-64: file exists
emulator: try dir C:\Users\7abhi\AppData\Local\Android\Sdk\emulator
emulator: Trying emulator path 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe'
emulator: Found target-specific 64-bit emulator binary: C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe
emulator: Adding library search path: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64'
emulator: Adding library search path: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\gles_angle'
emulator: Adding library search path: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\gles_angle9'
emulator: Adding library search path: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\gles_angle11'
emulator: Adding library search path: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\gles_swiftshader'
emulator: Adding library search path for Qt: 'C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\qt\lib'
emulator: Silencing all qWarning(); use qCWarning(...) instead: QT_LOGGING_RULES=default.warning=false
emulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\lib64\qt\plugins
emulator: Setting Qt to use software OpenGL: QT_OPENGL=software
emulator: Setting QML to use software QtQuick2D: QMLSCENE_DEVICE=softwarecontext
emulator: Overriding pre-existing bad Qt high dpi settings...
emulator: Quoted param: [C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe]
emulator: Quoted param: [-avd]
emulator: Quoted param: [Pixel_111]
emulator: Quoted param: [-verbose]
emulator: Quoted param: [-show-kernel]
emulator: Running :C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe
emulator: qemu backend: argv[00] = "C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe"
emulator: qemu backend: argv[01] = "-avd"
emulator: qemu backend: argv[02] = "Pixel_111"
emulator: qemu backend: argv[03] = "-verbose"
emulator: qemu backend: argv[04] = "-show-kernel"
emulator: Concatenated backend parameters:
 C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe -avd Pixel_111 -verbose -show-kernel
emulator: autoconfig: -skin 1080x2280
emulator: autoconfig: -skindir (null)
emulator: autoconfig: -kernel C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\kernel-ranchu-64
emulator: Target arch = 'x86'
emulator: Auto-config: -qemu -cpu qemu32
emulator: Auto-detect: Kernel image requires new device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: autoconfig: -ramdisk C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\ramdisk.img
emulator: Using initial system image: C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\system.img
emulator: Using initial vendor image: C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\vendor.img
emulator: autoconfig: -data C:\Users\7abhi\.android\avd\Pixel_111.avd\userdata-qemu.img
emulator: autoconfig: -initdata C:\Users\7abhi\.android\avd\Pixel_111.avd\userdata.img
emulator: autoconfig: -cache C:\Users\7abhi\.android\avd\Pixel_111.avd\cache.img
emulator: autoconfig: -sdcard C:\Users\7abhi\.android\avd\Pixel_111.avd\sdcard.img
emulator: Increasing RAM size to 2048MB
emulator: VM heap size 256MB is below hardware specified minimum of 512MB,setting it to that value
emulator: System image is read only
emulator: Found 4 DNS servers: 192.168.0.1 fec0:0:0:ffff::1 fec0:0:0:ffff::2 fec0:0:0:ffff::3
emulator: VERBOSE: FeatureControlImpl.cpp:172: WARNING: unexpected system image feature string, emulator might not function correctly, please try updating the emulator.

emulator: VERBOSE: FeatureControlImpl.cpp:175: Unexpected feature list:

emulator: VERBOSE: FeatureControlImpl.cpp:177: Vulkan
emulator: VERBOSE: FeatureControlImpl.cpp:179:

emulator: VERBOSE: System.cpp:3003: querying file version info API...
emulator: VERBOSE: System.cpp:3011: found kernelbase.dll
emulator: VERBOSE: System.cpp:3019: GetFileVersionInfoSizeW found. On Windows 10?
emulator: VERBOSE: System.cpp:3028: GetFileVersionInfoW found. On Windows 10?
emulator: VERBOSE: System.cpp:3058: VerQueryValueW found. Can query file versions
emulator: VERBOSE: System.cpp:3081: queryFileVersionInfo: path not found: amdvlk64.dll
emulator: VERBOSE: System.cpp:3003: querying file version info API...
emulator: VERBOSE: System.cpp:3081: queryFileVersionInfo: path not found: amdvlk32.dll
emulator: VERBOSE: System.cpp:3003: querying file version info API...
emulator: found magic skin width=1080 height=2280 bpp=16

emulator: Checking whether Windows Hypervisor Platform (WHPX) is available.
emulator: WinHvPlatform.dll found. Looking for WHvGetCapability...
emulator: WHvGetCapability found. Querying WHPX capabilities...
emulator: WHPX (10.0.22000) is installed and usable.
emulator: CPU Acceleration: working
emulator: CPU Acceleration status: Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22000) is installed and usable.
handleCpuAcceleration: feature check for hvf
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'qemu.cmdline' = 'androidboot.logcat=*:V androidboot.consolepipe=qemu_pipe,pipe:logcat'
emulator: Adding boot property: 'qemu.logcat' = 'start'
emulator: GPU emulation enabled using 'host' mode
emulator: Initializing hardware OpenGLES emulation support
emulator: VERBOSE: MultiDisplay.cpp:341: create display 0
emulator: VERBOSE: MultiDisplay.cpp:435: setDisplayPose 0 x 0 y 0 w 1080 h 2280 dpi 0
added library vulkan-1.dll
emulator: Found 4 DNS servers: 192.168.0.1 fec0:0:0:ffff::1 fec0:0:0:ffff::2 fec0:0:0:ffff::3
Content of hardware configuration file:
  hw.cpu.arch = x86
  hw.cpu.model = qemu32
  hw.cpu.ncore = 4
  hw.ramSize = 2048
  hw.screen = multi-touch
  hw.mainKeys = false
  hw.trackBall = false
  hw.keyboard = true
  hw.keyboard.lid = false
  hw.keyboard.charmap = qwerty2
  hw.dPad = false
  hw.rotaryInput = false
  hw.gsmModem = true
  hw.gps = true
  hw.battery = true
  hw.accelerometer = true
  hw.gyroscope = true
  hw.audioInput = true
  hw.audioOutput = true
  hw.sdCard = true
  hw.sdCard.path = C:\Users\7abhi\.android\avd\Pixel_111.avd\sdcard.img
  disk.cachePartition = true
  disk.cachePartition.path = C:\Users\7abhi\.android\avd\Pixel_111.avd\cache.img
  disk.cachePartition.size = 66m
  test.quitAfterBootTimeOut = -1
  test.delayAdbTillBootComplete = 0
  test.monitorAdb = 0
  hw.lcd.width = 1080
  hw.lcd.height = 2280
  hw.lcd.depth = 16
  hw.lcd.density = 440
  hw.lcd.backlight = true
  hw.lcd.vsync = 60
  hw.gltransport = pipe
  hw.gltransport.asg.writeBufferSize = 1048576
  hw.gltransport.asg.writeStepSize = 4096
  hw.gltransport.asg.dataRingSize = 32768
  hw.gltransport.drawFlushInterval = 800
  hw.displayRegion.0.1.xOffset = -1
  hw.displayRegion.0.1.yOffset = -1
  hw.displayRegion.0.1.width = 0
  hw.displayRegion.0.1.height = 0
  hw.displayRegion.0.2.xOffset = -1
  hw.displayRegion.0.2.yOffset = -1
  hw.displayRegion.0.2.width = 0
  hw.displayRegion.0.2.height = 0
  hw.displayRegion.0.3.xOffset = -1
  hw.displayRegion.0.3.yOffset = -1
  hw.displayRegion.0.3.width = 0
  hw.displayRegion.0.3.height = 0
  hw.display1.width = 0
  hw.display1.height = 0
  hw.display1.density = 0
  hw.display1.xOffset = -1
  hw.display1.yOffset = -1
  hw.display1.flag = 0
  hw.display2.width = 0
  hw.display2.height = 0
  hw.display2.density = 0
  hw.display2.xOffset = -1
  hw.display2.yOffset = -1
  hw.display2.flag = 0
  hw.display3.width = 0
  hw.display3.height = 0
  hw.display3.density = 0
  hw.display3.xOffset = -1
  hw.display3.yOffset = -1
  hw.display3.flag = 0
  hw.gpu.enabled = true
  hw.gpu.mode = host
  hw.initialOrientation = Portrait
  hw.camera.back = virtualscene
  hw.camera.front = emulated
  vm.heapSize = 512
  hw.sensors.light = true
  hw.sensors.pressure = true
  hw.sensors.humidity = true
  hw.sensors.proximity = true
  hw.sensors.magnetic_field = true
  hw.sensors.magnetic_field_uncalibrated = true
  hw.sensors.gyroscope_uncalibrated = true
  hw.sensors.orientation = true
  hw.sensors.temperature = true
  hw.sensor.hinge = true
  hw.sensor.hinge.count = 0
  hw.sensor.hinge.type = 0
  hw.sensor.hinge.sub_type = 0
  hw.sensor.hinge.fold_to_displayRegion.0.1_at_posture = 1
  hw.sensor.roll = false
  hw.sensor.roll.count = 0
  hw.sensor.roll.resize_to_displayRegion.0.1_at_posture = 6
  hw.sensor.roll.resize_to_displayRegion.0.2_at_posture = 6
  hw.sensor.roll.resize_to_displayRegion.0.3_at_posture = 6
  hw.sensors.heart_rate = false
  hw.useext4 = true
  hw.arc = false
  hw.arc.autologin = false
  kernel.path = C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\kernel-ranchu-64
  kernel.newDeviceNaming = yes
  kernel.supportsYaffs2 = no
  disk.ramdisk.path = C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\ramdisk.img
  disk.systemPartition.initPath = C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\system.img
  disk.systemPartition.size = 2331m
  disk.vendorPartition.initPath = C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\vendor.img
  disk.vendorPartition.size = 800m
  disk.dataPartition.path = C:\Users\7abhi\.android\avd\Pixel_111.avd\userdata-qemu.img
  disk.dataPartition.size = 6g
  disk.encryptionKeyPartition.path = C:\Users\7abhi\.android\avd\Pixel_111.avd\encryptionkey.img
  PlayStore.enabled = true
  avd.name = Pixel_111
  avd.id = Pixel_111
  fastboot.forceColdBoot = false
  android.sdk.root = C:\Users\7abhi\AppData\Local\Android\Sdk
  android.avd.home = C:\Users\7abhi\.android\avd
.
QEMU options list:
emulator: argv[00] = "C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe"
emulator: argv[01] = "-dns-server"
emulator: argv[02] = "192.168.0.1,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3"
emulator: argv[03] = "-mem-path"
emulator: argv[04] = "C:\Users\7abhi\.android\avd\Pixel_111.avd\snapshots\default_boot\ram.img"
emulator: argv[05] = "-mem-file-shared"
emulator: argv[06] = "-serial"
emulator: argv[07] = "con:"
emulator: argv[08] = "-device"
emulator: argv[09] = "goldfish_pstore,addr=0xff018000,size=0x10000,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\data\misc\pstore\pstore.bin"
emulator: argv[10] = "-cpu"
emulator: argv[11] = "android64"
emulator: argv[12] = "-enable-whpx"
emulator: argv[13] = "-smp"
emulator: argv[14] = "cores=4"
emulator: argv[15] = "-m"
emulator: argv[16] = "2048"
emulator: argv[17] = "-lcd-density"
emulator: argv[18] = "440"
emulator: argv[19] = "-nodefaults"
emulator: argv[20] = "-kernel"
emulator: argv[21] = "C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\kernel-ranchu-64"
emulator: argv[22] = "-initrd"
emulator: argv[23] = "C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\ramdisk.img"
emulator: argv[24] = "-drive"
emulator: argv[25] = "if=none,index=0,id=system,if=none,file=C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\system.img,read-only"
emulator: argv[26] = "-device"
emulator: argv[27] = "virtio-blk-pci,drive=system,modern-pio-notify"
emulator: argv[28] = "-drive"
emulator: argv[29] = "if=none,index=1,id=cache,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\cache.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
emulator: argv[30] = "-device"
emulator: argv[31] = "virtio-blk-pci,drive=cache,modern-pio-notify"
emulator: argv[32] = "-drive"
emulator: argv[33] = "if=none,index=2,id=userdata,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\userdata-qemu.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
emulator: argv[34] = "-device"
emulator: argv[35] = "virtio-blk-pci,drive=userdata,modern-pio-notify"
emulator: argv[36] = "-drive"
emulator: argv[37] = "if=none,index=3,id=encrypt,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\encryptionkey.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
emulator: argv[38] = "-device"
emulator: argv[39] = "virtio-blk-pci,drive=encrypt,modern-pio-notify"
emulator: argv[40] = "-drive"
emulator: argv[41] = "if=none,index=4,id=vendor,if=none,file=C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\vendor.img,read-only"
emulator: argv[42] = "-device"
emulator: argv[43] = "virtio-blk-pci,drive=vendor,modern-pio-notify"
emulator: argv[44] = "-drive"
emulator: argv[45] = "if=none,index=5,id=sdcard,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\sdcard.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576"
emulator: argv[46] = "-device"
emulator: argv[47] = "virtio-blk-pci,drive=sdcard,modern-pio-notify"
emulator: argv[48] = "-netdev"
emulator: argv[49] = "user,id=mynet"
emulator: argv[50] = "-device"
emulator: argv[51] = "virtio-net-pci,netdev=mynet"
emulator: argv[52] = "-device"
emulator: argv[53] = "virtio-rng-pci"
emulator: argv[54] = "-show-cursor"
emulator: argv[55] = "-device"
emulator: argv[56] = "virtio_input_multi_touch_pci_1"
emulator: argv[57] = "-device"
emulator: argv[58] = "virtio_input_multi_touch_pci_2"
emulator: argv[59] = "-device"
emulator: argv[60] = "virtio_input_multi_touch_pci_3"
emulator: argv[61] = "-device"
emulator: argv[62] = "virtio_input_multi_touch_pci_4"
emulator: argv[63] = "-device"
emulator: argv[64] = "virtio_input_multi_touch_pci_5"
emulator: argv[65] = "-device"
emulator: argv[66] = "virtio_input_multi_touch_pci_6"
emulator: argv[67] = "-device"
emulator: argv[68] = "virtio_input_multi_touch_pci_7"
emulator: argv[69] = "-device"
emulator: argv[70] = "virtio_input_multi_touch_pci_8"
emulator: argv[71] = "-device"
emulator: argv[72] = "virtio_input_multi_touch_pci_9"
emulator: argv[73] = "-device"
emulator: argv[74] = "virtio_input_multi_touch_pci_10"
emulator: argv[75] = "-device"
emulator: argv[76] = "virtio_input_multi_touch_pci_11"
emulator: argv[77] = "-device"
emulator: argv[78] = "virtio-keyboard-pci"
emulator: argv[79] = "-L"
emulator: argv[80] = "C:\Users\7abhi\AppData\Local\Android\Sdk\emulator/lib/pc-bios"
emulator: argv[81] = "-soundhw"
emulator: argv[82] = "hda"
emulator: argv[83] = "-vga"
emulator: argv[84] = "none"
emulator: argv[85] = "-append"
emulator: argv[86] = "no_timer_check clocksource=pit console=ttyS0,38400 cma=294M@0-4G ndns=4 mac80211_hwsim.channels=2 loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 printk.devkmsg=on qemu=1 androidboot.hardware=ranchu androidboot.serialno=EMULATOR30X8X4X0 qemu.gles=1 qemu.settings.system.screen_off_timeout=2147483647 qemu.encrypt=1 qemu.vsync=60 qemu.gltransport=pipe qemu.gltransport.drawFlushInterval=800 qemu.opengles.version=131072 qemu.dalvik.vm.heapsize=512m qemu.camera_protocol_ver=1 androidboot.vbmeta.size=6144 androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.digest=25857a23ca496649ae6cb48216f3550520f596e03f8de9cd17fd18b308317287 androidboot.boot_devices=pci0000:00/0000:00:03.0 qemu.wifi=1 qemu.hwcodec.avcdec=2 qemu.hwcodec.vpxdec=2 android.qemud=1 qemu.avd_name=Pixel_111"
emulator: argv[87] = "-android-hw"
emulator: argv[88] = "C:\Users\7abhi\.android\avd\Pixel_111.avd\hardware-qemu.ini"
Concatenated QEMU options:
 C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe -dns-server 192.168.0.1,fec0:0:0:ffff::1,fec0:0:0:ffff::2,fec0:0:0:ffff::3 -mem-path C:\Users\7abhi\.android\avd\Pixel_111.avd\snapshots\default_boot\ram.img -mem-file-shared -serial con: -device goldfish_pstore,addr=0xff018000,size=0x10000,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\data\misc\pstore\pstore.bin -cpu android64 -enable-whpx -smp cores=4 -m 2048 -lcd-density 440 -nodefaults -kernel C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\kernel-ranchu-64 -initrd C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\ramdisk.img -drive if=none,index=0,id=system,if=none,file=C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\system.img,read-only -device virtio-blk-pci,drive=system,modern-pio-notify -drive if=none,index=1,id=cache,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\cache.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=cache,modern-pio-notify -drive if=none,index=2,id=userdata,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\userdata-qemu.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=userdata,modern-pio-notify -drive if=none,index=3,id=encrypt,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\encryptionkey.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=encrypt,modern-pio-notify -drive if=none,index=4,id=vendor,if=none,file=C:\Users\7abhi\AppData\Local\Android\Sdk\system-images\android-30\google_apis_playstore\x86\\vendor.img,read-only -device virtio-blk-pci,drive=vendor,modern-pio-notify -drive if=none,index=5,id=sdcard,if=none,file=C:\Users\7abhi\.android\avd\Pixel_111.avd\sdcard.img.qcow2,overlap-check=none,cache=unsafe,l2-cache-size=1048576 -device virtio-blk-pci,drive=sdcard,modern-pio-notify -netdev user,id=mynet -device virtio-net-pci,netdev=mynet -device virtio-rng-pci -show-cursor -device virtio_input_multi_touch_pci_1 -device virtio_input_multi_touch_pci_2 -device virtio_input_multi_touch_pci_3 -device virtio_input_multi_touch_pci_4 -device virtio_input_multi_touch_pci_5 -device virtio_input_multi_touch_pci_6 -device virtio_input_multi_touch_pci_7 -device virtio_input_multi_touch_pci_8 -device virtio_input_multi_touch_pci_9 -device virtio_input_multi_touch_pci_10 -device virtio_input_multi_touch_pci_11 -device virtio-keyboard-pci -L C:\Users\7abhi\AppData\Local\Android\Sdk\emulator/lib/pc-bios -soundhw hda -vga none -append "no_timer_check clocksource=pit console=ttyS0,38400 cma=294M@0-4G ndns=4 mac80211_hwsim.channels=2 loop.max_part=7 ramoops.mem_address=0xff018000 ramoops.mem_size=0x10000 memmap=0x10000$0xff018000 printk.devkmsg=on qemu=1 androidboot.hardware=ranchu androidboot.serialno=EMULATOR30X8X4X0 qemu.gles=1 qemu.settings.system.screen_off_timeout=2147483647 qemu.encrypt=1 qemu.vsync=60 qemu.gltransport=pipe qemu.gltransport.drawFlushInterval=800 qemu.opengles.version=131072 qemu.dalvik.vm.heapsize=512m qemu.camera_protocol_ver=1 androidboot.vbmeta.size=6144 androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.digest=25857a23ca496649ae6cb48216f3550520f596e03f8de9cd17fd18b308317287 androidboot.boot_devices=pci0000:00/0000:00:03.0 qemu.wifi=1 qemu.hwcodec.avcdec=2 qemu.hwcodec.vpxdec=2 android.qemud=1 qemu.avd_name=Pixel_111" -android-hw C:\Users\7abhi\.android\avd\Pixel_111.avd\hardware-qemu.ini
emulator: Android qemu version 30.8.4.0 (build_id 7600983) (CL:N/A)

emulator: Starting QEMU main loop
Failed to open /qemu.conf, err: 2
emulator: Adding boot property: 'ro.opengles.version' = '131072'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'front'
emulator: Adding boot property: 'qemu.adb.secure' = '1'
emulator: Adding boot property: 'dalvik.vm.heapsize' = '512m'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '0'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '440'
C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: WHPX: Failed to setup partition, hr=c0350005
C:\Users\7abhi\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: failed to initialize WHPX: Invalid argument
emulator: Done with QEMU main loop

PS C:\Users\7abhi> adb shell top
adb.exe: no devices/emulators found
PS C:\Users\7abhi>

This looks like a Microsoft bug and we are contacting Microsoft to get a fix. Before that, I think you will have to disable hyper-v for the moment.

This issue suggests that upgrading the underlying QEMU version might be one way to fix it:
https://issuetracker.google.com/issues/202515259

We are still waiting for Microsoft to answer the question. Since my Ryzen/Intel Win11 works fine, it is better to know the root cause before we decide to upgrade QEMU, which would take quite some time.

Just to clarify, please note the preconditions to reproduce the problem:

1. Hardware virtualization enabled in UEFI (either on Intel or AMD).

2. Hyper-V feature enabled in Windows. This is used by WSL2, among others, and not installed by default. It’s commonly used by software devs, though.

3. The emulator must be run in WHPX mode. On Intel it’s run in HAXM mode by default, which is why it’s AMD users who usually report this problem. HAXM doesn’t support AMD.

This issue virtually prevents normal Android Studio usage in many Ryzen-based development environments. Maybe it deserves a higher priority.

Please ensure that you test this scenario with WSL2 enabled. This is pretty normal for software development on a Windows machine nowadays, so this would potentially block all AMD Ryzen users on Windows 11 to not be able to use the emulator. Not sure why this is only P3...

This issue has also affected the 21xxx Windows 10 insider dev builds for a long time, though this is less likely to be an issue going forward, since with Windows 11 out, it's unclear if and when Microsoft will choose to elevate the 21xxx Windows 10 insider builds to production.

Furthermore, Windows 11 installations that have enabled any of the following features:

Virtualization-Based Security (VBS)
Hypervisor-Protected Code Integrity (HVCI)
Windows Sandbox
Windows Credential Guard

are also affected, even if WSL2 and Hyper-V are not used explicitly (the AMD Hypervisor Driver that comes with the emulator cannot be used if the Windows hypervisor has been enabled implicitly by virtualization-based security features).

With Microsoft's increasing push to enable VBS and HVCI by default in new Windows 11 devices, this problem will only get more common.

Turn off core isolation in windows security this will fix your problem

Turning off core isolation in Windows security sounds like a very bad thing to do if you are conscious about security. We have to remember that this used to work in Windows 10 with the default security features. So this should work on Windows 11 also without compromising the security.  

I checked the "Core Isolation" security setting (I have to admit, I didn't know this security setting even existed). It was actually already turned Off by default on my PC. The emulator still doesn't work with the "Core Isolation" turned off. I turned it On, still doesn't work. So I don't think the setting affects the problem.
As mentioned by others, the emulator worked fine with Windows 10 (same PC).

I have a 2018 Dell XPS 9570 laptop having 8th Generation Intel Core i7-8750H 6-Core Processor, and the emulator works fine with Windows 11 and Hyper-V, WSL2 and Windows Hypervisor Platform enabled.
While on my PC having AMD Ryzen 9 5900X 12-Core Processor, it doesn't work on Windows 11 but worked on Windows 10. I am getting the exact error mentioned by the author of this issue on Windows 11.

So it seems the problem may affect AMD processors only. Note that this is not related to HAXM. Both the "Android Emulator Hypervisor driver for AMD Processors" and "Intel x86 Emulator Accelerator (HAXM)" don't work when Hyper-V is enabled. I have read reports by other users saying they have the same problem with newer generations of Intel processor. So it could be that my 8th Gen Intel processor on my laptop is not affected by this issue.

Reply to #8:
For AMD users, WHPX is not the only option we support. We also support Android Emulator Hypervisor Driver for AMD Processors (which is AMD's "HAXM").

Reply to #11:
We were told by Microsoft that WHPX should be installed silently too whenever these security features get Hyper-V silently. This should be sufficient to run emulator. Of course, only when they do it right.

Reply to #14:
We saw reports for both Intel and AMD processors. The issue may impact AMD more but we do not have enough data as proof.

Right now I did not get any feedback from Microsoft regarding the issue. But one of their developers was able to reproduce the same issue on Surface Laptop Studio.

I am able to reproduce this on an Intel i7-1185g7.  It's being caused by the XSAVE disable code in the WHPX API integration -- target/i386/whpx-all.c -- commenting out this line appears to make it work:
https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/target/i386/whpx-all.c#1768

Anyway, hopefully this is helpful to someone...  I had fun figuring it out.  :-)

PS - For clarity, the release version of the emulator worked prior to the Windows 11 upgrade on the same computer.  So it seems like something changed/broke in the WHPX APIs.  (I'm not blaming the Android Emulator)

Same error here.
I use WSL2 + Android emulators for development, they worked fine at Windows 10, but now with Windows 11 emulators wont start, the only fix was turning off the "Virtual Machine Platform", but then with that OFF the WSL2 wont work, so its not a solution.

Also checked the "Core isolation" and as comment #14 said, I also had it off and still didn't worked, so that's not a fix.

As mentioned before by the previous comments, I also have AMD processor.
Processor: Ryzen 7 5800H

Could the severity and priority of this issue be increased? There seems to be a consensus that Android Emulator is broken on Windows 11. And now with Windows 11 released outside of beta, many more users will hit this error.

Reply to #19:
It seems that "Core Isolation" is one of several Windows features that break the Android emulator. Basically any feature that uses the Windows hypervisor (This includes Hyper-V, WSL2, Core Isolation, Virtual Machine Platform, Windows Hypervisor Platform, etc) will break the emulator. Turning off all these features, you can use either "Android Emulator Hypervisor driver for AMD Processors" or "Intel x86 Emulator Accelerator (HAXM)" to run the emulator instead of the Windows hypervisor with which they are mutually exclusive (you can't have 2 hypervisors running at the same time).

So turning off "Core Isolation" solves the problem only if you also turn off other Windows features like Hyper-V,WSL2, etc (Which is not actually a solution and is basically what this issue is about).

Reply to #20:
I agree with that. The severity and priority of this issue should be increased.

we should also open a ticket or issue at Microsoft if the error is from their side

By the way, probably you guys are dealing with this with your own ways, but in my case the only way I found to keep working was using my real phone for testing the apps (through adb), and using WSL2 in the pc

Reply to #18:
Worked for me also!  THANKS!

Reply to #18:
Could you share patched qemu-system-x86_64.exe, please?

Thanks a lot.

Reply to #27:
Thank you, I can confirm that this patched version perfectly works with all W11 Hyper-V & Core Isolation features turned on.

Reply to #27:

Thanks for the binaries finally the emulator is working on AMD Ryzen 5950 with WSL2 under Windows 11.

Note: They require to update Android Emulator (30.9.5) first which is not automatically offered when using the Android SDK Manager of Visual Studio

Reply to #29 (from author of #18) -

Just a note that I hope is helpful:  You can get the 30.9.5 update for the Emulator with the Visual Studio Android SDK Manager by clicking the gear icon, selecting "Repository" -> "Full List (Unsupported)".  Once you do that, you should see available updates for the Android Emulator component to get from 30.8.4 to 30.9.5.

I'm glad to see that this change is also working for people with AMD CPUs...  I don't have one so I couldn't test it.  :-)

Awesome, thanks #27 and #18 !!
Now works fine for me in Windows 11, AMD Ryzen 7 5800H

thanks #27 and #18，Works in Windows 11, AMD Ryzen 7 5800X

While I applaud and think it's fantastic that this issue was resolved by #27 and #18 (hence by the community and thanks to open source!), I think it would be better if Google would be able to make the same fix and distribute an official patched emulator to us.

Google, any updates on this issue from your side? Can you apply the same fix and ship it through Android Studio?

Update:
Microsoft confirmed the issue was related to xsave. And we are working on emulator update based on Microsoft's suggestions.

thanks #27 and #18 works on Ryzen 5950 win11

Thanks #29, #27 and #18. Your suggestions worked on a Windows 11 with AMD 5800H. For Visual Studio 2019 / Xamarin users: the files kindly shared by #27 must be placed in the following folder:

C:\Program Files (x86)\Android\android-sdk\emulator\qemu\windows-x86_64

Please, do that *after* updating your emulator to 30.9.5, since the installer might try to "fix" your installation and get rid of any manually copied files.

#38 indeed, how they're putting android emulator being borked on the latest Windows (Ryzen, Hyper V is common and common among developers respectively) on P2 is beyond me. Shouldn't this be their first priority?

The fix from #27 also worked for me, interestingly enough on my i9-11980HK laptop running Windows 11 and WSL 2 w/Ubuntu 20. Every time I would try to start an emulator in Android Studio, qemu would just freeze. I downloaded the files and extracted them to the android sdk folder, which in my case was:
C:\Users\USERNAME\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64

It immediately started working. Thank you so much, hopefully this fix will get baked in at some point.

#40 perhaps you aren't using HAXM on intel? afaik HAXM isn't affected by this issue.

Hi,

Anyone can try emulator 31.1.2 and see if it fixes the issue. The fix is basically the same as #18 but only remove "disable xsave" on Windows 11.

(apologies for repost, I was in the wrong Google account)

Hi, I have been running this with a build from the repo code at 2c6ba8d (a few commits after the bump to v31.1.2) for the last 5 days, approx 2-3 hours a day, and it has worked well on my i7-1185g7 on Windows 11.

Is there an internal/nightly build you would like me to test instead?  Or would you like me to rebuild at the bump commit (f6a220d) ?

You can email me directly if that is easier.  I'm happy to help, just let me know...

Thanks,
Daniel
(author of #18)

Hi, Daniel,

Thanks for offering help. It would be perfect to run at 2c6ba8d. Actually to my surprise (I am not the one working on releases), I just found that our emulator binary 31.1.2 might not be compiled at exactly the bump commit but rather a few commits after. So your build is actually very close to emulator binary 31.1.2.
It does seem my commit can fix the problem from your test results.

Thanks!

Can someone provide the link to version 31.1.2?  Or, provide a way to get a list of all available from Android Studio?  Thanks!!

re #46,
try to use canary channel in studio's sdk manager, 31.1.2 should show up.

Reply to #46:
windows: https://dl.google.com/android/repository/emulator-windows_x64-7869535.zip
linux: https://dl.google.com/android/repository/emulator-linux_x64-7869535.zip
macosx: https://dl.google.com/android/repository/emulator-darwin_x64-7869535.zip

thanks #48

Thanks #18 for fixing!

+1 to #18

This has not resolved my issue.

Edition Windows 11 Pro
Version 21H2
Installed on    ‎10/‎5/‎2021
OS build        22000.318
Experience      Windows Feature Experience Pack 1000.22000.318.0

Hi #53 - your error appears to be a different cause than the one that was fixed.  Note in the initial log posted with this issue it shows that WHPX fails to initialize.  

From your log it appears WHPX initializes successfully:

WHPX on Windows 10.0.22000 detected.
Windows Hypervisor Platform accelerator is operational

Further down we see:

ERROR   | It seems too many emulator instances are running on this machine. Aborting.

I believe this is caused by an issue opening the network ports for ADB connections.  

In my logs, I will have this where yours fails:

VERBOSE | control console listening on port 5554, ADB on port 5555

If you don't have something using the ports already, you may need to configure your firewall rule or something similar.  Google search the "too many emulator instances" error message text and you should be able to find more information...

Hope this helps.

This fixed my issue and emulator did start and run (on windows 11Build 22000.346 with hyper-v) but then I killed the emulator uing ctrl c and on a restart I got errror below. Running again with -wipe-data fixed the issue. Restarts fine if I exit by closing the window

PS C:\Users\mlwp\Software\Android\emulator>  .\emulator.exe  -avd Pixel_C_API_30  -show-kernel
INFO    | Android emulator version 31.1.2.0 (build_id 7869535) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
INFO    | added library vulkan-1.dll
INFO    | configAndStartRenderer: setting vsync to 60 hz
ERROR   | Failed to open /qemu.conf, err: 2
WHPX on Windows 10.0.22000 detected.
Windows Hypervisor Platform accelerator is operational
INFO    | Started GRPC server at 127.0.0.1:8554, security: Local
INFO    | Advertising in: C:\Users\mlwp\AppData\Local\Temp\avd\running\pid_12832.ini
[ 5497.725387] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 5497.727452] rcu:     1-...!: (0 ticks this GP) idle=ffc/0/0x0 softirq=62892/62892 fqs=1 last_accelerate: d2d8/d3ec, Nonlazy posted: ..D
[ 5497.727452]  (detected by 0, t=21015 jiffies, g=160085, q=10509)
[ 5497.727452] Sending NMI from CPU 0 to CPUs 1:
[ 5497.755413] NMI backtrace for cpu 1 skipped: idling at default_idle+0x23/0x40
[ 5497.727452] rcu: rcu_preempt kthread starved for 15723 jiffies! g160085 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
[ 5497.758981] rcu: RCU grace-period kthread stack dump:
[ 5497.758981] rcu_preempt     I14680    10      2 0x80004000
[ 5497.758981] Call Trace:
[ 5497.758981]  __schedule+0x3f4/0x6f0
[ 5497.758981]  schedule+0x81/0xb0
[ 5497.758981]  schedule_timeout+0xb5/0x150
[ 5497.758981]  ? __prandom_timer+0x8/0x8
[ 5497.758981]  rcu_gp_kthread+0x69d/0xe70
[ 5497.758981]  ? usb_stor_control_thread+0x8/0x8
[ 5497.758981]  kthread+0x180/0x190
[ 5497.758981]  ? usb_stor_control_thread+0x8/0x8
[ 5497.758981]  ? change_clocksource+0x8/0x8
[ 5497.758981]  ret_from_fork+0x35/0x40
[ 5518.810673] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 5518.814623] rcu:     1-...!: (0 ticks this GP) idle=048/0/0x0 softirq=62892/62892 fqs=0 last_accelerate: e014/e884, Nonlazy posted: ..D
[ 5518.814623]  (detected by 3, t=5257 jiffies, g=160089, q=10499)
[ 5518.827577] Sending NMI from CPU 3 to CPUs 1:
[ 5518.834136] NMI backtrace for cpu 1 skipped: idling at default_idle+0x23/0x40

Reply to #55, I think that's a different issue. You can file a new bug. One of our kernel developers should be able to take a look. Thanks!

Does this hypervisor driver for AMD worked with WSL2 now? I need both of them, my env is Ryzen 3700X with Windows11

Just want to thank #18 and #27 for the fix - picked up a Surface Pro 8 with Windows 11 and had to resort to compiling on my phone (not helpful when people are calling you on it!). Fixed my issue and happily coding away, thank you!

Custom download at #48 fix the problem on Windows 11 + AMD Ryzen and Hyper-V enabled!

Reply to #57, the error is benign. The driver is for people who do not use hyper-V (and WSL2 depends on hyper-V).

Reply to #18

Didn't work for me.

#27 worked perfect on AMD 5900x Windows 11. Can finally run Android emulator and use WSL2 without having to keep turning off and on HyperVisor.

Can Windows 10 use this fix?

Reply to #64, the fix in official emulator releases only applies to Windows 11.

Please, can we have Windows 10 fix, too?

thanks to #18 for fixing.

#48 worked for me. Thank you so much.

I've spent days on this and can't seem to get it to work.  I don't see any recent posts, so I expected that the latest builds had incorporated the fix, but doesn't work for me.
Data:
1) Windows 11, Intel CPU, with WSL 2 installed and working (Hyper-V)
2) Tried Android emulator-31-3-14 and it runs slow (no acceleration)
3) Run command "emulator-check.exe accel" and the result is:

accel:
0
Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22621) is installed and usable.
accel

4) Renamed the folder
FROM: C:\Program Files (x86)\Android\android-sdk\emulator
TO: C:\Program Files (x86)\Android\android-sdk\emulator.ORIG-31-3-14

5) Downloaded the Windows.ZIP from message #48 above, unziped into the folder:
C:\Program Files (x86)\Android\android-sdk\emulator

6) Reboot
7) Run command: "emulator-check.exe accel" and the result is unchanged:

C:\Program Files (x86)\Android\android-sdk\emulator>emulator-check.exe accel
accel:
0
Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22621) is installed and usable.
accel

I've tried many things, but the result is the same.  I'm out of ideas.  By the lack of posts, I suspect that it is working for everyone else in the current version.  Why not on my system?

-B

Hi, perhaps, we should clean up the output from accel-check.
"Please disable Hyper-V before using the Android Emulator.  Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot." --------- This sentence comes from old days when only Intel HAXM is supported.

Nowadays, WHPX+HyperV may be a little bit slower than Intel HAXM but should not differ too much.

So the problem is why emulator runs slow. Can you tell me your CPU model?
And run "emulator" with "-verbose -show-kernel" options and paste the command line output?