How can I check which drivers are installed, and how do I remove a driver? Stack Exchange Network Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Zadig is a Windows application that installs generic USB drivers, such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices. It can be especially useful for cases where: you want to access a device using a libusb-based application you want to upgrade a generic USB driver. USB driver installation made easy Zadig is a Windows application that installs generic USB drivers, such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices. It can be especially useful for cases where: you want to access a device using a libusb-based application.
iPi Recorder supports multiple Kinects v2 on a single PC using libfreenect2 instead of Microsoft Kinect SDK v2.
To use this, first you need to enable corresponding camera type in iPi Recorder. Open Camera Types panel and hit ENABLE next to Microsoft Kinect 2 (libfreenect2). Alternatively, open Add Device dropdown and select Kinect 2 for Windows (multiple sensors per PC).
Next you need to install a driver for Kinect that makes it accessible to libfreenect2. There are two options - UsbDk and libusbK.
We recommend to start with UsbDk as an easier option. And turn to libusbK if:
- You have troubles installing UsbDk.
- It doesn't work as expected. E.g. Kinect is not visible in iPi Recorder when libfreenect2 support is on, or works unstable.
- It causes problems with other USB devices.
- 2libusbK
Download globespan usb devices driver windows 7. Just download and install the latest release (1.0.19 as of the moment of writing) and you are done. iPi Recorder can use Kinect v2 devices via libfreenect2. Moreover, because of the smart way UsbDk handles driver replacement you can still use other programs which work with Kinect in a standard way via MS Kinect SDK 2.0.
This driver can be installed using Zadig tool. There are few drawbacks compared to UsbDk:
- (Un)installation of the driver is more complicated (see below).
- While libusbK driver is installed for Kinect, programs which rely on MS Kinect SDK won't see the device.
Install
- Run Zadig tool (2.4 as of the moment of writing).
- Connect Kinect v2 to a PC.
- Under Options menu, check List All Devices and uncheck Ignore Hubs or Composite Parents.
- Then select Xbox NUI Sensor (Composite Parent) from the device combo.
- Select libusbK driver and hit Replace Driver button.
- Click Yes in confirmation dialog which appears after a few seconds.
- Upon successful installation of the driver close Zadig.
Now Kinect is available to libfreenect2 in iPi Recorder.
Uninstall
- Connect Kinect v2 to a PC.
- Open Windows Device Manager.
- Locate Xbox NUI Sensor (Composite Parent) device, right-click and select Uninstall device.
- In uninstall dialog, check Delete the driver software for this device.
- Scan for hardware changes, and MS Kinect SDK driver will be restored automatically.
We have tested libfreenect2 support with a number of USB 3.0 controllers. Here are some findings:
- Intel (built-in), 200 series and above chipsets
- Stable work of dual Kinects with occasional frame drops.
- Intel (built-in) other
- Stable work of a single Kinect. With two connected, there are frame drops and low frame rate issues.
- Works with 5m active USB 3.0 extension cable.
- No depth data with 1.8m passive USB 3.0 extension cable.
- NEC μ720202 (PCIe card)
- Stable work of a single Kinect. With two connected, Windows reports insufficient USB bandwidth for one of them.
- Unstable work with 5m active USB 3.0 extension cable - frame drops.
- Unstable work with 1.8m passive USB 3.0 extension cable - frame drops, low frame rate.
- Tip: PCIe cards with multiple μ720202 chips onboard exist that should be capable of connecting 1 Kinect device per chip.
- StarTech PEXUSB3S42V with 2 chips
- StarTech PEXUSB3S44V with 4 chips
- ASMedia ASM1042A (built-in).
- Stable work of two Kinects with rare FPS issues.
- VIA VL800 (PCIe card). Doesn't work.
- Etron EJ168 (built-in). Doesn't work.
Zadig: Driver Installation
These brief instructions describe how to install an RTL2832U TV tuner stick on your Windows PC. Your version of Windows must be XP SP3 or later. Microsoft does not support WinUSB on Windows 2000 or NT (and don't even ask about 9X/ME).
- Boot up Windows and plug your RTL stick into an open USB slot.
- Run Device Manager to verify that Windows has found the device.
- Download Zadig from here.
- Run Zadig to associate Microsoft's WinUSB driver with the device.
- Choose WinUSB and click 'Install Driver'.
- At this point, you should be able to test programs like SDR# and Unitrunker with your RTL stick.
Device Manager shows us what devices are attached and in what state. However, later versions of Windows made it harder to navigate to the right place to run Device Manager.
This works with Windows 8.1 (only):
Press the pair [Windows]+X where [Windows] is the Windows key and X is the 'X' key. A context menu will appear. Click 'Device Manager'.
For XP, Vista, 7, and 8.0:
Press the pair [Windpws]+R where [Windows] is the Windows key and R is the 'R' key. A popup dialog will appear prompting you to type a command or program name. Type 'control' and press return. This will run the control panel. From the control panel, click 'Hardware and Sound'. Under 'Devices and Printers', select 'Device Manager'.
There are two versions of Zadig. If you have Windows XP, you should download the XP version and read this.
Zadig does a lot of work behind-the-scenes like copying the appropriate drivers, creating an INF file, and adding registry entries so that the numerous layers of Windows can find everything each time your USB stick is plugged into a USB slot.
Zadig offers three choices - WinUSB, libusb0, and libusbK.
My only gripe with Zadig is it does not clean up after itself. It you re-install a driver (or swap out drivers), the old INF files are still there (more on this later).
After Zadig points Windows to the correct driver, you should see this:
For software that makes use of the rtl-sdr software library, download libusb. Extract the appropriate 32 or 64 bit version of libusb-1.0.dll and place it in the application folder. Do not copy it to your Windows folder. It's an application DLL, not a system DLL. One bad actor installs an old version of libusbx (1.0.8) in a Windows system folder, breaking programs that expect latest version (1.0.18 as of this writing).
The following information may help advanced Windows users:
The INF file installed by Zadig goes in your WindowsInf folder and looks something like:
The actual file is longer. The above text should be enough to help you recognize it. The file is named 'OEMxx.inf' where xx is a number that increases each time you run Zadig. The old INF file isn't removed. Zadig also adds keys to the registry that point to this file.
Look under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB for a list of VID/PID pair registry keys. See the device ID in the INF above? The key will have a similar name. Your device may have a different VID and PID value. Under that key will be another key that is the eight digit serial number of your RTL stick. Using one of my sticks as an example:
Under this key are a dozen or so values. The Mfg and DeviceDesc values point to our INF file above. For example:
Suppose you accidentally installed the actual FM + DAB TV drivers that normally ship with these devices? Your INF file will look something like:
Notice the 'Vender' typo. This INF loads the drivers meant for watching TV. If you're reading this page, probably not what you want.
Before mucking around with the registy and Windows folders; try un-installing the device from device manager. Plug the RTL stick into each USB slot and repeat - just to be sure. Once you're satisfied the un-wanted driver(s) are gone - reboot.
Libusbk Drivers
As always - when mucking around with Windows Registry settings and Windows system folders - create a Windows Restore Point and backup of the registry before any changes. Good luck.