Windows Phone 8.1 emulator stuck at starting OS

12
votes

I did fresh W10 and VS 2015 install and now when i try running newly created hello world type of app on emulator it doesn't load, all it says is: Emulator text after 5-10 minutes it exits and Visual studio returns DEP6100 (error on bootstrapping stage - connecting to device) and DEP6200 (Device not found) errors.

However VM itself starts, boots up and works in Hyper-V

VM works

Things i tried:

  • Change/Repair Windows 8.1 emulator (nothing changed)
  • Change/Repair Visual studio (nothing changed)
  • Re-install Visual studio (nothing changed)
  • Change Switch type in Hyper V from internal to private (When emulator windows popped it it prompted that there is error with resolving host ip, but booted up and actually this time passed Windows Phone OS is starting screen and actually booted up, but Visual Studio somehow didn't recognize that and after a few minutes of it booting up it forcefully shut down VM and returned same error codes)
  • Removing all ethernet adapters (including my computer one) and then checking for hardware changes so it would create them again. (They were recreated but didn't help, there are only 3 adapters now (Ethernet, Wifi and vEthernet(Windows phone internal Switch)
  • Relaunching it billion of times without changing anything (somehow didn't work)
6
visual-studiowindows-phone-8windows-phone-8.1windows-phone-8-emulator
Related question with an answer that worked for me: stackoverflow.com/questions/29230855/… – Alexander Pacha

6 Answers

11
votes

I tried what you did and it didn't work. So I did the following:

  1. Go to "Control Panel\Network and Internet\Network Connections"
  2. right click on "vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)".
  3. Choose properties and check the case "Hyper-V Extensible Virtual Switch" and click OK.
  4. Again right click on vEthernet and disable it. Then re-enable it.
  5. Run the VM and wait for a few minutes (The 1st time is always longer to load)
9
votes

So, after around 2 days of non-stop googling i found a solution from other stackoverflow question where someone had similar problem but with Android emulator Visual studio (2015) emulator for android not working - XDE.exe - Exit Code 3

What I did was:

  1. Delete All VMs in Hyper V
  2. Delete All switches in Hyper V
  3. Run xdecleanup.exe for every version of XDE (Found at C:/Program Files (x86)/Microsoft XDE/ [8.0/8.1/10.0.10240.0] /XdeCleanup.exe
  4. Run Change/Repair on 'Windows Phone 8.1 Emulators - ENU'
  5. Restart Visual Studio
2
votes

This fixed it for Visual Studio on Windows 10. Allow the following app through your firewall. If you don't have a firewall installed then you are using the built in Windows version:

"C:\Program Files (x86)\Microsoft XDE\10.0.10586.0\XDE.exe"

Note that the actual path may change depending which emulator you have installed.

2
votes

I had the same problem with the Windows 10 Mobile emulators which suddenly stopped working after disabling and re-enabling the Hyper V features of Windows 10 once.

What fixed it for me was this:

  1. Open Control Panel -> Network and Internet -> Network Connections

There should be an adapter named vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch). (Actually I had 2 of those, one showing a red cross saying "Network cable unplugged" and one saying "Unidentified network" - I chose the latter for the following steps).

  1. Right-click the adapter and choose Properties
  2. Switch to tab Sharing
  3. Check the first option "Allow other network users to connect...", uncheck the second option "Allow other users to control or disable..."
  4. As home network connection choose vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)
  5. Switch back to the first tab Networking
  6. Uncheck the item Internet Protocol Version 6
  7. Click OK and also click OK in the message dialog that follows (saying something about IP addresses)

Visual Studio 2015 was open the whole time while doing this. After these steps I pressed F5, waited some time (1-2 minutes) for the OS to boot and the app started.

(This solution is similar to the one proposed over in the MS forums.)

Note: the solution provided by DomDev did not work for me. I did not try the one by Edgar.A

0
votes

A bit late, and stupid, but my problem was that there wasn't enough disk space on my machine!

-1
votes

The following comment, from a reply on the Xamarin forums works:

make sure the compatibility setting is checked under processor for all the emulators you use