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-11-26T21:18:38+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.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-12-03T21:06:32+00:00

    I had to rollback the update; luckily I'm on a project machine with no corporate policy so I have admin. Tried uninstalling device and driver, turning off core isolation, reinstalling the device from the installer on the SCR3310 website, and device manager would recognize the device, but it seems Windows Credentials manager will not see the device, and it's process stops responding if you try to close the window or cancel.

    100% an issue on Windows' end.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-12-04T04:07:11+00:00

    I just did the update. I tried my SCR3310, a travel card reader, and my Yubikey and none of them work. Going to have to roll back.

    Microsoft, HELP!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Neil D 34,305 Reputation points Volunteer Moderator
    2024-12-04T11:18:52+00:00

    Paul Sankey,

    You are not talking to Microsoft directly here, this is a user community forum.

    For problems with specific devices you need to use the Feedback Hub in windows (winkey+f). You can post a link to your feedback on this thread but unless another user finds a specific fix and replies here Microsoft wont share the fix here.

    It may be fixed by a cumulative update in the future.

    for ref. Windows 11, version 24H2 known issues and notifications | Microsoft Learn

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-12-06T15:38:08+00:00

    All,

    I had the same problem and was able to fix it using the steps below.

    1. Roll back to the 23H2 version
    2. Uninstall the card reader from device manager and include the driver
    3. Plug card reader back in (should see the Windows usbccid card reader driver).
    4. Download the most recent driver version from SCR3310v2.0 USB Smart Card Reader Drivers, Downloads, Support | Identiv (should be version 9)
    5. Reinstall the 24H2 update.

    Let me know if this fix works for anyone else.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments