My setup
HoloLens
Windows 10 October 2018 Update (10.0.17763.134)
Desktop
Windows 10 Enterprise
Visual Studio Community 2017 Version
Unity 2018.2.19f1 (Latest 7th December 2018 Update)
The Problem
I am unable to deploy any application to the HoloLens, but able to deploy it on hololens-emulator. I'm attempting with the Origami application exported from Unity as in the tutorial. I'm able to pair with the HoloLens easily and I have developer mode on. Visual Studio also does auto-detect the device as a remote machine. But when I attempt to deploy it, I always get the same "DEP0100" error, that the device is not in developer mode though the device is already in a developer mode. I'm at a loss for what else to try, or what setting I've missed. I've reset the HoloLens several times and reinstalled Visual Studio only to get the same thing.
I have already tried the solution mentioned here Unable to deploy HoloLens application but it didn't work for me.
It is not clear what you got. But I have couple ideas:
You connected to HL as Remote Machine, but HL is Device.
You built an appx as x64, but HL is x86.
You didn't install a proper runtime, debug or release.
You use older SDK than HL platform version.
You minimal target platform is higher then HL platform version.
Maybe something else. You need to investigate the Hololens logs. Open "Windows Device Portal"/System/Logging.
Then you need to select some providers with severity by choosing them in box and clicking "Enable". I usually begin from "Microsoft-Windows-WinRT-Error" ETW provider.
DO NOT CLOSE THE LOGGING PAGE!!!!!
Start the debugger with app, see the error and go to Logging page. Try to find out the root of issue.
Related
I have freshly installed Unity 2018.3.10 with Visual Studio 2017 (15.9.10). I cannot deploy a bare-bones 3D unity application to HoloLens due to an error in Visual Studio ("DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on 127.0.0.1 due to error 80004005"). Here are the steps to reproduce:
Create new 3D scene in Unity. Set camera position to 0,0,0 and camera clear color to solid black. Create a red cube in front of the camera with dimensions 0.1x0.1x0.1
Window / Package Manager : remove Ads, Analytics Library, In App Purchasing, TextMesh Pro, Unity Collaborate, because I don't need these
Build settings and Project Settings (Quality and Player Settings) shown in screenshots. Scripting backend = IL2CPP
Unity successfully generates a .sln file
The HoloLens has OS build 10.0.17763.316 . Under Settings/Update & Security / For developers , I set 'Use developer features'=on, 'Enable Device Portal'=on
I don't know if it's necessary, but on my PC, I also do Settings/Update & Security/For developers, select 'Developer mode', 'Enable Device Portal'=on, 'Device discovery'=on
Connect HoloLens to PC via USB cable
Open the .sln file in Visual Studio. Set to Release, x86, Device. Build / Deploy Solution
Compilation is successful, and Visual Studio asks for a PIN, which I get from the HoloLens by opening Settings / Update & Security / For developers / Device Discover / Pair
Visual Studio shows error message: DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on 127.0.0.1 due to error 80004005
Make sure Developer mode is enabled on the Hololens. You can find this in settings.
If that doesn't work then...
Try reseting the device.
Reseting is annoying but that is the solution found for 'Could not obtain a developer license on 127.0.0.1 due to error 80004005'on the forums:
https://forums.hololens.com/discussion/8964/could-not-obtain-developer-license-for-hololens
Pasting the comment here as those forums will be removed:
"shyykoserhiy ✭ November 2017 I've had the same issue. Tried to run
from two different setups: MacBook Pro 2016 with touch bar (windows 10
Pro in Bootcamp) and Surface Pro 4. Same error on two different
machines. So I've though that it might be a problem with the HoloLens
itself. After Resetting the HoloLens from Settings> Update and
Security> Reset everything started to work just fine. This is the only
solution that've worked for me."
It is also mentioned in the unity forums:
https://forum.unity.com/threads/could-not-obtain-developer-license-for-hololens.500808/
"billyjacobs So I did some searching and found that one way to solve
the problem is to reset your hololens device. It will have the latest
version of the device software after you reset it. I was hesitant
against doing this at first but it worked like a charm."
I've been working in a Unity app with Hololens emulator in Visual Studio 2017 in Windows Pro, and it was working great until last night where I started to get the following issue every time that I try to deploy my application into the Hololens emulator:
Error DEP6957 : Failed to connect to device '[device_ip]' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings.
I've tried to do the following things without success:
Clean/rebuild solution
Checked 'uninstall/install' checkbox in the UWP project settings
Deleted Hololens virtual machine
Uncheck/check Hyper-v feature (and restart PC after each try)
Restarted computer
No luck. Sometimes, I am able to make it work, but after 30 seconds to 1 minute, the hololens emulator gets frozen and then it closes itself; again, this was working fine until last night, and I have not installed anything different, unless an automatic windows update did something. This happens with all the applications, and they run just fine in the Unity player.
I would appreciate your help on this, I just don't think the only solution is to uninstall/install Visual studio and all its components, it makes no sense, since everything was ok.
Thank you.
UPDATE
I've just noticed that if I connect the laptop to the internet by using an ethernet cable, it works, it only fails in WIFI, have you seen that before? I also have another UWP that I deploy remotely to a raspberry and it also works only with ethernet, but both of them were used to work in wifi? any idea?
My setup
HoloLens
Windows 10 October 2018 Update (10.0.17763.134)
Desktop
Windows 10 Enterprise
Visual Studio Community 2017 Version
Unity 2018.2.19f1 (Latest 7th December 2018 Update)
The Problem
I am unable to deploy any application to the HoloLens, but able to deploy it on hololens-emulator. I'm attempting with the Origami application exported from Unity as in the tutorial.I always get the same error "
DEP6953: Failed to launch remote debugger with the following error:
'Command failed: 0x80070020'
I'm at a loss for what else to try, or what setting I've missed. I've reset the HoloLens several times and reinstalled Visual Studio only to get the same thing.
I have already tried the solution mentioned on Windows Mixed Reality Developer Forum https://forums.hololens.com/discussion/7361/deployment-error-dep6953 but it didn't work for me.
For whom it may be usefull.
I got this error deploying and debugging windows iot on a raspberry pi.
I fixed this by changing the authentication mode to 'none'. then deployment succeeded.
It could be anything. You need to investigate the Hololens logs. Open "Windows Device Portal"/System/Logging.
Then you need to select some providers with severity by choosing them in box and clicking "Enable". I usually begin from "Microsoft-Windows-WinRT-Error" ETW provider.
DO NOT CLOSE THE LOGGING PAGE!!!!!
Start the debugger with app, see the error and go to Logging page. Try to find out the root of issue.
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). But I receive the following error when i try to build:
Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
SEHException - External component has thrown an exception. App1
and
Severity Code Description Project File Line
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. App1
It's worth mentioning that I went from Windows 7 to Windows 10. It's also worth mentioning that my computer was missing the IpOverUsbSvc.exe (not just the registry post, but the actual service was missing). Couldn't find any way to get this back so, so my colleague sent over the .exe and the DLLs and I placed it in it's location. And the service is now running and no longer gives any errors. My device is recognized by the PC, it's running Windows 10 Mobile (but I've also tried with a device running Windows 8.1).
Specs on PC:
Windows 10 Pro (Build 10240)
Using Visual Studio 2015
UWP Tools
Any suggestions to fix my nightmare? Thanks!
Steps that helped me. I have windows 10 mobile build 10581 (and now 10586) installed on phone
Turn off Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Error.
Turn on Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Working.
If you change another device or re-connect you must close VS2015, re-launch and do again!
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.
I had this issue after updating my device to win10 ver:10.0.10581.0. I tried many things but finally after installing latest sdk and emulators i got it working. You may try installing from this page sdk and emulator:
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
Somehow the new emulators were not visible in vs, they got visible after few restarts and then on device debugging started to work.
But one problem still remain from me that vs crashes after ending debug session with device.
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
Seems like there are many issues causing the same error message.
This one worked for me Windows Phone deploy Issue
Essentially you need to remove/uninstall the device from Windows. Then after unplugging and plugging back in, the device and drivers are reinstalled.
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
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 ....
I uninstalled the existing version of the app in device and re-ran it and it worked for me
I got that error for a really simple reason...just opened a new solution I downloaded from GitHub, pressed F5, and got it!
I had left my build configuration in the default "Debug - ARM" setting, when I changed to "Debug - x64" it worked fine!
(Just adding another reason for completeness, not likely to affect your case!)
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
One more thing could be tried.
Uninstall the existing app if any and then deploy from Visual Studio.
Try on another usb port. It worked
I tried to run the directx samples from ..\Windows Mobile 6 SDK\Samples\PocketPC\CPP\win32\directx\d3dm\tutorials on a Samsung Omnia and on the emulator and it doesn't work because of a deployment error.
I am using Microsoft Visual Studio 2008 and have installed Windows Mobile SDK Standard and Professional refresh.
The device is correctly plugged in and set up for active sync (I know this because other samples work, also a creating Win32 smart device application and running it works).
When I try to run a directx sample application it compiles without errors but the message:
" There were deployment errors, Continue? Yes/No" appears
If I manually copy the application from the debug folder to the device and run it from there, it works.
The same deployment error message appears if I try it on an emulator. Other applications are deploying successfully.
Is there any way to make the deployment work? Maybe there is an obscure option I need to set...
What I do is:
Connect the Mobile device to the PC,
Open Visual Studio 2008,
Open a directx sample project,
Click Run (in Debug or Release mode).
The problem with the deployment is that the file msvcr80.dll could not be found.
It was specified at the deployment options as an additional file "Project->Properties->Configuration Properties->Deployment" then "General->Additional files"
with the paths msvcr80.dll|$(BINDIR)\$(INSTRUCTIONSET)\|%CSIDL_WINDOWS%|0;
Removing it makes the deployment successful. I have only tested this on a Windows Mobile 6.1 device and with the D3DM reference driver on an WM6.1/WM6 emulator.
What I haven't figured out is where does $(BINDIR)\$(INSTRUCTIONSET) point to.
Also I don't know why msvcr80.dll is in the addition files if it is not actually needed.
Is there actually a msvcr80.dll compiled for Windows Mobile platform on an ARM cpu?
I was able to resolve this issue after doing some low-level Sysinternals Debugging. It was trying to deploy NETCFv35.Messages.EN.cab to the device and in my case it was deleted for some reason. Re-installing .NET CF fixed the issue for me. Wish VS 2008 said what file was missing instead of a generic message. Hope this helps you too.