Visual Studio 2015: the emulator cannot check if the virtual machine is working

I have the following problem, hope someone has a solution. I used to have Windows 8.1 and Visual Studio 2013. I upgraded to Windows 10. I installed Visual Studio 2015 Enterprise. I created a new solution, with only one project for a simple Universal Windows application. I am using C #.

When tring starts my proyect, choosing any of "Mobile Emulators 10 ....", I get the following error: enter image description here However, if I select Simulator, it works. Also, if I open the solution for Windows Phone 8.1, and I launch it with "Emulator 8.1", it works.

Any help is appreciated. Thanks.

+8
windows-10 windows-10-mobile
source share
5 answers

If anyone is interested, I found a solution that works for me here:

https://social.msdn.microsoft.com/Forums/vstudio/en-US/823ce958-5287-40f9-bfc8-8fb6db0d4f95/visual-studio-2015-windows-mobile-10-emulator-app-deployment-failed- error? forum = visualstudiogeneral

Basically this is what people should do:

  • 1) Launch the application deployment process in VS 2015 by selecting the emulator, and then press F5
  • 2) Wait until the emulator starts up and "OS starts" is displayed
  • 3) Then go to the task manager, go to the VS 2015 process (devenv.exe) and kill it

Result: The emulator image is built, and the application deployment process cannot fail, since VS no longer works.

Once the emulator is fully built and you see Windows Mobile 10 in action, close the emulator and start the application deployment process again through VS 2015. This time, the application deployment process will be successful.

0
source share

I had a similar problem, however I am using VMWare Fusion to run Windows 8.1. The steps in this article solved my problem. https://blogs.endjin.com/2013/06/running-the-windows-phone-emulator-in-vmware-fusion/


  • Stop the virtual machine on which the emulator is running.
  • Open the virtual machine library L ( WindowsVirtual Machine Library )
  • Select a virtual machine in the list and go to SettingsProcessors & MemoryAdvanced Options

    Select the Enable hypervisor applications in this virtual machine check box to enable nested virtualization. This will add vhv.enable = "TRUE" to the virtual machine configuration file (more on this below).

  • Go back to the list of virtual machines and right-click on the virtual machine and select Show in Finder .
  • In the Finder window, right-click and Show Package Contents .
  • After displaying the contents (list of files and folders), find the configuration file for the VMware virtual machine — a file with the extension .vmx.
  • Open this file in TextEdit and add this line to the end: hypervisor.cpuid.v0 = "FALSE"
  • Save and restart the virtual machine.
+6
source share

I had a problem launching the HoloLens emulator. I had to go into Hyper V Manager and go to Hyper-V settings. Select "Physical GPUs" and uncheck "Use this GPU with RemoteFX".

For this, rdvgm.exe applies. Disabling this option resolved my problem.

+3
source share

Solved: I also encountered the same problem. In my case, the problem was that I did not enable developer mode. After turning it on, it worked fine fine.

+1
source share

Do you see your Virtual Switch information in the Control Panel \ Network and Internet \ Network Connections section? If not, you can try creating your Windows Phone Emulator Internal Switch from Hyper-V again to see if this fixes your problem. Follow these steps:

1.) Open Hyper-V

2.) Disable all existing configured phone emulators.

3.) Click "Virtual Switch Manager"

4.) Click on "Internal Phone Phone Emulator Switch"

5.) Remember what settings are displayed there (because you delete it and recreate it)

6.) Uninstall the existing “Windows Phone Emulator Internal Switch” by clicking “Uninstall”

7.) Click "Apply" and "OK"

8.) Re-create the “Internal Phone Phone Emulator Switch” by clicking “New Virtual Network Switch” and use the same settings that you remembered in step 5.

9.) Then try F5 from Visual Studio, which should set up a new emulator on the virtual virtual switch.

10.) Now the error will be resolved. if not in hyper v, start the Windows phone emulator → then click "Connect" (now starting the emulator from hyper v)

11.) Then try F5 from Visual Studio - to start the emulator (it took some time to start in my case)

0
source share

All Articles