Pico Key WebCCID Interface --> no driver #203

Closed
opened 2025-11-19 05:31:32 +08:00 by cinehorse · 4 comments
cinehorse commented 2025-11-19 05:31:32 +08:00 (Migrated from github.com)

Hi guys.
I've installed Pico Fido and initially it's showing a missing driver:

Pico Key WebCCID Interface
USB\VIUSB\VID_FEFF&PID_FCFD&MI_03
USB\VID_FEFF&PID_FCFD&MI_03

Hardware: Waveshare RP2350 - zero
Firmware: Pico Fido 6.6 fpr RP2350-zero (pico_fido_waveshare_rp2350_zero-6.6.uf2). No matter which vendor is set in the Pico Commissioner, this remains the case. If I change the product name here, for example to xyz, and unplug and replug the Pico, the uninstalled device changes to xyz WebCCID Interface.

I received two more RP2350-one units today, and the WebCCID installed correctly on these.
USB\VID_1050&PID_0407&REV_0700&MI_03
USB\VID_1050&PID_0407&MI_03
Could it be that the VID/PID is not set correctly on the Zero?

Hi guys. I've installed Pico Fido and initially it's showing a missing driver: Pico Key WebCCID Interface USB\VIUSB\VID_FEFF&PID_FCFD&MI_03 USB\VID_FEFF&PID_FCFD&MI_03 Hardware: Waveshare RP2350 - zero Firmware: Pico Fido 6.6 fpr RP2350-zero (pico_fido_waveshare_rp2350_zero-6.6.uf2). No matter which vendor is set in the Pico Commissioner, this remains the case. If I change the product name here, for example to xyz, and unplug and replug the Pico, the uninstalled device changes to xyz WebCCID Interface. I received two more RP2350-one units today, and the WebCCID installed correctly on these. USB\VID_1050&PID_0407&REV_0700&MI_03 USB\VID_1050&PID_0407&MI_03 Could it be that the VID/PID is not set correctly on the Zero?
lacrimal commented 2025-11-22 04:55:59 +08:00 (Migrated from github.com)

PID:VID are just fine you have set Yubi, you need correct drivers set to get it working get two tools usbdevwiev and zadig driver installer. after running usbdevwiev (looks like you are under windows) sort by vid you will find vid:pid active when it is connected, there are 5 rows, Look at 'driver infpath' column and identify *.inf driver it should be:

  • 2x input.inf for hid,
  • wdfusbccidriver.inf for SmartCard
  • some oemXX.inf for WebCCID,
  • usb.inf for composite device
    If there are more oemXX.inf for your device you need uninstall it. Best way is to use:
    pnputil /delete-driver oemXXX.inf /uninstall /force, do it to the moment when you get *.inf as i mentioned above (you need unplug and plug back your device after removing all oemXX.inf to check if there are no more) - then you are clean.
    Now for WebCCID use zadig to change its driver.
    After that it will work.
PID:VID are just fine you have set Yubi, you need correct drivers set to get it working get two tools usbdevwiev and zadig driver installer. after running usbdevwiev (looks like you are under windows) sort by vid you will find vid:pid active when it is connected, there are 5 rows, Look at 'driver infpath' column and identify *.inf driver it should be: - 2x input.inf for hid, - wdfusbccidriver.inf for SmartCard - some oemXX.inf for WebCCID, - usb.inf for composite device If there are more oemXX.inf for your device you need uninstall it. Best way is to use: `pnputil /delete-driver oemXXX.inf /uninstall /force`, do it to the moment when you get *.inf as i mentioned above (you need unplug and plug back your device after removing all oemXX.inf to check if there are no more) - then you are clean. Now for WebCCID use zadig to change its driver. After that it will work.
cinehorse commented 2025-11-26 17:01:13 +08:00 (Migrated from github.com)

Thanks, that's no problem on my own devices, but I can't easily follow those steps on other people's devices. Or do I not need WebCCID for authentication?

Thanks, that's no problem on my own devices, but I can't easily follow those steps on other people's devices. Or do I not need WebCCID for authentication?
lacrimal commented 2025-11-26 17:19:10 +08:00 (Migrated from github.com)

Thanks, that's no problem on my own devices, but I can't easily follow those steps on other people's devices. Or do I not need WebCCID for authentication?

I did it at once so not sure if zadig is needed at all when you only use key. For programming WebCCID is necessary.
You can try clear only invalid I FS for users without zadig, that path will be simpler for end user when successfully tested.

> Thanks, that's no problem on my own devices, but I can't easily follow those steps on other people's devices. Or do I not need WebCCID for authentication? I did it at once so not sure if zadig is needed at all when you only use key. For programming WebCCID is necessary. You can try clear only invalid I FS for users without zadig, that path will be simpler for end user when successfully tested.
polhenarejos commented 2026-01-07 04:42:19 +08:00 (Migrated from github.com)

Please use the latest version of the firmware as it has been fixed.

Please use the latest version of the firmware as it has been fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#203