8

I recently updated a PC to Windows 8.1 in order to make it compatible to Kinect v2. It's an ASUS N53S with the following specs:

  • CPU: Intel Core i7 - 2670QM (2.2GHz)
  • RAM: 16 GB
  • GPU: GEForce GT 550M
  • USB3 Controller: Fresco Logic xHCI

When running Kinect v2 Configuration Verifier I get all items to green except the USB Controller (even the Kinect is detected). I guess it means the USB hub is not compatible or is missing a driver.

I had a look at the Device Manager and saw that wdf kinectsensor interface 0 has a yellow warning next to it. The warning contains code 10, meaning that the device could not be started.

Otherwise, all drivers are up to date.

I've been browsing quite a lot and found out that other people with the same USB Controller had similar problems but no post mentionned solutions.

Does anybody have an idea of what the problem may be?

Vito Gentile
  • 13,336
  • 9
  • 61
  • 96
Pimich
  • 121
  • 1
  • 1
  • 9
  • I am having a similar issue with my Kinect V2. I have a beefy hardware rig with Asus ROG Crosshair V Formula-Z. http://www.newegg.com/Product/Product.aspx?Item=N82E16813131876 I've updated the bios and I am in the process of installing other drivers/utilities I may have missed in the past. I clearly have it plugged into one of the many usb 3.0 slots but when the Kinect Studio Verifier runs it shows that there is no USB 3.0. When I plug in the device into a 3.0 slot windows notifications comes up with the "Kinect Connected - please click to determine what to do with this device"(Or something li – Sivx Dec 04 '15 at 17:07
  • 2
    Chances are that the USB3 Controller is not compatible. Only 2 brands are compatible with the Kinect2 (see post below). – Pimich Dec 05 '15 at 23:24
  • 2
    This is an old topic, but I can add some extra information. The Kinectv2 requires a USB 3 Host Controller that supports Gen-2 (Microsoft doesn't really make clear if that means USB 3.0 generation 2, or a host controller Gen-2, or something else) - https://docs.microsoft.com/en-us/previous-versions/windows/kinect/dn782036(v=ieb.10). The host controller is on Intel Haswell (i#-4###) systems and later, and on AMD Ryzen systems and later. The poster has an i7-2670QM which is 2 generations older. Some 2### and 3### systems might have it, but documentation is poor and debugging will be frustrating. – user3685427 Oct 28 '19 at 16:41

3 Answers3

7

Not all the USB 3 controllers support Kinect v2. As described in this page from Xbox.com:

Only USB3 controllers from Intel and Renesas are supported

If you use a different brand of USB3 controller, the Kinect sensor may not function correctly.

In this other page (from the official documentation on MSDN), there is another useful detail about the USB 3 controllers:

If you're adding USB 3.0 functionality to your existing PC through an adapter, please ensure that it is a Windows 8 compliant device and that it supports Gen-2

So your controller may be a non-Gen-2 one (see this forum for more information about USB 3.1 Gen-2).

For a list of tested and working controllers (some of which are also available at low costs), refer to the dedicated topic in the official Microsoft Kinect SDK v2 forum. Moreover, in the same forum there are some posts of users that had similar issues with Fresco USB 3 controllers.

So the best solution for you is probably to get a new USB 3 controller, and use it.

Community
  • 1
  • 1
Vito Gentile
  • 13,336
  • 9
  • 61
  • 96
0

  1. Some Laptops preserve few USB 2.0 Ports along with the USB 3.0 Ports. Make sure you've connected the cable to the USB 3.0 Port. Generally, a USB 3.0 port has a 'SS' symbol next to it's USB symbol.

  2. If you are certain that Kinect is connected to USB 3.0 port, then restart your PC while kinect cable is connected to your PC. I face this problem in my HP laptop and restarting my PC this way works for me. Hope it'll work for you too.

Rafaf Tahsin
  • 7,652
  • 4
  • 28
  • 45
0

I had similar problem which was catched by EventLogger that Kinectservice.exe could not start because of lack of MFPlat.DLL. Virtually, the KinectConfigurationVerifier remarks "Verify Kinect Depth and Color Streams" with a exclamation mark. After a little search of DLL, the problem might be caused by the lack of media package of system.

On Windows N versions (the EU version without Media Player) applications crashes with a system error missing MFReadWrite.dll or MFPlat.DLL. You need the Media Feature Pack for your Windows version: Blockquote

Yang C
  • 536
  • 5
  • 16