Windows Phone Emulator Not Running on Visual Studio 2015 (Windows 10 pro)

3
votes

I am trying to run a Windows Phone Emulator, running Visual Studio 2015 Professional, on Windows 10 pro (64 bit), Here's the error I get when I run the emulator in VS:

It gets stuck on "Loading OS.." and I get this after a few seconds:

enter image description here

When I try running the emulator in the Hyper-V Manager, I get this error:

enter image description here

I have already turned on Virtualization in my BIOS & Checked the "Hyper-V" option in programs and features.

My machine:

Intel Core i7 3770K (4 Physical Cores, 8 Threads) & 32GB of RAM.

Any help on this will be greatly appreciated!

1
c#visual-studioemulationhyper-v
The message in the dialog is too small to read. It would be nice to you type the message directly in the question. – Dante May Code
Thanks for the reply, I wanted to but it was way too long, you can simply right-click and open in a new window, that shows its original size, thanks in advance. – DarkInferno
@DarkInferno - it actually does not. no option to open an image in the new window.... – Ahmed ilyas
Alright, sorry about that guys, I've re-uploaded the screenshots, should be readable now. – DarkInferno
Instead of screen shots, do <kbd>CTRL-C</kbd> and copy the text of the message and paste that. – ΩmegaMan

1 Answers

0
votes

The Intel Core i7 3770K does not support one of the virtualization components, the VT-d (virtualization with Directed I/O). This is where the virtual manager can assign hardware to a VM (i.e. such as NIC port).

You will need to run this on other hardware.

Here are the scenarios, #1 I experienced directly after installing a non-related Azure update:

  1. Something installed may have affected the original install of Visual Studio. Re-run the install of Visual Studio, or the latest update, and select Repair to fix the issue.
  2. Try creating a virtual running a generic OS in the machine's Hyper-V. If it cannot start it could be one of the following issues:
    1. The OS can't run Hyper-V either because it is a consumer version which doesn't have Hyper-V capabilities.
    2. The computer's BIOS doesn't have virtualization capabilities or it is turned off in BIOS. Check BIOS to turn on.
    3. The processor doesn't run all components of virtualization and even though the BIOS does, the Hyper-V manager fails.