LIBUSB_ERROR_NOT_FOUND driving me nuts!

[themanuel]

A few days ago received a Kinivo BTD-400 (Broadcom BCM20702A0) and in five minutes I set up Zadig per instructions in the wiki and was using bluetooth passthrough in dolphin.  This is one of those adapters that have to be forced by adding VID/PID to the dolphin ini, which I id. However, because only one wiimote would reconnect after launching a game, I started playing around with the drivers to see if this could be fixed, much to my chagrin.  

I installed and uninstalled Zadig multiple times, as well the UsbDk drivers and I got to a point where now I can't get BT passthrough to work at all, no matter what I do.  I have tried uninstalling both, installing both separately and together, restarting the computer multiple times, physically reconnecting the adapter, manually deleting the driver files from \windows\system32\drivers and \syswow64, deleting the sysconf file, you name it.  All I get is the subject error message plus another dialog box that more clearly states that dolphin cannot find libusb.  I even also tried a different bluetooth adapter that I have and I get the same problem.  I also checked with a fresh, portable load of dolphin to no avail.

Is there anything I can do to diagnose this issue, other than completely reinstalling windows?

[leolam]

What is the actual error message? Is it an issue with initialising libusb (which could be caused by parts of usbdk leftover in the system) or with finding an adapter? Or something else entirely?

[themanuel]

The error message is:
LIBUSB_ERROR_NOT_FOUND

When I get back home tonight I'll take screenshots and describe the problem better. I will also describe if there is any difference in the error reports using Zadig or installing UsbDK by itself.

Is there a log file I should post?

Thank you for your attention. It's frustrating how I screwed this up from mostly working to not working at all :-)

[leolam]

LIBUSB_ERROR_NOT_FOUND is the error code, which is shown as part of an error message. Several messages can show this error code, so without the actual message, I cannot know where Dolphin fails.

[themanuel]

OK. I'll put everything together and post more info tonight. Thanks again.

[themanuel]

(10-28-2017, 01:30 AM)leolam Wrote: LIBUSB_ERROR_NOT_FOUND is the error code, which is shown as part of an error message. Several messages can show this error code, so without the actual message, I cannot know where Dolphin fails.

I went back and replicated the issue.  First, I made sure I uninstalled both sets of drivers (Zadig and UsbDk) and restarted my computer.  I also made sure I had the VID and PID of my adapter in the .ini file.

I proceeded to reinstall libusbK with Zadig (v2.3) and tried to run MKW with passthrough, producing the following warning dialog box as soon as I double clicked on the game from the list and before rendering anything:
"Couldn't initialise libusb for Bluetooth passthrough: LIBUSB_ERROR_NOT_FOUND"
I clicked "OK" and dolphin proceeded to crash.

I then rolled back the driver to the Windows 10 default and actually tried to run it again, knowing it would not work without proper driver, but just to see what kind of error I would get and got the same exact one so it is as if Zadig's drivers are not being recognized.

At this point, I reinstalled UsbDk using "UsbDk_1.0.19_x64.msi" and restarted my computer.  I tried to launch MKW again and the rendered video simply hung on a white screen with no messages, although the menu commands were still active.  After almost a minute a warning box appeared:
"Failed to open Bluetooth device: LIBUSB_ERROR_OTHER"
After clicking OK:
"Bluetooth passthrough mode is enabled, but no usable Bluetooth USB device was found. Aborting"
I clicked OK and the emulator did not crash and showed the game list again.

Please let me know if there is any more information I can provide you.

[themanuel]

Update: I did a non-destructive "repair re-installation" of Windows but it did not help. If you have any more ideas before I go though the pain of reinstalling Windows completely, please let me know. It's the nuclear option and I would rather not do it because of all that I have would have to reconfigure.
Thanks.

[leolam]

"Couldn't initialise libusb for Bluetooth passthrough: LIBUSB_ERROR_NOT_FOUND"

This appears to mean that libusb is still detecting usbdk and trying to use it, only to fail because it's been uninstalled... partially.

Have you tried uninstalling usbdk using the controller application? Instructions: https://github.com/daynix/UsbDk/blob/master/Documentation/Uninstallation.txt (section UsbDkController)

[themanuel]

I have not tried that which gives me hope, as it sounds promising. I'll try when I get home and report back here. If it works I'll just bang my head against one of the basement columns 3-5 times for not reading through that information before.

[themanuel]

(10-30-2017, 10:49 PM)leolam Wrote: "Couldn't initialise libusb for Bluetooth passthrough: LIBUSB_ERROR_NOT_FOUND"

This appears to mean that libusb is still detecting usbdk and trying to use it, only to fail because it's been uninstalled... partially.

Have you tried uninstalling usbdk using the controller application? Instructions: https://github.com/daynix/UsbDk/blob/master/Documentation/Uninstallation.txt (section UsbDkController)

I was finally able to make it work again, thanks to your lead.  It wasn't without additional frustrations along the way, but I have a working setup now and that is what matters.  After much trial an error, I had to reinstall usbdk through the .msi file and then follow the instructions to use usbdkcontroller.exe to uninstall it again.  Only then was I able to make Zadig's installation work.  As long as the uninstallation method described above is reported as successful in the command prompt, Zadig will be able to do its thing reliably (I was hard-headed enough to screw everything up again to verify that this method works and it does every time).

For some reason, I can't ever get it to work again where installing through the usbdkcontroller.exe or the .msi file will work.  When I had done it the first time days ago it worked fine and you could use bluetooth when not using dolphin BT passthrough, which was nice but not worth the inconvenience of having to deal with it when it doesn't work.

At any rate, I'm happy now and the morale of the story is:
Stick to Zadig and don't ever try to install UsbDk on your own using the .msi file provided in their Github page.

By the way, playing SMG2 these last few days without BT passthrough support and now going back to it made me realize how good the feature really is.  The star pointer moves much more smoothly, the speaker works (not a great original feature of the Wii but authentic), the rumble is more consistent, etc.  I even see a difference in nunchuk responsiveness with the 3rd party wireless nunchuk I have.  Without BT passthrough, it's harder to do a quick turn-around high jump when walking front to back but I'm able to nail it every time with it.

Thank you very much for all your help, leolam!