There were errors in VS2013 when a Windows Phone 8.1 App is launching for deploy and debug:
Error 1 Error : DEP6100 : The following unexpected error occurred
during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was
detected. Make sure a phone is connected and powered on. AppWP
Error 2 Error : DEP6200 : Boostrapping 'Device' failed. Device cannot
be found. Deployment failed because no Windows Phone was detected.
Make sure a phone is connected and powered on. AppWP
After performing of many method trying to eliminate this problem (disabling firewall, reinstalling SDKs, updating Lumia 930 to the latest Windows Phone developer preview), I managed to deploy and run an app with debugging. And as topic says, deploying and debugging is possible only with disabled WiFi on the Phone.
After enabling WiFi on the Lumia 930 device while connection of VS-debugger/PowerTools is established, then the debugging session stays connected and working. But if I disconnect Windows Phone Developer Power Tools (8.1) and try to connect again (while WiFi is enabled), it says:
Power Tools can't communicate with the device. Here's the error message:
0x80131600 - 0x80131500 - 0xC0000374
Visual Studio can deploy and start a new debug session after enabling of WiFi even after restarting of a VS2013.
But, after restarting the Windows Phone IP over USB Transport (IpOverUsbSvc) service, VS2013 becomes unable to deploy and debug again until WiFi is disabled again.
That's how it behaves.
UPDATE: After updating to Lumia Denim, the bug was fixed.
I have solved it with the following steps:
Open Windows Search, search for "services".
Find the Service “Windows IP over USB Transport (IpOverUsbSvc)”.
Alter initialization type for automatic and click mouse right button and select Start.
Try running !
I put this answer on another post but I guess some did not feel it was an appropriate answer because I didn't find the exact cause - Can't deploy window phone apps to Emulator. Error DEP6100 & 6200. I see that you are having a few issues that I did not originally have but overall I was having weird symptoms. Below is what I did to remedy the DEP6100 and DEP 6200 errors.
I'll start by saying that reloading Visual Studio 2013 and Windows Phone SDK 8.0 did not fix my issue. What did correct my issue was creating a blank project within the Visual Studio Express 2012 for Windows Phone and deploying the project. Then I went into Visual Studio 2013 and tried deploying my project again and voila, it worked. Why, I have no idea but my guess is there is a file or configuration that is set up by VS Express 2012 for WP that has been missed in the VS 2013 with built in WP SDK.
I had a similar experience with VS 2013 where I could not connect the debugger to the device AND the app would crash out with WIFI enabled (emulator was fine)
I solved these problems by installing VS2015 Enterprise RC
Related
I'm developing a UWP app for Windows 10 Phone. Since some days when I try to deploy the app from within Visual Studio I get asked for a PIN in order to connect to the device
In the phone settings I can trigger pairing so a new PIN is generated for me. But when I enter that PIN, a new dialog appears telling that the PIN was wrong:
If I press 'Cancel' then the deployment is interrupted with an error message:
1>Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
It's strange but some days ago I was not asked for the PIN when I deployed the app. :-( So currently the only option I have is deploy via the web portal. This works but it's enormously slow :-(
Can someone tell me how to solve the problem or what PIN should I enter in order to achieve the deployment?
I had this problem today, closing visual studio and restarting IpOverUSB service fixed this issue for me.
You might want to take a look at Ricardo Pieper Question he has listed all the things he tried to do and all the things that might work.
It looks like the problem was caused by the fact that I'm developing inside a virtual machine (VMWare Fusion on Mac). After setting up the development ebvironment on a PC the deployment works fine.
I can even debug the app running on the phone from inside Visual Studio.
Here's a solution which worked for me:
I had the same problem on my Macbook running VMWare Fusion and trying to debug on my Lumia 950 phone. I was nearly giving up, then I tried using the free VirtualBox and with a virtual USB 3.0 port (which requires the VB extension pack). And it worked!!
Here's my setup:
VirtualBox 5.0.14
VB Extension Pack
Win 10 Development VM from Microsoft – the VirtualBox variant, Build 201601: https://dev.windows.com/en-us/downloads/virtual-machines
Lumia 950 with Windows 10 Mobile 10.0.10586.29
In the VM, I configured to use the USB 3.0 port, since with USB 1.x the phone device driver could not be installed by Windows 10.
The VM contains Visual Studio 2015; I created a UWP JavaScript application and ran it with "Debug" on the connected Lumia device.
Had to go to the Developer options on the device.
Switch back to "Windows Store Apps" option, and then back to "Developer Mode"
I'm having issue on Visual Studio Pro 2015 when trying to debug (ARM Solution Platform selected) on a Windows 10 Mobile physical device on my desktop.
The physical device: Nokia Lumia 920 OS Build 10.0.10586.36 (Developer mode) (device not in lock screen and is powered on)
My Desktop: Windows 10 Pro, Intel Core i5-4670K 8GB RAM 64-bit OS Build 10.0.10586.36 (Developer mode)
I do not have this issue on my laptop using the same Nokia Lumia 920.
Severity Code Description Project File Line Suppression State
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
DeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. App1
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on. App1
So far I've tried restarting both devices and re-installing Visual Studio 2015.
EDIT: So after I've tried the proposed solution, this is what I got even for my emulator. Tried re-installing and repairing, nothing works.
Severity Code Description Project File Line Suppression State
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '8BDF218D-FDBB-4A97-90F9-3AA33B559A92'.': DeviceException - The system cannot find the file specified. App1
Error Error : DEP6200 : Bootstrapping 'Mobile Emulator 10.0.10240.0 WVGA 4 inch 512MB' failed. Device cannot be found. The system cannot find the file specified. App1
I was able to solve the emulator issue by Installing a newer version of Microsoft Emulator for Windows 10 mobile from https://dev.windows.com/en-us/downloads/sdk-archive.
Next I'll try deleting the driver from device manager and if that fails, I'll restoring my device to factory defaults, enable developer mode, and try again to deploy on a physical device.
EDIT: As for the device issue, I deleted the drivers from Device Manager and now I'm able to deploy my apps onto the physical device.
Lumia 920 Driver
The solution is your project need to be deployed first, but may be Emulator 10.0.14393 can't work as good as you want. Following below step can help you.
Turn off Hyper-V
Device Manager: Uninstall Hyper-V driver
Restart
Download Emulator (Version 10.0.10586.11): https://go.microsoft.com/fwlink/p/?LinkId=698769
Restart
Deploying project by Emlulator ver 10586
Deploying in higher emulator version or real device.
It was successful with me!
Does the computer detect the device?
I get this same error when developing with my Windows 10 device and VS105, even though my device is detected by my computer. While I haven't been able to find a permanent solution, the following steps work for me:
Shut down Visual Studio
Unplug your device from your computer
Turn Developer mode OFF on your device.
Plug your device back in
Start up visual studio.
Try running Debug again on your device. It should now come up with another error relating to the fact you don't have developer mode turned on.
Turn developer mode back ON on your device.
Debug should now run.
If you unplug your device, you'll need to go through these steps again before VS can detect it.
EDIT: It might also be worth trying the top answer here: How to develop windows 10 uwp on real device (mobile)?
I am facing a strange issue with Windows Phone Emulators for last a few days. When I try to run any windows phone application from Visual Studio 2013/2012, it initially starts the emulator and then stops with an error displayed in the error window inside visual studio:
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - App deployment failed. Please try again.
I have been trying many solutions in order to fix this issue but nothing helped. At last I re-installed the whole windows 8.1 and then visual studio 2013. Then I created a windows phone 8 application and run it smoothly in windows phone emulator.
Then I installed all windows updates including windows 8.1 update 1. After that I installed the visual studio 2013 update 2. Now if I run any new/existing windows phone 8/8.1 project I get the same error again. Seems like there is something wrong with windows 8.1 updates or visual studio 2013 update 2.
Any help?
Open network and sharing center
Change adapter settings
Check if vEthernet [Windows phone emulator internal switch is enabled)
Try deploying it to the emulator now
If above does not work
Delete the virtual switch(s) if any and do a deployment
If it still does not work, connect to the internet via a LAN
Keep you’r wifi on
do a deployment to the emulator
Most cases above method worked !
I had the same error when i tried switching the target OS version of my app from Windows Phone 8 to 8.1. With 8.1 you get a new manifest file and if, for app or publisher identification string, you have different values in one manifest file than in the other, it will output that exact error when trying to start the app in the emulator. However after searching the web back when i had that error, this error seems to have quite a bunch of possible sources, this being only one among many other, but be sure to check it.
Uninstalling the symantec antivirus fixed my issue.
Step1: Installed VisualStudio 2013 Express for Windows along with
Update 2.
Step2: Created a blank Windows Phone App.
Step3: Deployed the app to the Emulator 8.1 WVGA 4 inch 512MB.
The Emulator Displays with the message 'Windows Phone is Starting'. Times out after about 5 minutes with the following error messages:
Error: DEP6100: The following unexpected error occurred during
bootstrapping stage 'Connection to the device':
Error: DEP6200: Bootstrapping 'Emulator 8.1 WVGA 4 inch 512MB' failed.
Device cannot be found. App deployment failed. Please try again.
Hyper-V Manager shows the phone emulator running when the app is deployed to the
Phone Emulator.
Running my existing phone 8.0 apps with VisualStudio 2012 Professonal through the
phone emulator stopped working after installing VisualStudio 2013 Express with Update 2.
I get this error:
Windows Phone Emulator is unable to connect to the Windows Phone
operating system:
The phone did not respond to the connect request.
Some functionality might be disabled.
Tried running as administrator and repairing VisualStudio 2013 Express with no effect of this problem.
Anyone having similar issues ?
I solved this problem just now. Please take all windows update. Reboot, and check again for any remaining update. This was a bug earlier as well so microsoft fixed it in first update of windows 8.1
Then check any remaining extension update for your visual studio 2013. update there as well.
Try opening a sample app, it should work.
Regards
Kajal
I had same problem . first i fixed it with:
Updating windows
Uninstall / install Windows Phone SDK 8
Remove and add Hyper-v again ( maybe it is not necessary )
But problem came back and instead of previous solution i fixed the issue with :
going to windows firewall and then click on "restore defaults"
Open Hyper-V manager. Look at all the emulators that are running and turn them all off.
Then open visual studio and deploy your app.
This will start a fresh instance of Emulator.
I had the same problem with VisualStudio 2013 Professional and the latest Windows Phone 8.1 SDK and emulators (as of December 2014).
In my case I fixed it by changing the virtual switch 'WinPhoneEmulatorSwitch' in Hyper-V Manager from 'Internal network' to 'Private network'.
I found this solution at pekari.wordpress.com
I had your same problem and after many attempts resolved it this way:
Deactivate Hyper-V (and restart computer);
Go in the Device Manager and open the Network Adapters, here uninstall everything with the name "Hyper-V...", this will allow us to reactivate Hyper-V without any conflict;
Enable Hyper-V (and restart computer);
Finally launch the emulator (if it is the first time you launch it you will have to wait 5-10 minutes, so be patient and wait for it to load all apps it need).
im trying to ebug my universal app from VS 2013 update 2 in my WP8.1 device but i have this error:
Failed to deploy. Make sure another deployment or debugging session is
not in progress for the same emulator or device from a different
instance of Visual Studio: Error writing file
'%FOLDERID_SharedData%\PhoneTools\11.0\Debugger\bin\RemoteDebugger\msvsmon.exe'. Error 0x80070005: Access Denied.
I tried run as administrator and got the same error. Im using VS 2013 Update 1+2, Windows Phone 8.1 on my device (unlocked with WP8.1 developer tool).
Thanks in advance!
Usually, this error means there's a pending Windows Phone OS update. Can you see if you have pending updates on the phone and restart?
In the remote case that still doesn't work, you can try reset the phone in about page to get the phone to a clean state.
http://www.windowsphone.com/en-US/how-to/wp8/basics/reset-my-phone
Probably you installed the app before and then changed some settings in you AppManifest like the project-ID. Uninstall the previously installed version from your device or change the ID-settings back to what you used for the previous installation.