Kinect v2 does not work with Surface Book with latest Windows 10 version1607

Anonymous
2017-03-13T22:04:07+00:00

Hi,

Until recently I had no issues in using Kinect v2 on my Surface Book computer. Suddenly, after last week Windows and Surface Book firmware updates Kinect is not recognized anymore.

My configuration: Surface Book, i5/256

Kinect connected on the USB3 port of Surface Book

Powered either directly or via docking station

Kinect service set to use Nvidia card

Once I connect the USB cable the following happens:

  • Kinect led (from the Kinect adapter) is either orange (as no connection) or flashing white
  • After a few seconds, I get the following message popping up on the screen (message in the bottom right of the screen): "USB Device is not recognized...", followed up by the typical and infinitely repeating USB out sound
  • In Device Manager I can see under the Universal Serial Bus controllers: Unknown USB Device (Set Address Failed)
  • When I installed it first time the device was visible in the Devices, device Manager, etc. But was not starting the Kinect. After restart device was just not recognized.

What did I try?

  • from removing devices, disable, etc...
  • to reinstalling completely my Surface Book (yes... a few hours of work)
  • tested Kinect on a desktop PC - works OK
  • tested on a Surface3 even there works ok (I don't think that Surface3 has a USB 3 port... but, it works!)
  • used Kinect verifier, which as always is listing that USB device is unknown (but this is not new since I had it in the past too)

Any idea? I believe it has to do with latest Windows 10 updates, drivers and latest Surface Book update too. Thank you!

Kind regards,

Gia

***Post moved by the moderator to the appropriate forum category.***

Surface | Surface Book | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

84 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-04-18T18:20:40+00:00

    Hi guys

    I'm having the same problems as all of you. I did manage to get the Kinect to flash up very briefly after I managed to temporarily uninstall the Surface Book keyboard. To me, it looks like a similar issue to one my Macbook has where if one device (the keyboard, in this case) is using USB2, it daisy-chains the USB devices effectively downgrading them all to USB2. I'd be interested to here your thoughts on this.

    Also, has anyone been bugging anyone at Microsoft to get support on this? If so, can people let me know who so I can add another voice.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-18T18:02:42+00:00

    After a full day of Kinect demos, I added a new USB sound device to my computer (external smart speaker) and.... the Kinect stopped working!!  (same problem as before.. device not recognized).

    Highly likely that the problem is the adapter, not the Kinect.  

    I ran through the steps above again, and after about 45 minutes, I once again have a functioning Kinect.

    With device manager open, if you just plug in the adapter without the Kinect, you should see a Generic USB Hub get added, and then a Generic SuperSpeed USB Hub added, and then both will disable and the endless train of beeping begins (when its _not_ working). Once it fails, a third USB device appears that has the error in parens (set address failed).

    At this point, I unplug the adapter USB, and go through the steps above.  Both times, when it worked, despite having no USB devices connected, after updating the driver on one of the original Generic SuperSpeed USB Hubs (e.g. not the one added when I plugged in the Kinect adapter) I got a 'disconnected USB device' windows sound.  I then unplugged the power to Kinect Adapter, plugged the adapter in to a _different_ port on the Surface Dock, re-plugged the adapter power, and "success".  Yay, but also, ridiculous.

    I don't know that it matters, but I am using the "front" USB ports on the dock (side that only has the 2 USB ports).

    The bluescreen will happen when attempting to reload the driver on the Generic USB Hub that gets disabled after it fails. The bluescreen only happens if you reboot after device manager hangs.  If you wait long enough (maybe 5 minutes), the operation will timeout and the bluescreen doesn't happen.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-18T17:29:42+00:00

    not sure if there is of any help... I did some debugview tracing. Interesting is that Access Denied... It completely filled up the log.

    00000023 17.13092613 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1895)\wpncore.dll!00007FFA9CC8F465: (caller: 00007FFA9CC919BE) Exception(140) tid(1198) 80070490 Element not found.  

    00000024 17.13096428 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1899)\wpncore.dll!00007FFA9CCC9165: (caller: 00007FFA9CC919BE) ReturnHr(179) tid(1198) 80070490 Element not found.  

    00000025 17.13096428 [15884]     Msg:[onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1895)\wpncore.dll!00007FFA9CC8F465: (caller: 00007FFA9CC919BE) Exception(140) tid(1198) 80070490 Element not found.  

    00000026 17.13096428 [15884] ]  

    00000027 17.13380241 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\endpoint\appendpoint.cpp(2605)\wpncore.dll!00007FFA9CC82332: (caller: 00007FFA9CC82E01) LogHr(4) tid(1198) 80070057 The parameter is incorrect.  

    00000028 17.13627434 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(964)\wpncore.dll!00007FFA9CC90CD2: (caller: 00007FFA9CC819D3) ReturnHr(180) tid(1198) 80070490 Element not found.  

    00000029 17.13812828 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(964)\wpncore.dll!00007FFA9CC90CD2: (caller: 00007FFA9CC8999A) ReturnHr(181) tid(1198) 80070490 Element not found.  

    00000030 17.14632034 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1895)\wpncore.dll!00007FFA9CC8F465: (caller: 00007FFA9CC919BE) Exception(141) tid(25b0) 80070490 Element not found.  

    00000031 17.14645767 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1899)\wpncore.dll!00007FFA9CCC9165: (caller: 00007FFA9CC919BE) ReturnHr(182) tid(25b0) 80070490 Element not found.  

    00000032 17.14645767 [15884]     Msg:[onecoreuap\base\diagnosis\platform\notifications\platform\database\sqlitedatabase.cpp(1895)\wpncore.dll!00007FFA9CC8F465: (caller: 00007FFA9CC919BE) Exception(141) tid(25b0) 80070490 Element not found.  

    00000033 17.14645767 [15884] ]  

    00000034 17.14666748 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\database\databasehelpers.cpp(133)\wpncore.dll!00007FFA9CC85129: (caller: 00007FFA9CCAB0F6) ReturnHr(183) tid(25b0) 80070490 Element not found.  

    00000035 17.15294456 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\ui\toastforwardingwork.cpp(167)\wpncore.dll!00007FFA9CC745CE: (caller: 00007FFA9CC74826) Exception(142) tid(1198) 80040105     CallContext:[\WnsAFCToastForwarding]  

    00000036 17.15299416 [15884] onecoreuap\base\diagnosis\platform\notifications\platform\ui\toastforwardingwork.cpp(76)\wpncore.dll!00007FFA9CCC632F: (caller: 00007FFA9CC92EF0) ReturnHr(184) tid(1198) 80040105     Msg:[Failed to create activity from toast -- onecoreuap\base\diagnosis\platform\notifications\platform\ui\toastforwardingwork.cpp(167)\wpncore.dll!00007FFA9CC745CE: (caller: 00007FFA9CC74826) Exception(142) tid(1198) 80040105     CallContext:[\WnsAFCToastForwarding]  

    00000037 17.15299416 [15884] ] CallContext:[\WnsAFCToastForwarding]  

    00000038 17.16407394 [15884] onecoreuap\shell\shcore\libs\stream\managedcreatefile.cpp(1359)\shcore.dll!00007FFABB77A4A4: (caller: 00007FFAB9E388D3) ReturnHr(1) tid(1198) 80070005 Access is denied.  

    00000039 17.16420364 [15884] onecoreuap\shell\shcore\libs\stream\managedcreatefile.cpp(1383)\shcore.dll!00007FFABB77A315: (caller: 00007FFABB784F92) ReturnHr(2) tid(22fc) 80070005 Access is denied.  

    00000040 17.16466904 [15884] onecoreuap\shell\shcore\libs\stream\managedcreatefile.cpp(1359)\shcore.dll!00007FFABB77A4A4: (caller: 00007FFAB9E388D3) ReturnHr(3) tid(1198) 80070005 Access is denied.  

    00000041 17.16477966 [15884] onecoreuap\shell\shcore\libs\stream\managedcreatefile.cpp(1383)\shcore.dll!00007FFABB77A315: (caller: 00007FFABB784F92) ReturnHr(4) tid(22fc) 80070005 Access is denied.  

    00000042 17.16556168 [15884] onecoreuap\shell\shcore\libs\stream\managedcreatefile.cpp(1359)\shcore.dll!00007FFABB77A4A4: (caller: 00007FFAB9E388D3) ReturnHr(5) tid(1198) 80070005 Access is denied.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-04-18T16:08:21+00:00

    Well i tried,  The steps did not work for me....  : (  no matter what i do it says USB device not recognized and the beeping that won't stop.

    I am banging my head on the desk.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-04-18T13:23:26+00:00

    Yay, Microsoft finally replied about fixing the Kinect!  Oh wait it's Persistent Pineapple!!!

    Pineapple,  Thank you so taking your time to help trouble shoot this issue.  I will try what you suggested today if i can find 3 hours to tinker.  

    I was almost going to go buy another Kinect to see it it was ours....  but I think that's what Microsoft wants....

    twitter support to all parties involved was no help at all...  @windowssupport was the least responsive...  : (

    Was this answer helpful?

    0 comments