'Visual Studio: Xamarin - Error starting Android Emulator
Problem encountered on https://dotnet.microsoft.com/learn/xamarin/hello-world-tutorial/devicesetup
Operating System: Windows 10 Pro
Using the Hello World xamarin example in Visual Studio - I'm unable to start the Android Emulator.
When I click on the Run button in the Android Device Manager - the error appears immediately (See attached)
Error-AndroidDeviceManager (Emulator including Google Play/Google API)
Emulator error
Device error: WARNING: unexpected '-prop' value ('monodroid.avdname=pixel_2_pie_9_0_-_api_28'), only 'qemu.' properties are supported WARNING: unexpected '-prop' value ('emu.uuid=4b63b139-cc77-4b66-9200-0d25f8fc545e'), only 'qemu.' properties are supported
Same Error when Emulator is not using Google Play/Google API
Same Error when Emulator is not using Google Play/Google API
Windows Specifications Edition: Windows 10 Pro Version: 1909
Processor AMD Ryzen 9
Task Manager: Performance: Virtualization is Enabled
cmd - systeminfo: Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes
Visual Studio 2019
Windows Features On/Off (see attached - shows Hyper V / Virtualization enabled as per documentation):
WindowsFeatures
I tried this way too - adding the Virtual Machine Platform - same error
Android SDK Settings
Android SDK Version:
Could the issue be related to the Android SDK Tools - only showing Android SDK Command-line Tools versions 1.0 to 2.1?
Could the issue be related to Android Repository perhaps missing on the bottom right hand side?
I've now also included the Android SDK Repository under the tools - but this is still not coming through:
Solution 1:[1]
You should also check Virtual Machine Platform in Turn Windows features on or off. Also, note that the tutorial that you linked to use an Android device for USB debugging.
EDIT
Here are my Android SDK Manager settings
Platform Settings
Tools
Solution 2:[2]
I had also the same problem, but I have already fixed as next process.
- disable both [Hyper-V] and [Windows Hypervisor Platform].
- restart PC.
- enable both [Hyper-V] and [Windows Hypervisor Platform].
- restart PC.
Solution 3:[3]
I had exactly the same problem, so I went to my UEFI settings and I realized that my SVM Mode was disabled. I don't know what motherboard you have but for Gigabyte this usually is in:
M.I.T ? Advanced CPU Core Settings ? SVM Mode
Solution 4:[4]
I had the same problem, solved it by turning on the virtualization in the bios
Solution 5:[5]
Disable the hyper-v via the following command on command line and reboot.
bcdedit /set hypervisorlaunchtype off
Enable it back with the following command and reboot.
bcdedit /set hypervisorlaunchtype auto
Now my emulator runs!
It seems like there is some kind of conflict with virtualization as per this and it effects creating Linux VMs too but these steps clears it.
The answer by suzukimi is right but I provided the commands and some additional info.
Solution 6:[6]
I had same issue after I brainlessly type some command which ADB I think recommend it to me. After a while a realize, that even WSL does not work (Ubuntu in WSL and Docker) so I started to troubleshoot this one and finaly find solution
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
bcdedit /set hypervisorlaunchtype auto
this typing in powershell fix all issues for me with Hyper-V and WSL
Solution 7:[7]
I had the same issue turns out the issue was that the intel HAXM wasn't installing properly from the SDK manager window. So I downloaded the Installer directly from the repo. and installed it via the exe.
here: https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Restarted Visual studio. Worked perfectly.
Solution 8:[8]
I struggled with this issue for 2 days. I even installed Android Studio and run its own emulator to make sure the issue is not Xamarin. Finally it is solved. In my Dell laptop running Windows 10 with Hyper-V installed, there are two issues causing this:
- Run Command prompt in Admin mode. type
bcdedit. On the last entry all the way down, make surehypervisorlaunchtypeis Off. By default it is set to Auto. To change this setting, type:
bcdedit /set hypervisorlaunchtype off
- Make sure to run the emulator on the laptop screen. Not on any other monitor. Somehow Android emulator crashed my laptop graphics driver when it is on other monitor.
Solution 9:[9]
This recently happened to me. After some research, I discovered that Microsoft Hyper V was the issue, but the machine I was trying to use it on was Windows 10 Home edition. It had to be Professional, Enterprise, etc. It's not compatible with the version of Windows. Hope this helps.
Solution 10:[10]
Go to BIOS and enable Virtualization Technology and of course also make sure the Windows Feature (Hyper-V is installed - all components).
In my case, BIOS was reset when I changed my CPU battery.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow