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.***

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.

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.

After days of testing we finally got the Kinect Dev 2 working on Windows 10 on a desktop, thanks to Persistant pineapples tips about device manager. but still not the 2 surface books we own. I think RobAlcock is onto something with this usb2 being downgraded..... but when we first bought the surface books they both worked great, plug and Play , the 3d sacn program poped up and we were scanning stuff for fun. But ever since the windows 10 end of March updates it has stopped working..... attached is a 3d model made from Kinect on surface book from February... #SAVEKINECT

Ok, I will try Persistent Pineapple's trick too. I hope I will not brick my Surface Book.... Last time when I did something similar I had to reimage the device. Wish me good luck! Cheers, Gia

Do you guys have any updates? I've wasted all day today figuring out how to make it work... I just found this thread and read through all the replies, which seem to be exactly about the same problem I have. I'm really disappointed about MS that they can't even manage to have their own product lines compatible and work nicely. I really wish this problem being resolved quickly.... Here's my environment: Surface Book with Performance Base Windows 10 (build 1607, update 1.0.13.0 installed) Kinect SDK 2.0 Symptoms are the same as the others...

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

Anonymous

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.***

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

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

2017-04-19T16:57:23+00:00

After days of testing we finally got the Kinect Dev 2 working on Windows 10 on a desktop, thanks to Persistant pineapples tips about device manager. but still not the 2 surface books we own.

I think RobAlcock is onto something with this usb2 being downgraded..... but when we first bought the surface books they both worked great, plug and Play , the 3d sacn program poped up and we were scanning stuff for fun. But ever since the windows 10 end of March updates it has stopped working.....

attached is a 3d model made from Kinect on surface book from February... #SAVEKINECT
Was this answer helpful?

0 comments No comments
Anonymous

2017-04-19T18:00:23+00:00

Ok, I will try Persistent Pineapple's trick too. I hope I will not brick my Surface Book.... Last time when I did something similar I had to reimage the device.

Wish me good luck!

Cheers,

Gia
Was this answer helpful?

0 comments No comments
Anonymous

2017-04-21T21:50:46+00:00

Do you guys have any updates? I've wasted all day today figuring out how to make it work... I just found this thread and read through all the replies, which seem to be exactly about the same problem I have. I'm really disappointed about MS that they can't even manage to have their own product lines compatible and work nicely. I really wish this problem being resolved quickly....

Here's my environment:

Surface Book with Performance Base

Windows 10 (build 1607, update 1.0.13.0 installed)

Kinect SDK 2.0

Symptoms are the same as the others...
Was this answer helpful?

0 comments No comments