I need to run my Universal Application from Visual Studio 2015 for Device, but when click in "Run" or "Deploy", in ARM architecture, have two errors:
Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be
found. The data necessary to complete this operation is not yet
available.
Error : DEP6100 : The following unexpected error occurred during
bootstrapping stage 'Connecting to the device
'30F105C9-681E-420b-A277-7C086EAD8A4E'.': DeviceException - The data
necessary to complete this operation is not yet available.
My phone (Lumia 535), have build 10581, and my pc have Windows 10 Enterprise.
My pc recognized my phone.
In two devices I activate option Developer Mode.
In emulator it's work fine.
Someone help me?
Thanks
I had this issue earlier please try the below steps.
1.Deactivate Hyper-V (and restart computer).
2.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.
3.Activate Hyper-V (and restart computer).
This may help you to figure out the issue.
Related
Been trying to deploy one of my projects onto the Microsoft HoloLens 1 via USB. For some reason, I keep getting an error about remote authentication: "DEP6957: Failed to connect to device '127.0.0.1' using Universal Authentication. Please verify the correct remote authentication mode.. etc."
I'm using Bootcamp on a Macbook Pro + HoloLens 1 with Visual Studio 2019.
Things I've done:
Developer Settings on Both HoloLens1 and Laptop.
Clean/Rebuild solution.
Pair HoloLens to Laptop with the Microsoft HoloLens desktop app.
Selected x86 & Debug with deploy to DEVICE.
Both devices on same Wifi network.
HoloLens connected via usb.
Really hoping someone can help! I've gone through most of the forums online and they all say more or less the same things which I've already done. I've attached some screenshots as well.
UPDATE: Installed the USB Device connectivity on Visual Studio and am still getting the same errors.
We think this issue may happen due to the lack of USB Device connectivity component in Visual Studio and the following steps worth trying for you.
Check if the component USB Device connectivity has been installed for your VS. If not installed, you can install it with Visual Studio Installer.
Unpair all devices in Setting from your HoloLens.
Deploy your project to your device, the first time Visual Studio deploys it, you will be prompted for a PIN. Follow the Pairing your device instructions.
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)?
Have been trying to launch the Visual Studio Emulator for Android for quite some time with the continued end result of an error code from the log of either [Critical] XDE Exit Code: 16, [Critical] XDE Exit Code: 3 or an infinite "Preparing Virtual Machine" status. I've tried numerous troubleshooting guides and different device profiles but haven't had any success, nor in reproducing what has worked for others.
Running Windows 8.1 Pro 64-bit
Things I have tried:
Both Repairing and Reinstalling the Program
Reinstalling Android Studio and SDK (along with the above in various orders)
Changing Administrative Permission through Microsoft Management Console
Running XdeCleanup.exe
Creating an internal switch in Hyper-V Manager (removing in between attempts)
All of the above by "Run as Administrator"
I have been able to create a virtual machine using the Internal Switch(s) I've created in Hyper-V Manager (albeit there is nothing to boot from) and can run Virtual Box successfully so I do not believe it is a question of my BIOS setup. I would greatly appreciate any insight you could offer or a possible solution that has worked for you with this emulator. Thanks for your help.
*Note that there is no instance of Visual Studio installed on this PC (the documentation suggests that it is not required).
Screens:
You need to be a member of the Hyper-V Administrators group. Go to Control Panel and then Local Users and Groups. Add your username to the "Hyper-V Administrators" group. If no group exists, create it.
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
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.