Just a quick post today, hope it helps you out. I spent a few hours trying to track down what could be the root cause of the issue. I was using a Windows Nokia 920 phone and the device would not register with Visual Studio 2013. I could not deploy my applications to the phone, nor could I use the developer tools to unlock it.
Ultimately the thing that fixed me was to wipe a registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\042106610100]
With the phone unplugged, I deleted that key, which is associated with my specific phone, and once I reconnected the device, I could work with Visual Studio once more.
The instructions came from Mark, a Microsoft Escalation Engineer, and the full details of the forum where I found the answer is HERE.
In short these are the steps from Mark.
1. Open a command prompt and browse to this folder:
C:\Program Files (x86)\Common Files\Microsoft Shared\Phone Tools\CoreCon\11.0\Bin
Then run IpOverUsbEnum.exe (with the device unlocked!)
2.Expected results:
C:\Program Files (x86)\Common Files\Microsoft Shared\Phone Tools\CoreCon\11.0\Bi
n>ipoverusbenum
Partner:
Container Id: 6C5585FD-8C32-587B-BBDE-3DB382497937
Instance: USB\VID_0421&PID_0661&MI_01\6&2C0EBAFF&0&0001
Name: RM-820|Nokia Lumia 920
Guid: 00000011-6AE5-9FD1-0000-000000000000
Partner Services listening at ports:
Debugger 8888 -> 127.0.0.1:8888
DeviceReg 27177 -> 127.0.0.1:27077
Msvsmon 8016 -> 127.0.0.1:8016
RPCSurrogate00 6610 -> 127.0.0.1:6510
RPCSurrogate01 6611 -> 127.0.0.1:6511
RPCSurrogate02 6612 -> 127.0.0.1:6512
RPCSurrogate03 6613 -> 127.0.0.1:6513
RPCSurrogate04 6614 -> 127.0.0.1:6514
RPCSurrogate05 6615 -> 127.0.0.1:6515
RPCSurrogate06 6616 -> 127.0.0.1:6516
RPCSurrogate07 6617 -> 127.0.0.1:6517
RPCSurrogate08 6618 -> 127.0.0.1:6518
RPCSurrogate09 6619 -> 127.0.0.1:6519
RPCSurrogate10 6620 -> 127.0.0.1:6520
WPConManClient2Proxy 6891 -> 127.0.0.1:6791
WPPingSirep 29819 -> 127.0.0.1:29819
WPSirep 29917 -> 127.0.0.1:29817If the output is as expected, most likely it’s not an IP Over USB issue.
3. If it reports RPC Server Unavailable, most likely the service is indeed not running on the PC.
4. If it reports no connected partners found:
– check the phone is unlocked
– check it is available in explorer to drag and drop files
– verify whether the USB device (i.e. the Phone) has been correctly detected and installed. This step is not trivial as it requires looking up the USB device (i.e. the phone) in the registry.The following example is based on inspection in the registry (regedit) of an installed Nokia 920 device. If looking for a different device, the difference will be in the VID (Vendor ID, represented as VID_vvvv) and PID (Product ID, represented as PID_pppp).
1) Inspect the DeviceInterfaceGUID value in the registry key indicated below. If the device failed to install, that value may be missing. Please note this is the interface 1 (MI_01), interface 2 is used by Nokia for something different.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0421&PID_0661&MI_01\7&338e4600&1&0001\Device Parameters]
“ExtPropDescSemaphore”=dword:00000001
“DeviceInterfaceGUID”=”{26fedc4e-6ac3-4241-9e4d-e3d4b2c5c534}”2) Inspect the usbflags\042106610100 key below. The osvc value is the relevant thing to look for, it won’t start with 01 if the device wasn’t recognized correctly:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\042106610100]
“osvc”=hex:01,42
“SkipContainerIdQuery”=hex:01,00,00,00The long number, in this case 042106610100 was derived from the Vendor ID (0421), the Product ID (0661) and the revision number (0100) of the device.
More USBFLAGS info:
http://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspxThe correct workaround, if these values are not correct, is to (1) uninstall the devices under “Universal Serial Bus Devices” from Device Manager, (2) remove the key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\042106610100” manually (use that number only if it is the Nokia 920), and then attach the phone again.
