-
Notifications
You must be signed in to change notification settings - Fork 154
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
Add DeviceInterfaceGUIDs registry key for Windows #43
Comments
Looks like this is already implemented in d845253? |
@gusarov use regedit and search for 975F44D9-0D08-43FD-8B3E-127CA8AFFF9D first. If nothing then you should retry to download a fresh copy of Arduino and WebUSB to try again. If you find this GUID, you may need to try delete all the references to 975F44D9-0D08-43FD-8B3E-127CA8AFFF9D in the registry first. This appears in a few places, use regedit and search for the above GUID. Ideally if you can, try on another computer that you have never plug in the board before and test if it is the board problem or windows problem. Also, what board are you using? |
Pro Micro (clone) |
@gusarov you should see two devices appear on DEVICE MANAGER. See image below |
Similar with Leonardo bootloader: (My debug led is on 7, so it fits for both) |
Finally, I got it... hardware\boards.txt have different vid/pid for the microwebusb, and looks like this is doing the trick... Now I have it in chrome, but Access Denied (looks like I've seen someone had such problem already) |
@gusarov Thanks for pointing out that the patch to add the registry key descriptor had been landed. Closing this issue. |
In order for an application to find a USB device on Windows it must have a device interface GUID. For the root USB device this will be GUID_DEVINTERFACE_USB_DEVICE however for functions of a composite device there is no standard GUID. For devices using WinUSB Microsoft recommends adding a descriptor that tells Windows what GUID to use. This value ends up in the DeviceInterfaceGUIDs registry key when the device is enumerated.
The text was updated successfully, but these errors were encountered: