Windows 10 - drivers do not work as expected

[frogcrush]

When trying to use on Windows 10, I get the following showing up in Device Manager:

And I cannot access the device using any software.

[jhofstee]

You wrote "drivers do not work as expected", but you forget to add what you did expect to happen..

[fenugrec]

Just plugged in mine on a random win10 box and they were detected properly. I would close this as "works here" unless you still have issues ?

[frogcrush]

I don't work at that place any more, so I have no way of testing or explaining any more unfortunately, so I agree that if it works for you then we can close this ticket :)

[fenugrec]

Perfect ! thanks for the update @frogcrush .

[alexandration]

@fenugrec
Hi,
Unfortunately, I have the same issue with Canable 2 adapter with candlelight_fw-ba6b1dd.
Drivers not installed automatically.
The problem is reproducible on all 4 computers (Windows 10, Windows 11) I tried.

[stmlex]

Hi!
My Canable 2 adapter with candlelight_fw-ba6b1dd do not recognized on my computer

[fenugrec]

The windows drivers for this firmware are not part of this repo. The only driver I'm aware of (by HubertD), was not updated in many years, and has many problems. I had tried to fix it, had limited success then abandoned - I don't even use windows except rarely in a VM. Until someone adopts that driver and fixes it, there is not much we can do here.

[alexandration]

@fenugrec, thanks for your answer.

Just maybe someone has a solution.

This adapter worked on one computer running Windows, but after trying to find the reason in the regedit tool, I broke it too. And @HubertD dll worked perfectly.

[alexandration]

@fenugrec
Please tell me, is it correct that the GS_USB interface descriptor index in the configuration descriptor is zero? Because when requesting a string descriptor, this interface has an index of 0xEE.
I changed this value and the host started asking for a string descriptor and then a Microsoft Compatible ID Feature Descriptor.
As a result, I have for my F4DiscoveryBoard:

and for canable2 adapter:

And Savvy CAN works these adapters.

But before that I cleaned the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\1D50606F0000.
And removed the drivers of previous devices. After that I connected F4DevBoard with the corrected firmware. Since Windows requests the extended descriptor once and writes to the registry into usbflags, the canable2 adapter now works on my computer with factory firmware.

[stmlex]

@fenugrec Please tell me, is it correct that the GS_USB interface descriptor index in the configuration descriptor is zero? Because when requesting a string descriptor, this interface has an index of 0xEE. I changed this value and the host started asking for a string descriptor and then a Microsoft Compatible ID Feature Descriptor. As a result, I have for my F4DiscoveryBoard: and for canable2 adapter:

And Savvy CAN works these adapters.

But before that I cleaned the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\1D50606F0000. And removed the drivers of previous devices. After that I connected F4DevBoard with the corrected firmware. Since Windows requests the extended descriptor once and writes to the registry into usbflags, the canable2 adapter now works on my computer with factory firmware.

This method works and on my Windows11pro machine.

[fenugrec]

Thanks for the additional details @alexandration .
Reopening since we may be doing something non-windows-friendly in our descriptors. Unfortunately I don't have time to dig into this (and no win* machines). I think it will be hard to bisect for the F4 targets since they were added recently, also maybe this perhaps isn't a regression, I'm not sure. Canable were supported forever, it might be worth testing a build from ~2019 or so (after cleaning the registry as you described, to force the descriptor query).

I hope this isn't related to our use of unique serial numbers in one of the strings...

[Lyubiao]

@fenugrec
Please tell me, is it correct that the GS_USB interface descriptor index in the configuration descriptor is zero? Because when requesting a string descriptor, this interface has an index of 0xEE.
I changed this value and the host started asking for a string descriptor and then a Microsoft Compatible ID Feature Descriptor.
As a result, I have for my F4DiscoveryBoard:

and for canable2 adapter:

And Savvy CAN works these adapters.

But before that I cleaned the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\1D50606F0000.
And removed the drivers of previous devices. After that I connected F4DevBoard with the corrected firmware. Since Windows requests the extended descriptor once and writes to the registry into usbflags, the canable2 adapter now works on my computer with factory firmware.

thinks，This method works

[alexandration]

I recently did the same with this project for the MKS CANable 2 (G431) adapter. But there it was also necessary to add #define USBD_SUPPORT_USER_STRING_DESC 1 to the usbd_conf.h file. And everything works. Now I don't need F4DevBoard for the initial driver setup.

I think it's worth making a pull request with these fixes to the @normaldotcom project?