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?

Anonymous
2024-11-20T19:52:05+00:00

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.

0 comments No comments

58 answers

Sort by: Oldest
  1. Anonymous
    2024-12-11T10:40:37+00:00

    Any news on an update to fix this issue, or only solution for now is to rollback to 23H2 ?

    Br

    Thanks

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-12-11T13:00:50+00:00

    I'm not sure if you found a resolution. I am still looking. Some had luck disabling core isolation. I cannot have that done to our corporate devices. I thought about a temporary ETP. But nah, Microsoft needs to fix this. It is something related to the 24H2 update. I have tried all the smart card reader, used the default Microsoft drivers, installed manufacturer drivers, no luck. I can authenticate to website applications using my smartcard. What I cannot do is authenticate to Azure Virtual Desktop using the MS Remote Desktop Application. The Choose a certificate prompt is MIA. I can authenticate through the url version and reach the desktop. What I cannot do from there is authenticate to a website application using a smartcard because it cannot see the card. Seems to me like the win11 portion that allows the selection of a certificate is gone.

    Microsoft, stop blaming other manufacturers and fix the issue.

    1. No issues on Windows 10. Verified.
    2. No issues with previous versions of Windows 11. Verified.

    This is a 24H2 issue. This isn't the first time an update has jacked up functionality.

    any updates to share ?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-12-11T13:50:17+00:00

    I work for DOE and we tried all sorts of things with no resolution. We did confirm that it has something to do with the latest update of 24H2. The fix will require a Microsoft Windows patch.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-12-11T14:01:45+00:00

    It appears the Dec 2024 update for 24H2 corrected the issue. So is was Microsoft’s fault…

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-12-11T14:08:31+00:00

    It appears the Dec 2024 update for 24H2 corrected the issue. So is was Microsoft’s fault…

    Hey Josh,

    any chance you have the KB the fixes it ?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments