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 No comments

84 answers

Sort by: Most helpful
  1. Anonymous
    2017-06-21T22:40:17+00:00

    Another bad news is, leap motion cant work on windows 10 now either.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-06-15T07:51:03+00:00

    Hi Joseph

    Thanks for trying to help.

    Have you or anyone else at Microsoft actually tried to plugin the Kinect into a Surface Book?

    It seems to me this would be a simple thing to do given this is all you need is a Microsoft Surface Book that is up to date (firmware, OS etc.) and a Microsoft Kinect. Both should be easily to locate for a few minutes of testing someplace at the Microsoft campus. Maybe you could even try on the display equipment at the store on campus.

    Just plug the Kinect into the Surface Book and you should see what we are experiencing and frustrated with.

    With respect to your specific questions - It's not possible to get past the USB cycling error, therefore no Kinect drivers get installed. And confirming again, the Surface Book is completely up to date, drivers, firmware, everything - including the Windows updates that came out yesterday. Bringing it now to Version 1703 (OS Build 15063.413).

    Given the Kinect appears to work on any other qualifying system (e.g. USB3) other than the Surface Book (that is running the latest firmware and Windows), it pretty much points to something specific to Surface Book being the issue (firmware?).

    There are no failed updates to show .. the problem is at the Surface Book's USB device detection level. Others also in this forum thread have provided very detailed descriptions of what we are all experiencing along with various attempts to get it to work.

    If it is impossible for the Microsoft support team to get access to the same Microsoft equipment at Microsoft, then I can provide you with an video/audio recording of the USB error cycling 'music' if that helps illustrate the problem more clearly.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-06-14T18:45:43+00:00

    To help you more about this issue, we would like to know more about the one you mentioned about the version "Dev-v2.2_1607" that was automatically installed on your Surface Pro 2. Have you tried replicating that version to the Surface Book since you're unable to find the tool to download?

    Can you tell us if the graphics driver is up to date? If so, what's the driver version from the Device Manager?

    Also, can you provide us screenshot/s of failed updates via Update history so we can check it on our end?

    Regards.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-06-13T07:37:46+00:00

    Hi Joseph

    On the Surface Pro 2, interestingly version "Dev-v2.2_1607" was automatically installed when the Kinect was plugged in.

    I also went and tried the Kinect on another system, a Lenovo E570 and the Kinect drivers were installed and worked perfectly., but also Dev-V2.2_1607".

    I cannot find a download for this version to be able to try it on the Surface Book. Seems strange that the runtime version that is automatically installed is different to the official version that can be downloaded.

    I also tried to remove the Surface Performance Base out of the equation, by connecting the Surface Docking station directly to the display. The docking station worked fine, but it made no difference to the Kinect which did the same thing as before (error loop). So it seems the Performance Base makes no difference.

    The issue appears to be very specific to the Surface Book, which is unfortunate given it is a premium Microsoft system connecting to Microsoft hardware.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-06-12T03:41:52+00:00

    Hi Everyone,

    I have the same issues as described by others.

    Was it working fine before?

    Yes, I confirmed after CU update and also confirmed it worked with Windows Hello.

    The version I have now is: v1703 OS Build 15063.332

    Kind regards,

    KO_Na

    Was this answer helpful?

    0 comments No comments