Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found

Question

I\'ve read every StackOverflow that I could find on this issue, but I still can\'t work it out.

I\'m trying to deploy an app to actual device (NOT emulator)

Answer 1

I tried many of the suggested solutions to no avail.

After changing the USB-C cable from a USB 3.1 port to a USB 2.0 port on my computer, the error goes away. YMMV

Answer 2

One more thing could be tried.

Uninstall the existing app if any and then deploy from Visual Studio.

Answer 3

I see it is quite an old post...but I still get this problem. In my case, this happened after I deployed to a second phone I had for testing. After that, VS 2017 now only wants to deploy to that phone and not to the other phone no more. If I start another project, the other phone is recognized and deployable to (listed as device under debug). Restarting system fixes this...

Also, if I add another project as reference (like a background task) to my project, I will loose the ability to select the devices and emulators under debug. VS 2017 simply then seems to deploy to the last device selected...(really no clue what this is). I have not been able to get the selection of emulators and devices back yet on this one. I only will have the "Start" and "Download new emulators" options. I think this has to do with the fact that VS maybe doesn't know the type (like arm/86/64) of the reference project because it is not set (not needed as this defies the purpose of referencing a project for dynamic references and not the compiled device specific file...)

Hope it helps someone ....

Answer 4

In case it's helpful for others... I got: DEP6701 bootstrapping failed ... access denied.

Thanks to comments here, I only dev-locked then dev-unlocked my phone (was originally dev-unlocked). Totally works now (took some time installing missing frameworks at first). All good.

Thanks

Answer 5

desktop-->my computer--> right click--> management--> service--> start the service Windows Phone IP over USB Transport (IpOverUsbSvc) although maybe the starttype is set as automatic

Answer 6

Finally managed to find a solution to this illusive bug.

It seems that if I didn't have the Windows Phone 8.1 Tools installed I couldn't build to an ARM device (not even Windows 10 Mobile).

So my step to solve this was: Go to Control Panel -> Programs and Features -> Microsoft Visual Studio ... 2015 -> Modify. And then select the Windows Phone 8.1 Tools.

Pretty pissed that one can't get a reasonable error message when things like this is missing.