Windows phone 8.0 error 0x89371B01 when trying to deploy app

Question

I cant find information on this error anywhere. I am connecting to a brand new lumia icon (AKA lumia 929). Dev account is registered. I have attempted:

• reinstalling windows phone SDK
• restarting phone
• restarting computer
• ensured the app runs on the emulators properly. the only required capability of this app is network. Capabilities have not been changed from the defaults since the project was created. none of the manifest xml files have been touched.
• ensured phone software version is up to date
• ensured apphub account is valid and active
• ensured the windows phone developer registration tool worked, unregistered and re-registered the phone to make sure
• restarting the "ip over usb" windows service thingy
• changing the platform built target to ARM or AnyCpu (no difference, same error)
• tried alternate deployment methods such as windows phone power tools (the xap deploy) and I get the same error when trying to connect (so I know it's not an issue with visual studio, nor is it an issue with the app code)
• I can successfully deploy separate code to a separate WP7 device (so I know it's not an issue with the computer)
• tried multiple usb ports
• tried two separate laptops
• tried visual studio 2013 and 2012

The behavior is this:

1. Connect the phone via usb and unlock it
2. Attempt to connect to phone via windows phone power tools OR deploy an app via visual studio
3. System hangs for about 90 seconds and seems to time out
4. Error appears

I am able to view the phone contents, name it and explore it on my laptop, but when it comes time to deploy something I am stuck.

Error message is simply: 0x89371B01

What does that mean? Has anyone else run into this?

Answer 1

Have you checked the device drivers on your Windows 8.1 machine? It could be a driver issue with your USB drivers on the computer.

I have also found that, once you get it connected, going into the Device Manager and deleting the device from there and forcing it to reload has helped me in the past.

Answer 2

Out of curiosity, try running "sfc /scannow" at a command prompt on the PC. It may require admin elevation. I've seen some bizarre behaviors due to dll problems in sxs in win 8.1, wondering if this could be caused by that kind of thing.