Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get handle for specified device! #2

Open
ParadoxDelta opened this issue Nov 21, 2024 · 4 comments
Open

Can't get handle for specified device! #2

ParadoxDelta opened this issue Nov 21, 2024 · 4 comments

Comments

@ParadoxDelta
Copy link

Hi,
I'm trying to reset the pairing of my USB BT Proxy. Unfortunately, I get this error: 'Can't get handle for specified device!'

IS this related to the stricter BT policy in recent Windows releases? I'm on Windows 11 23H2

@chancefavorsthepreparedmind
Copy link
Owner

Do you perchance have access to an older Windows version to check if it's a Win 11 issue? Alternatively, there's a Linux 'port' of the CLI in this repo you could also use if you have access to a Linux rig.

I'm still running trusty old Windows 7 on my regular Windows rig so I wouldn't know about any issues particular to your built of Windows 11, or any other recent Windows built/version, for that matter. The CLI uses the Libusb library to talk to the dongle so if anything then maybe Libusb is broken again due to some change in the Windows 11 USB stack. There was an issue in late 2019 with a particular Windows 10 built, it's well documented. The Windows version of this CLI is actually based on on a patched version of Libusb to work on Windows 10. Libusb wouldn't open the target device anymore, resulting in the same error message you posted above:

https://stackoverflow.com/questions/53761417/createfile-over-usb-hid-device-fails-with-access-denied-5-since-windows-10-180

libusb/libusb#619

I will look into the issue asap and make the necessary adjustments.

@ParadoxDelta
Copy link
Author

Hey, sorry it was a problem on my end. Somehow radio dongles dont work properly near the mainboard. When I connected the CSR dongle with a USB extension, the tool worked flawlessly.

@chancefavorsthepreparedmind
Copy link
Owner

Hm, that shouldn't be. See, the issue you described doesn't result from an error on the part of the BT interface of the dongle but the USB interface, and, more specifically, it's host-related rather than client-related. If your USB host controller cannot talk to a client device simply because it's located in close proximity that's verry odd, I would rather expect error if it were the other way around (very long cable). What is your mainboard?

@ParadoxDelta
Copy link
Author

ParadoxDelta commented Nov 23, 2024

It's kinda off-topic since it's not related to this software, but to shed some light:
There are documented issues with 2.4 GHz dongles and USB 3.0. https://www.reddit.com/r/buildapc/comments/jfnbbk/til_usb_30_may_interfere_with_nearby_24ghz/

I had ongoing issues with 2.4 GHz mouse / keyboard / xbox controller dongles that I plugged directly into the motherboard. At times they started acting up and losing connectivity / dropping in and out of the device manager. The drops also messed with other USB operations like copying data to an external disk or the USB connection of my VR headset.

I have two PCs right next to each other (an older skylake and a recent ryzen (MB: ASUS Strix X570-E Gaming) and the issue happens on both of them. They are very close to the wifi router so this might be a culprit as well. Those issues stopped for all dongles that I connected over a USB extension cord. I didn't think the issue would also extend to bluetooth dongles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants