This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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
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.
Tested (as Matt Dooris) and issue still present.
Tested by delete old drivers and reinstall smartcard reader and last drivers (4.68) but same issue.
In my case, reader is "SCR35xx USB..." but issue is exactly the same and linked to the windows 24H2 upgrade
Regards,
Nicolas
Thank you for the suggestion. Yes, I had tried that before and I just tried it again but it still does not work. I have all the most up-to-date Windows 11 updates and use any other firewall or virus software other than what Windows provides. My desktop is also fairly new. I have tried two different card readers (after verifying both work on another computer) and they just don't work. Again, everything was working great until the install of 24H2.
I read some advice on the issue with my CAC reader SCR331. I downloaded the V9.02 Windows driver installer and it fixed the problem. SCR3310v2.0 USB Smart Card Reader Drivers, Downloads, Support | Identiv
I did several times…also DOE IT tried that, as well as other things, to no avail.
I believe it was part of the rollup. KB5048667
