Try downloading the driver from the website I had on my reply and see if that fixes it by itself.
We upgraded to 24H2 and now our SCR3310 card reader is no longer recognized and we now cannot log in with our CAC card. Is there a fix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
We upgraded to 24H2 and now our SCR3310 card reader is no longer recognized and we now cannot log in with our CAC card. Is there a fix?
We downloaded latest drivers, removed and reinstalled the driver, tried different USB ports. It shows up as working properly in Device Mgr but that's it. The light won't come on, it ignores the reader. Help.
* Changed to a question
Windows for home | Windows 11 | Devices and drivers
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
58 answers
Sort by: Newest
-
Anonymous
2024-12-12T18:14:57+00:00 -
Anonymous
2024-12-12T16:49:05+00:00 The only issue with this is you only have 10 days to revert. I am well past that…
-
Anonymous
2024-12-12T16:29:04+00:00 All,
I had the same problem and was able to fix it using the steps below.
- Roll back to the 23H2 version
- Uninstall the card reader from device manager and include the driver
- Plug card reader back in (should see the Windows usbccid card reader driver).
- Download the most recent driver version from SCR3310v2.0 USB Smart Card Reader Drivers, Downloads, Support | Identiv (should be version 9)
- Reinstall the 24H2 update.
Let me know if this fix works for anyone else.
-
Anonymous
2024-12-12T15:40:47+00:00 Perhaps they reverted back to 24H2...or a firewall was blocking it. I have had some seriously qualified IT folks look into this from DOE and it is 24H2 blocking the driver and functionality. We believe the driver software and 24H2 are not compatible in some way.