I've seen this error several times. Each time I google deeply and finally made me reinstall my windows and all stuffs. Please help, I don't want to reinstall everything again. The error is:
Windows Phone Emulator
Unable to start the Windows Phone Emulator
Windows Phone Emulator is unable to start because
the hypervisor is not running. The likely cause is
that hardware-assisted virtualization is not enabled.
Check your computer's BIOS to ensure that hardware-
assisted virtualization and hardware-assisted data
execution features are enabled.
But yesterday I debugged really normally on Windows Phone using Emulator and I really sure
I've turned on Virtualization in BIOS and also in Turn Windows features on or off :
Sometimes when I hit f5 the IDE come with another error: 0x80131500
My PC: windows 8.1 ultimate 64b, 4gb ram, i3, Visual Studio 2013 RC3
Finally after struggling all day, I solved it ^^
I post the solution here so that somebody don't have to waste time just like me to solve such a silly error!
Just simple disable Hyper-V option in Turn Windows features on or off
(you could open this by hit the combination Windows + S, this will open the search box, then type "Turn Windows features on or off"
restart your PC
enable the Hyper-V option by using the same way as step 1.
Enjoy coding :D
If the accepted answer doesn't work for you - as it unfortunately did not for me - also be sure to enable Data Execution Prevention (DEP) in your BIOS.
The article below outlines what BIOS settings to enable for Hyper-V:
https://msdn.microsoft.com/en-us/library/windows/apps/jj863509%28v=vs.105%29.aspx
In my case, I had hardware-assisted virtualization enabled in the BIOS, but not data execution prevention (DEP). I also had Hyper-V enabled via Windows Features. After enabling DEP in the BIOS, I was able to run the Windows phone emulator.
CMD with admin rights:
bcdedit /set hypervisorlaunchtype auto
and reboot.
Related
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:
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
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.
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
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.
I had the same problem, solved it by turning on the virtualization in the bios
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 sure hypervisorlaunchtype is 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.
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
source
this typing in powershell fix all issues for me with Hyper-V and WSL
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.
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.
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.
I am running on
* Visual Studio 2015
* Windows Surface Pro 4
When I attempt to load a Windows Phone application, I get the message, "Unable to start the Windows Phone Emulator. Windows Phone Emulator is unable to start because the hypervisor is not running. The likely cuase is that hardware-assisted virtualization is not enabled."
I've searched on SO and done the following checks
make sure to use turn on/off windows features to turn on hypervisor
gone into the bios to enable VT-x (actually, the BIOS in windows surface pro 4 doesn't even have this option to enable or disable)
enabled data execution prevention
One thing I've noticed is that when I go to Control Panel > System and Security > Administrative Tools, I do not see the Hypervisor-V Manager shortcut. Also, when I type in "hypvervisor-v" into the searchbox, there are no local hits.
Also, I am running VirutalBox on my system, and I am wondering if this is causing a conflict?
Any ideas if there is a problem with Windows Phone development on a Surface Pro 4? Is it even possible?
Check out this the link to...
http://www.infoworld.com/article/2998538/microsoft-windows/surface-book-and-surface-pro-4-problems-proliferate.html
You have to manually turn on Hyper-V in any Windows 10 Pro system;
it's not turned on by default
I am not able to start any of the Mobile Emulators for Windows Phone 10 (version 10.0.10240).
When I start it from the VS 2015, it gets stuck at "OS is starting". In the Hyper-V Manager, I can see the status "Starting (10%)" for the whole time. After some time, the machine is automatically restarted and it gets stuck at "Starting (10%)" again. Then it timeouts again and the emulator shows an error: "The virtual machine cannot be started because the file rdvgm.exe that is required to start the RemoteFX Manager process does not exist". That is weird, because I do have the rdvgm.exe in the C:\Windows\System32.
I have seen that there are some questions with the same error, but they are resolved by fixing the network switch or by killing devenv.exe after it shows "OS is starting". I have tried both, but it did not help. The network switch issue is different (I have seen it on a different computer - in that case the emulator starts correctly, but VS is not able to connect to it). I am stuck at "Starting (10%)".
What can I try to get it working? Windows Phone 8 emulator is working without any issue.
Thanks
The problem was that Hyper-V detected a graphic card which is able to work with RemoteFX (integrated Intel GPU) but the dedicated one (AMD Radeon) was not supported. I was not able to convince Hyper-V to ignore the dedicated one. When I disabled the RemoteFX support for Hyper-V (unchecked it in the Intel GPU setting in the Hyper-V configuration), it started working.
I found this Microsoft technical support desk yesterday. Its an on line chat with their technical people. I don't know if it covers all MS products. I was asking them about Outlook. Could be worth a try. I found it a touch slow at times, but ...
https://www.awasa.microsoft.com/en-GB/consultation/index?id=914801398064643&skuId=0
Hyper-V has problems enabling RemoteFX with some dual gpu graphics cards. Disabling one of the graphics cards in device manager solved the problem for me:
Disable one of the integrated graphics cards in device manager. I disabled Intel (R) HD Graphics 4600 and left NVIDIA GeForce GT 740M enabled.
Reboot Windows.
Delete the existing mobile phone virtual machines in Hyper-V Manager.
Start Visual Studio and deploy your app again.
I'll be honest, with much distress, I performed a complete factory reset. Reinstalled only Visual Studio 2015 Community edition (only with the tools I needed and not any other emulators such as Android), and it worked after setting up Hyper V as instructed via documentation on dev.windows.com
this is the error I get when I try to launch the emulator:
I have windows 8.1 professional, and the emulator as its shown is compatible with w8.1, and I installed the suitable VS update.
As the message suggests, you probably don't have Hyper-V enabled. If your PC supports it (which it should if the CPU isn't very old), you'll probably have to enable it from your BIOS (look up your motherboard or laptop model number for the exact location of the option in the BIOS).
On the off chance that it's enabled there but disabled from Windows, type "Turn Windows features on or off" from your Windows search charm and see if the Hyper-V option is checked or not. If the option isn't there at all then it's probably disabled from the BIOS or not supported by your CPU.
Also make sure you are running the 64 bit version of Windows 8.1 Pro. From the error shown it sounds like you may have the 32 bit OS installed.
So I have a HP laptop, and as many HP users know it's a nightmare to install Hyper-V on it. But I somehow managed. Hyper-V is running on my laptop and I have all the necessary hardware requirements:
SLAT is enabled
VT-x is supported and enabled
I'm running 64 bit Windows 8.1 Professional
I'm running Visual Studio 2013 Professional Update 3
Hardware D.E.P. is enabled and supported
And yet when I run the Phone Emulator installation I get the following display:
I can't figure out what's going on or why I keep getting the error. Hyper-V is running as shown:
I've spent two days already trying to figure this out and searching on Google for a solution to this problem. Some of the things I've tried:
Flashing my BIOS
Resolving issues with the Realtek BlueTooth driver (this causes issues with Hyper-V)
Reseting my BIOS
Doing a clean install of my whole system
Installing all Windows Updates
Installing all Visual Studio updates
Enabled / Disabled D.E.P.
Any advice is appreciated. If you need the log from the emulator installation let me know and I'll post it here.
Thanks
UPDATE:
I've attempted to install winsows server standard 2012 and tried enababling hyper-v and installing visual studio and the phone emulator there, and that works and I'm able to run the emulators with no problem.
When I tried the same thing back after installing windows 8 again it installs hyper-v but fails to start windows after installing visual studio update 2 with the phone images etc. The only way I can boot back into windows is if I turn off virtualization in bios.
So it turns out that HP Pavilion laptops support all that is needed to run Hyper-V, however it looks as if HP is blocking the SLAT functionality from working properly with Hyper-V thus not allowing it to run correctly. This looks like it's blocked at the BIOS level.
Updating the BIOS doesn't solve the issue.
The way I came to this conclusion is that Windows Server running Hyper-V runs the Windows Phone emulator with no problems, and it's a Microsoft decision to not require SLAT when running Hyper-V on Windows Server while requiring it on Desktop version of Windows.
Seeing how I paid extra for a more powerful laptop to be able to use features like Hyper-V, and to have an experience such as this due to a manufacturer configuration has left a bitter taste in my mouth. Needless to say this is the LAST time I'll ever buy an HP laptop.