DEP0001 : Unexpected Error: -1988945906 while depl

问题:

Exact error:

Severity Code Description Project File Line Suppression State Error DEP0001 : Unexpected Error: -1988945906 TestApp

What does it mean? It seems it isn't problem with application, it works OK on PC.

Version of OS: 1511, Windows 10 for phones 10.0.10586.164

回答1:

I've experienced the same problem after updating Visual Studio community to Update 2. Typing in CMD (under admin rights) the following command solved my issue:

net start IpOverUsbSvc

Thanks to Agrgg for a good tip ;)

回答2:

This kind of error happens very randomly and usually it means there was an issue during the deployment of the app. Things to check:

• Developer mode is correctly enabled on phone
• Uninstall the app from phone, rebuild solution and then try debug again
• Check that the architecture for all projects is set accordingly (ARM for debugging on real device)
• Sometimes the VS debugger hangs up, so closing VS and kill from Task Manager all VS processes that are eventually running and restart VS may also help.

回答3:

I had the same error with deploying onto Windows Phone 8.1 device. In my case the problem was in Windows Phone IP over USB Transport (IpOverUsbSvc) service, which wasn't running. The deployment error disappeared after I'd started the service manually.

回答4:

I had the same problem.

"net start IpOverUsbSvc" didn't worked for me (throws Access is denied Exception).

I have followed following steps to fix.

1. Start Run (Windows+R), Type: services.msc
2. Start/Restart Windows phone IP over USB Transport.

回答5:

For the RPi, I have RPi3 with WIOT (build 14376) this error happens after failed deployment. Just restart VS and it'll deploy ok.

回答6:

After trying some of the answers already provided and nothing worked, I fixed the error by simply restarting the phone. After that the error was gone for me.

回答7:

I had the same issue, and found that in my case it was occurring while the phone was downloading system updates in the background. App updates/installations from the app Store were also prevented from downloading/installing.

After the update had finished, all was back to working again.

As Windows Phone 10 doesn't seem to make it obvious that it's downloading updates, maybe worth checking this out if you hit this problem.

回答8:

I had the same error, solution is here: https://msdn.microsoft.com/ru-ru/library/windows/apps/jj863509(v=vs.105).aspx Look at Checking BIOS settings required by Hyper-V for Data Execution Prevention. You must select "Turn on DEP for all programs and services except those i select" and in my case application deploys successfully.

回答9:

For me, it was as simple as unlocking the phone so that the computer would have access to it.

回答10:

I had this issue as well. None of the answers helped me. IpOverUsbSvc was up and runing, phone reset, system reboot, nothing... The issue was fixed after a Visual Studio "repair": control panel -> Programs and features -> select VS2015 -> Repair

回答11:

I got a similar error.

The reason the error occurred for me was because I forgot to add the new splash images in assets after deleting the old ones.

The solution was to add the images. To get the correct image names and sizes, I used this extension for visual studio.

回答12:

For Windows 10 (desktop) users

I faced this problem after I uninstalled Windows 10 SDK. It deleted the IpOverUsbSvc service from the system.

Solution

1. Download the Windows 10 SDK .iso installer

2. Inside it there is Installers folder.

3. Find Windows IP Over USB-x86_en-us.msi. Install it. (Don't worry if there is no setup window, it installs fast and silently).

4. I didn't even have to reboot VS2015, it just worked.

5. Check if the IpOverUsbSvc service is running

   • Open a Powershell prompt and type Get-Service -Name *USB*
   • Or go to the Services window. There you should see the IpOverUsbSvc running.

回答13:

So, I think I get the trick. After plugged in your Windows Mobile device, Windows App Deploy can see W10M device, but once your device goes to lock screen, WPD can not detect it anymore.

You should to plug out and plugin again, with screen unlocked, to make it detectable. (I'm not a really English speaker).