Geek Answers Handbook

Windows Phone emulator does not start

When I run the emulator from VS13, I blame myself for “Windows Phone OS is Starting,” but it works correctly in Hyper-v Manager and then continues to receive two errors

Error: DEP6200: Boostrapping 'Emulator 8.1 WVGA 4 inch 512 MB' failed. The device could not be found. Failed to deploy application. Please try again.

Error: DEP6100: The following unexpected error occurred during the "When connecting to the device" level: The SmartDeviceException utility - application crashes. Try again.

Help!

+7
c # visual-studio-2013 windows-phone emulation
source share
6 answers
+3
source share

The solution removes the duplicate route.

  • List item
  • Run "cmd.exe" as administrator
  • Enter "print route"
  • If you see two identical routes from 169.254.0.0, like here:
Persistent Routes: Network Address Netmask Gateway Address Metric 169.254.0.0 255.255.0.0 192.168.1.47 1 169.254.0.0 255.255.0.0 192.168.1.44 1
  1. (b) Then delete both routes using "route delete 169.254.0.0"
  2. Uninstall Hyper-V (go to "programs and features")
  3. Reboot system
  4. Install Hyper-V
  5. Reboot system

Now you can deploy and debug your Windows phone project on the emulator.

+2
source share

From my experience, the two errors you get are related to two components of the Windows Phone virtual machine.

For the first error, I don’t know exactly what failed, but it looks like the virtual machine image is not working as VS expects, one thing you can do for this is to simply open the Hyper-V manager and delete the virtual machine when you will start debugging again from VS, it will again create a virtual machine image in accordance with the characteristics of the device that you are emulating.

But pay attention to the second error:

I have had this error many times, but it is mainly presented even if the virtual machine is running VS successfully, but there is a problem associated with it through the virtual switch created for it, and which can be controlled in Hyper -V under virtual switches.

In this case, again, you can solve this problem by deleting the virtual switch in Hyper-V Manager, and VS will recreate it when debugging again.

I'm sorry that I do not have a definitive answer for you with detailed steps, but removing virtual switches and virtual machines works most of the time, since VS does all the configuration for you when you try again, but if that fails, check this guide on MSDN . I hope that you earn it, it is a serious pain to deal with these problems for a while when you are just trying to test your applications.

+1
source share

It seems that there are problems / conflicts with Windows Update and a reboot during the installation phase of VS2013 Update 2, resulting in WP8.1.

Many people have the same problem:

Can you restart your computer, check all pending Windows updates, and try again?

+1
source share

In my case, I solved this problem by deleting the entire virtual machine in Hyper V Manager, as suggested in this solution: https://stackoverflow.com/a/220290/

  • Open Hyper V Manager (click Start, select Administrative Tools, then Hyper-V Manager).
  • Remove all installed virtual machines
  • Delete all virtual switches
  • Reboot system
  • Rerun visual studio
+1
source share

I have encountered this problem many times, and the main reason is the settings of the anti-virus firewall.

A Windows phone emulator will create virtual network adapters, and an independent anti-virus firewall will not allow access to these adapters.

To resolve this issue, uninstall or disable antivirus software, including Windows Defender.

+1
source share

More articles:


All Articles