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

Looks like a fix may be on the way From @SurfaceSupport on Twitter " This has already been cascaded to our engineers to release immediate fix. Please continue to follow the thread on Community. "

I am having exactly the same issue. I bought my Surface Book (Performance Base) wanting to run 3D scans of fairly large models for a project that I'm working on as a major reason for purchasing. If this cannot be fixed, I will return my Surface Book for something that works. What is the status on this? Will Microsoft Support Engineers post here with an announcement when they get a potential fix, or will it come over Twitter? I need to know while I'm still in the return window.

I have nine of the new Surface Books in my team. Other than the blemish being discussed in this thread, they are an excellent device. Everyone that has one really likes its performance and design. I would suggest also reply to the tweet https://twitter.com/SurfaceSupport/status/878158392304443392 to maintain visibility and pressure on Microsoft about the problem. Also given your device is so new, may be a call to customer support may also be worth it. All of us keen to have the issue resolved. Please keep us informed if you make progress.

Hello to everyone on this thread, To further isolate this issue, we would like to know does anyone of you has already posted their concerns via MSDN community ? If so, do they have any recommendations? We need this information so that we will send our report to our support engineer for additional reference. Regards.

I have not been able to find anyone that has reported success or even partial success with this particular issue, on MSDN or elsewhere on the Internet. The only possible fix is to not apply the firmware update from earlier this year, and apparently it's not possible to back out of even with an OS refresh. I believe that others on this thread have stated that this did work on the Surface Book before one of the recent upgrades, and things seem to be narrowed down to a Surface Book specific USB firmware upgrade that came out around the same time as the major Update earlier this year. I do not know if new Surface Books are shipped with or without the offending firmware, as I ran all of the updates on mine before attempting to connect my Kinect v2. I did notice a bunch of firmware updates when i originally ran Windows Update, so it's probably possible that Surface Books still ship without the suspect firmware and would work "out of the box." However, I seem to remember looking at the history and seeing a bunch of the firmware updates report failure, which seems wrong because I didn't get notified at the time of the installation. Unfortunately I cannot verify this fact, as the new Windows Update UI doesn't let me see back all of the updates like i could in previous versions of Windows.

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-06-23T08:30:48+00:00

Looks like a fix may be on the way

From @SurfaceSupport on Twitter

"This has already been cascaded to our engineers to release immediate fix. Please continue to follow the thread on Community."
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-30T21:38:28+00:00

I am having exactly the same issue. I bought my Surface Book (Performance Base) wanting to run 3D scans of fairly large models for a project that I'm working on as a major reason for purchasing. If this cannot be fixed, I will return my Surface Book for something that works.

What is the status on this? Will Microsoft Support Engineers post here with an announcement when they get a potential fix, or will it come over Twitter? I need to know while I'm still in the return window.
Was this answer helpful?

0 comments No comments
Anonymous

2017-07-01T01:37:36+00:00

I have nine of the new Surface Books in my team. Other than the blemish being discussed in this thread, they are an excellent device. Everyone that has one really likes its performance and design.

I would suggest also reply to the tweet https://twitter.com/SurfaceSupport/status/878158392304443392 to maintain visibility and pressure on Microsoft about the problem.

Also given your device is so new, may be a call to customer support may also be worth it.

All of us keen to have the issue resolved. Please keep us informed if you make progress.
Was this answer helpful?

0 comments No comments
Anonymous

2017-07-01T20:25:37+00:00

Hello to everyone on this thread,

To further isolate this issue, we would like to know does anyone of you has already posted their concerns via MSDN community? If so, do they have any recommendations?

We need this information so that we will send our report to our support engineer for additional reference.

Regards.
Was this answer helpful?

0 comments No comments
Anonymous

2017-07-03T20:57:31+00:00

I have not been able to find anyone that has reported success or even partial success with this particular issue, on MSDN or elsewhere on the Internet. The only possible fix is to not apply the firmware update from earlier this year, and apparently it's not possible to back out of even with an OS refresh.

I believe that others on this thread have stated that this did work on the Surface Book before one of the recent upgrades, and things seem to be narrowed down to a Surface Book specific USB firmware upgrade that came out around the same time as the major Update earlier this year.

I do not know if new Surface Books are shipped with or without the offending firmware, as I ran all of the updates on mine before attempting to connect my Kinect v2. I did notice a bunch of firmware updates when i originally ran Windows Update, so it's probably possible that Surface Books still ship without the suspect firmware and would work "out of the box." However, I seem to remember looking at the history and seeing a bunch of the firmware updates report failure, which seems wrong because I didn't get notified at the time of the installation. Unfortunately I cannot verify this fact, as the new Windows Update UI doesn't let me see back all of the updates like i could in previous versions of Windows.
Was this answer helpful?

0 comments No comments