Unrecognized smart card reader ( SCR-3500 ) on Windows 10


I use a $10 smartcard reader, the SCR 3500 [info - http://www.scm-pc-card.de/index.php?lang=en&page=product&function=show_product&product_id=637 , amazon - http://amzn.to/1Hf0Srm ] . Portable, compact, and cheap. But not officially supported by our internal Microsoft IT team. I've been using the SCR3500 from Windows 7 through Windows 8.1 .

So I upgraded my HP810 to Win10 Build 10076 at the office. All good so far.  I was using a ethernet cable during the upgrade for  PXE boot upgrade.  Very nice experience.

Next it was time to get onto the wifi in my office, as well as get setup for remote access to our corpnet. To access our wifi, II need a smart card. So I plugged in my trusty SCR-3500 Smart Card Reader, which has never given me an issue in the past.  Woops it didn't work. Ooooh, its too late for this AND the Stanley Cup is on. With Win7 and Win8 I had no issues with the SCM-3500. I would plug in the SCR 3500, the reader was recognized, drivers installed, and itsimply worked.

Now, this is the only smart card reader I had. And JimmyC wasn't in the office with his "secret mystery box" of adapters and gizmos to borrow from.

I needed the smartcard so I could install a virtual smartcard on my machine ( https://msdn.microsoft.com/en-us/library/windows/apps/xaml/dn456355.aspx  ).

The virtual smart card install adds the certificates I need to get onto the intranet wireless at the Microsoft office. So without physical smart card reader, I'm not getting onto the wifi and I cannot remote into Microsoft corpnet to get to all that super secret stuff you know we have (somewhere) on our intranet!

Surfed over to the website and found the SCR 3500 is "end of life", replaced by the SCR 2910 [ http://www.scm-pc-card.de/index.php?page=product&function=show_product&lang=en&category_id=46&product_id=868  ]. Can't quite figure out where to buy a SCR2910 in the USA, but…

Long and short of it, naviagate to the SCR-3500 downloads page at http://www.scm-pc-card.de/index.php?page=download&function=show_downloads&lang=en&product_id=637  . Install the Windows 8 drivers for the SCM-3500. Voila, the smartcard reader is now recognized. Reboot may be required if you've tried adding the SCM-3500 since you last booted and it was unrecognized.

Moral of the story. Some devices that were automatically recognized on Windows 8.1 / Windows 7 may not be automatically recognized on Windows 10. Go hunt down the appropriate drivers for Windows 8. Manually install the drivers.  Hopefully you get a happy result as I did.

Comments (2)

  1. Eric P. says:

    Here's my experience with this reader on build 10586 (November release).

    It shows up in "device management" as "SCR35xx USB Smart Card Reader" with an exclamation mark on it.

    Going to details, I found the following "explanation":

    [Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

    {Bad Image}

    %hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x]

    That's pretty sad for a driver that is MS signed.

    The version is 4.65.0.0 from 2/11/2015, provided by SCM Microsystems Inc.

    I found this article while looking for a solution.

    Unfortunately, the SCM driver at the link is version 4.64.0.0 and I'm not sure I even convinced the OS from using it.

    Fortunately, by doing the following in "device management", I found a driver that works:

    Update driver -> Browse my computer for driver software -> Let me pick from a list…

    I picked "Microsoft Usbccid Smartcard Reader (WUDF)" and voila!

    As far as I know, that's a MS generic driver that hardware vendors that design their reader against so that they don't need to write a driver... It should be sufficient.

    1. D. says:

      Eric P.,

      You just saved me!

      I'm testing Windows 10 at my job, and I'm having the same issue when the bosses approved running something called Device Guard. It "hates" the native drivers for the SCR3310s and other devices. But, when I changed the driver to the WUDF, they work like a champ! Now, I have to set this as a default when we start imaging our systems (yikes!).

Skip to main content