Unplug the Kinect from your PC, reboot and then plug it back into the PC again to check if the drivers are there. Run a search on your PC for 'libusbK' and delete as many files that come up. I know the above process is kind of rough. However, I can say that I successfully deleted the libusbK driver and was able to reinstall the Windows SDK. LibusbK.sys is a KMDF based usb device kernel driver for the Microsoft Windows Operating System family. (Windows XP and up) Windows 2000 is currently not supported by the release builds or driver installer packages but can still be achieved with manual builds and custom driver installations. The driver includes files for USB and the library uDMX.dll. The USB-files are always used, uDMX.dll is used depending on the lighting software. As driver installation became more problematic with each newer Windows-version there are several uDMX-drivers that can be installed / tried. LibusbK: all tested programs worked fine.

• Libusbk Driver Install
• Remove Libusbk Driver
• Libusbk Driver
• Libusbk Driver Goldleaf
• Libusbk Driver Switch
• Libusbk Driver Remove

Most Bitcraze products using USB communication uses the libusb driverfor Windows. This driver allows to communicate with USB devices withouthaving to develop custom drivers. This page explains how to install thelibusb driver using the Zadig tool.

Install the driver

First of all download Zadig from its website: http://zadig.akeo.ie/.

Plug the Bitcraze device in the PC. Windows should display someinstallation window. On windows 8 and 10 it does nothing and closesitself. On windows 7 you have to close the install failed window.

Once windows is out of the way, launch Zadig, you should see your devicein the list. Select the device, select libusb and click install:

The install process should run and succed. Installation is usually quickbut it could also take some time:

Et voilà! The driver is now installed and you can use your USB Bitcrazedevice.

Reinstall driver

If the driver is wrongly installed and needs to be reinstalled or ifWindows already have another driver installed for this device, plug thedevice, launch Zadig and click 'Option/show all devices'. You shouldbe able to choose the device in the list and reinstall the libusbdriver. For example with the Crazyradio.

Troubleshooting

If things does not work check that the device appears as a libusb devicein the Windows device manager. If it is not the case try to reinstallthe driver as described above.

If you are having problems with the device not working all the time youcan try to install the libUSBK driver, it have been behaving a bitbetter to some version of the Bitcraze softwares:

Since 5.0-910, Dolphin has the ability to passthrough a Bluetooth adapter for emulated Wii software. This gives emulated Wii software full control of a Bluetooth adapter, which, provided a decent, working adapter, notably allows pairing Wii Remotes to Dolphin, third-party Wii Remote support, working Wii Remote audio and more accurate connectivity.

• 2Setting up
  • 2.2Windows
• 3Using passthrough mode in Dolphin
  • 3.1Advanced usage
• 4Troubleshooting

Limitations

Libusbk Driver Install

• The functionality and stability of the connection heavily depends on the compatibility of the Bluetooth adapter used.
• Even though most Bluetooth adapters can be used in passthrough mode, perfect compatibility is only guaranteed with the Bluetooth modules from Wii consoles.
• When using Bluetooth Passthrough mode, the emulated software directly communicates with the Bluetooth adapter, so it's not possible to mix passthrough mode with emulated Wii Remotes and some Dolphin features like Netplay, TAS input, input display, among others, won't be available.
• Save states made in Bluetooth Passthrough mode can't be loaded on 'Emulate a BT Adapter' mode, nor vice-versa.
• Wii Remote connection state dictates whether save states made in Bluetooth Passthrough mode will work or not:

Setting up

Linux

A udev rule has to be installed so Dolphin can use a Bluetooth adapter without having to get root privileges.

1. Paste the following into /etc/udev/rules.d/52-dolphin.rules (/lib/udev/rules.d/52-dolphin.rules if making a package). Replace 'YOURVID' and 'YOURPID' with the Vendor ID and Product ID respectively.

SUBSYSTEM'usb', ATTRS{idVendor}'YOURVID', ATTRS{idProduct}'YOURPID', TAG+='uaccess'

2. Reload udev rules with:sudo udevadm control --reload-rules

3. Reinsert the adapter.

Dolphin should be able to automatically unload the USB Bluetooth kernel module (assuming you have permission to; you typically need to be in the plugdev group). If not, unload it with modprobe -r btusb.

Windows

WARNING: While a libusb driver is installed, other programs/devices will not be able to use your Bluetooth device. This can be easily reverted in Windows Device Manager and instructions are provided below.

Download and open Zadig as Administrator, then:

1. In the 'Options' menu in Zadig, make sure 'List All Devices' is enabled.
2. Look through the devices for the radio to passthrough.
3. On the right column, select 'libusbK', then click 'Replace Driver'. Select 'Yes' to modify the system driver.

If you wish to return your Bluetooth drivers back to normal, start 'Device Manager' and locate 'libusbK' devices in the list. Right-click the device you wish to restore and select 'Uninstall Device'. Upon plugging it in next time, Windows will install the default Bluetooth driver and it will resume normal functions. NOTE: If you used the winUSB driver instead, it will be located under 'Universal Serial Bus Devices.' Same instructions apply otherwise.

If Dolphin is unable to use your Bluetooth device after doing this, it may not have the necessary hardware features. You can attempt to use the 'winUSB' driver from Zadig as a last ditch effort.

usbdk

As of 5.0-10617 usbdk is no longer supported.

Some users who wish to maintain use of their Bluetooth Device and use it in Dolphin without swapping drivers have opted to use usbdk. When Dolphin starts up, you will lose control of your Bluetooth Device and regain it when Dolphin shuts down. While this cuts down on the work you need to use your Bluetooth device across many controllers, usbdk has many bugs; the worst of which is that any ES_Launch will immediately crash/freeze the game due to usbdk losing control of the Bluetooth.

Remove Libusbk Driver

macOS

There is currently no way to use this feature on versions newer than 10.9, because Apple removed the ability to unload the Bluetooth kernel module.

A potential solution would be to force the OS to ignore the adapter with a codeless .kext, but this hasn't been tried yet.

Android

This feature is not supported on Android.

Using passthrough mode in Dolphin

In Dolphin, open the Controller Configuration dialog, then select the 'Passthrough a Bluetooth adapter' option in the Wii Remotes section.

While a game is running:

• Wii Remotes can be synced and paired to Dolphin by using the Sync button.
• All saved Wii Remote pairings can be reset by using the Reset button. This will also disconnect all currently connected Wii Remotes.

Advanced usage

Sync button hotkey

It is possible to use the 'Press Sync Button' hotkey as an alternative to the buttons in the controller configuration dialog.

You will need to map 'Press Sync Button' to a key or combination of keys. This can be done within Dolphin by left clicking on the 'Hotkey Settings' tab under 'Options' to bring up the appropriate configuration menu. You must then left click on the 'Wii and Wii Remote' tab and left click on the box for 'Press Sync Button' to map this hotkey.

'Press Sync Button' is designed to work just like the Wii's red sync button:

• Pressing the hotkey will trigger a sync.
• Holding the hotkey for 10 seconds will clear all saved pairings.

Forcing a specific adapter

If you need to use a specific adapter, instead of using the first Bluetooth adapter that is found, you can force Dolphin to use it by editing Dolphin's configuration file (Config/Dolphin.ini). In the BluetoothPassthrough section, set 'VID' and 'PID' to your adapter's vendor ID and product ID. These values should be converted from hex to decimal, for example a VID of '057E' should be inputted as '1406'.

Libusbk Driver

Troubleshooting

'Failed to open Bluetooth device: LIBUSB_ERROR_ACCESS'

This error means that Dolphin doesn't have permission to use the Bluetooth adapter.

If on Linux, make sure the udev rule is set up correctly.

'Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED'

On Windows, this typically means that the libusb/WinUSB driver was not installed for the adapter.

'Failed to detach kernel driver for BT passthrough'

Dolphin tried to automatically unload the Bluetooth USB kernel module and failed to. Unload the module manually before starting a game to avoid this issue.

Wii Remotes do not stay paired after closing the game

This means that your adapter is likely broken and does not remember Wii Remote link keys properly. Use a different adapter to avoid this issue.

This may also happen if your SYSCONF is corrupted or if you changed to a Dolphin version which doesn't have BT passthrough. If your adapter is listed as working with pairing or if you're sure it supports pairings (by having checked the HCI command replies), you can try deleting Wii/shared2/sys/SYSCONF and Wii/btdinf.bak.

Black screen on boot

Games send a reset command to the Bluetooth adapter when they start and wait for it to be acknowledged. If you are getting a black screen for a long time (more than 10 seconds), your adapter may be stuck in a broken state and is unable to respond to any commands. Unplug the adapter and try again.

No usable adapter found

This can happen with some adapters. You'll need to force your adapter to be used.

Libusbk Driver Goldleaf

Adapter test results

Libusbk Driver Switch

Unknown. Not enough information to classify.

Incompatible. Does not work or has significant limitations.

Partially compatible. Works well in most cases, but there may be some issues.

Fully compatible. Works well in all cases and will give the same experience as a Wii Bluetooth adapter.

Stability

^[1] May stop working after HCI resets (stopping, resetting emulation or going back to the system menu).

^[2] Has issues with games which send a lot of commands (including New Super Mario Bros. Wii and The Legend of Zelda: Skyward Sword before you get in game).

^[3] Starts having lag issues after ~30 minutes. Reconnecting the Wii remote is required.

^[4] May stop working after HCI resets on Windows, works fine on Linux and macOS.

^[5] Randomly stop working on Windows, works fine on Linux and macOS.

^[6] Has issues connecting multiple Wiimotes.

Pairing

^[7] Has issues reconnecting multiple Wiimotes.

^[8] Remembers only one Wiimote.

Other

Libusbk Driver Remove

^[9] Doesn't expose its internal Bluetooth adapter, can't be used with Bluetooth Passthrough in any capacity.

^[10] Must be modded before use, refer to this forum thread.