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.
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
![](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)
igals,
If it is a fix it will be the latest Dec cumulative update available via windows update. KB5048667
December 10, 2024—KB5048667 (OS Build 26100.2605) - Microsoft Support
Hi,
I checked with the last 2 KB :
Issue is still present so probably no patch for the moment
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.
