Getting Started

This topic contains additional resources that will help you to develop a Kinect-enabled application. This includes the release notes for the SDK, instructions for getting started creating projects using Visual Studio, and lots of links to blogs, published papers, and other SDKs that you may need.

  • License Agreement
  • System Requirements
  • Installation
  • Getting Help

License Agreement

By downloading, installing, accessing, or using the Microsoft Kinect for Windows Software Development Kit 2.0 (SDK), you agree to be bound by the terms of its license. Please read the Microsoft Kinect for Windows SDK license provided as part of this software.

System Requirements

See System Requirements.



  1. Download and launch the KinectSDK-v2.0_1409-Setup executable from and wait for setup to complete before moving on to step 2.

  2. Ensure that the Kinect sensor is connected to the power hub and the power hub is plugged into an outlet. Plug the USB cable from the power hub into a USB 3.0 port on your computer. Driver installation will begin automatically.

  3. Wait for driver installation to complete. You can verify that installation has completed by launching Device Manager and verifying that "KinectSensor Device" exists in the device list.


    On first plugin, the firmware on the device will be updated. This may result in device enumeration happening several times in the first minute.

  4. Installation is now complete.

Verify that the driver is installed correctly

To verify that the Kinect driver has been correctly installed, perform the following steps:

  1. Ensure that KinectService is running.
  2. The three red LEDs on the Kinect sensor should be lit.
  3. The Kinect sensor should appear in Device Manager as the following nodes under Audio inputs and outputs: Microphone Array (Xbox NUI Sensor), KinectSensor Device: WDF Petra KinectSensor Interface 0, and Sound, video and game controllers: Xbox NUI Sensor.
  4. The Kinect sensor's microphone array will appear under Sound, video and game controllers in Device Manager as: Kinect for Windows USB Audio.


As the first step in trouble shooting, we recommend running the Kinect Configuration Verifier tool. This tool is available in the SDK Browser, and will determine if your hardware is a supported configuration.

  • Samples don’t show any output from the sensor.
    • Verify that the Kinect Sensor, power hub, and USB 3.0 cables are all connected properly.
    • Verify that only a single instance of KinectService is running (through TaskManager)
    • In some instances, you may need to completely power cycle the power hub by unplugging it from the power outlet.
    • If you have additional USB devices attached to the computer, remove them and try again with only the Kinect Sensor attached. Also, see the USB 3.0 section below.
    • Ensure that your system meets the recommended hardware configuration outlined above.
    • Reboot
  • The Infrared stream is returning all zeroes. (In this case, InfraredBasics will show a black screen, while color and depth basics will be streaming correctly.)
    • You are likely on an NVidia GPU with an old driver. Ensure that you have the latest WHQL driver installed from NVidia’s website.
  • The Speech samples crash.
    • Ensure that you have the x86 version of the Speech runtime installed.
  • USB 3.0
    • If you’re adding USB 3.0 functionality to a current system by installing a USB 3.0 host adapter (PCIe), verify that the USB 3.0 host adapter supports Gen-2. Note that you may have to try different PCI-e slots to find one that provides the USB bandwidth required by the sensor. We’ve found that plugging the host adapter into one of the graphics slots works best.
    • If you receive a notification from the OS that there are not enough resources for this device, it means there are other devices which are reserving bandwidth on your controller, and the Kinect cannot currently function. First, try removing high bandwidth devices, such as a webcam, from that controller. If this does not resolve the problem, try to reboot. For integrated controllers, this will often solve the issue. If the problem persists, you may have to add a discrete USB3 controller to your system, or explicitly disable whatever device is causing the conflict.

Getting Help

Online developer resources for Kinect for Windows include the following:

For general Windows development questions, try the following:

In this section