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.
![](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(204.8, 96%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
I was responding from a previous post about a possible update being the fix.
It needs reporting to Microsoft via the Feedback Hub. Posting here won't do that. If it isn't reported there could be a long wait.
One of the cumulative updates was a security update so perhaps that was thought to be a fix.
Same issue here (France).
Made lots of test and update to Windows 24H2 seems to be the issue (but no problem on all PCs). So Microsoft need to create a patch ASAP - And this issue seems to be already exist in a previous windows version (1903) : https://osim.ro/wp-content/uploads/Brevete/Cannot-initialize-reader-connection-error.pdf
Regards,
Nicolas
It appears the Dec 2024 update for 24H2 corrected the issue. So is was Microsoft’s fault…
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.
- No issues on Windows 10. Verified.
- 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 ?
Any news on an update to fix this issue, or only solution for now is to rollback to 23H2 ?
Br
Thanks
