Hi Gia,
We recommend reaching out to our Xbox support to assist you better with this concern.
Feel free to get back to us if you have other concerns. We'll be happy to assist.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
What did I try?
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.
Hi Gia,
We recommend reaching out to our Xbox support to assist you better with this concern.
Feel free to get back to us if you have other concerns. We'll be happy to assist.
Hi Michelle,
although it is about Kinect which is usually an accessory for Xbox, it Is actually used for other purpose that gaming. It is used in conjunction with Visual Studio for gesture recognition application.
To me, it is about a device which was working well until new Surface Book and Windows drivers started to conflict with it.
Could you please confirm that even in this case I should address my support request to xbox forum?
Many thanks!
Gia
I am having the same problem, Kinect V2 was working fine on my surfacebook pro, and even the 3d scan app. Now it just keeps rejecting the Kinect ever since windows was updated....
You phrased the issue perfectly. now how do we fix this?
This seems like a windows issue not an xbox issue? it was working until the windows update?