Unable to start WP Emulator because hypervisor isn't running

Dan_Friedman

Bit poster
I'm trying to set up my new MacBook so I can develop mobile apps for WP, but I get the following error:

[Window Title]
Windows Phone Emulator

[Main Instruction]
Unable to start the Windows Phone Emulator

[Content]
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 protection features are enabled.
More information

The closest KB article I could find is http://kb.parallels.com/en/115211. Not the same error message, but it gave me some things to check.
4 CPUs, plenty of RAM and nested virtualizationScreen Shot 2014-11-10 at 4.54.57 PM.pngHypervisor enabled Screen Shot 2014-11-10 at 4.55.18 PM.png
I'm using Parallels Desktop 10 (Trial) and Win10 Technical Preview. I don't have an extra license to test Win8.1, but can get one if we can narrow down that that is the issue.
 

Attachments

  • Screen Shot 2014-11-10 at 4.57.38 PM.png
    Screen Shot 2014-11-10 at 4.57.38 PM.png
    36 KB · Views: 3
I had this problem and fixed it by turning on Control Panel / Programs and Features / Turn Windows features on or off / Hyper-V / Hyper-V Platform
 
Hi ChaseC,
Thanks for sharing it! Glad that your issue is resolved, feel free to reach us anytime, we're here to help you.
 
Hi there,

I am experiencing the same issue.
"I had this problem and fixed it by turning on Control Panel / Programs and Features / Turn Windows features on or off / Hyper-V / Hyper-V Platform" - did not resolve my issue.
I have also enabled nested virtualization under configruation

Details:
- Running Parallels Desktop 11 (Trial)
- Running windows 10 Pro
- Visual Studio 2015 enterprise
- Running from boot camp drive (using parallels)

Any suggestions?
 
Hi,
I was experiencing the same on Win10 Pro and Parallels 11 Pro (Trial)
What helped:
1 start with windows directly, not emulation
2 disable hyper-V (), restart directly again
3 enable hyper-V, restart directly again
4 check hyper-V - working
5 restart in Mac OS, start windows in Parallels
hyper-V is working
 
Back
Top