How to Install ACS Smart Card Reader Drivers on Windows 10 and 11
← Back to the ACS testing and utilities centre
How do you install an ACS smart card reader driver on Windows 10 or 11? Find your reader model in the ACS drivers directory, download the Windows PC/SC Driver Installer for that model, and run it as an administrator with the reader unplugged. Then plug the reader in and check two things: the reader is listed under Smart card readers in Device Manager with no warning mark, and the Windows Smart Card service (SCardSvr) is running. The procedure is the same on Windows 10 and Windows 11.
Most current ACS USB readers follow the CCID standard, so Windows often sets them up on its own with a built-in driver before you install anything. This guide explains when that built-in driver is enough and when you need the ACS driver, then covers removing an old driver and fixing the errors people meet most often: Code 10, Code 52 and the "unknown device". It applies to any ACS USB reader. For the exact driver file, version and test steps for one reader, use the model guides. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer: every driver link on this page opens acs.com.hk.
Windows 10 vs Windows 11: What Is Different?
For an ACS reader, very little. Both versions use the same smart card system: your program talks to the Windows Smart Card service, the service talks to the reader driver, and the driver talks to the reader over USB. The installer, Device Manager and the service work the same way on both. The differences are in the details around them:
| Topic | Windows 10 | Windows 11 |
|---|---|---|
| Installing the ACS driver | Same steps | Same steps |
| Removing an app | Settings > Apps > Apps & features | Settings > Apps > Installed apps |
| Uninstall device option | Tick box usually reads "Delete the driver software for this device" | Tick box usually reads "Attempt to remove the driver for this device" |
pnputil command options | /enum-drivers and /delete-driver (version 1607 or later); /enum-devices (version 1903 or later) | The same, plus filters such as /enum-drivers /class |
| Memory integrity (Core isolation) | On both, when it is turned on it can block a driver that is not compatible with it. Check it in Windows Security > Device security > Core isolation details (see common errors) | |
Check the operating system column on the ACS download page for your model before you install. ACS lists the Windows versions each package supports, and an older package may name Windows 10 and 11 explicitly while a newer one simply says "Windows".
Built-in Windows CCID Driver vs the ACS PC/SC Driver
CCID (Chip Card Interface Device) is the USB standard for smart card readers. ACS describes its current USB readers, including the ACR1252U, ACR1552U, ACR122U and ACR39U, as compliant with both CCID and PC/SC. Two drivers can therefore run the same reader on Windows:
Built-in Windows CCID class driver
Supplied by Microsoft as part of Windows. Microsoft's list of USB class drivers gives the smart card class (0Bh) its own driver, so a CCID reader can work with no download. Microsoft lists the older Usbccid.sys as obsolete, replaced by a user-mode driver, WUDFUsbccidDriver.dll. In Device Manager the Driver Provider shows Microsoft.
Installed and updated with Windows
ACS PC/SC driver
Published by ACS for each reader model on acs.com.hk. It is written for ACS hardware and is the driver ACS's own manuals and tools assume. In Device Manager the Driver Provider shows ACS and the Driver Version matches the ACS download page.
Downloaded from acs.com.hk, one package per model family
When the built-in driver is enough
If your reader appears under Smart card readers with no warning mark, and your software can see a card, the built-in driver is working. Microsoft notes that when a device belongs to a supported USB class, Windows loads the class driver and the device works with no other driver. Many simple uses, such as reading a contact smart card or the ATR of a card, can run this way.
When you should install the ACS driver
Microsoft also says its class drivers might not support every feature in a class specification, and that hardware makers should provide drivers for the extra features of their devices. Install the ACS driver when any of these apply:
- The reader is not set up at all: it shows as an unknown device or under Other devices, or not under Smart card readers.
- Your software uses reader-specific commands from the ACS reference or API manual, for example LED, buzzer or reader configuration commands. Test those with the ACS driver installed.
- The ACS tools or your software supplier tell you to use it, or support asks you which ACS driver version is installed.
- The reader works, but not reliably with the built-in driver. Switching to the current ACS driver is a sensible first step before deeper troubleshooting.
- The reader is older and not CCID, so Windows has no built-in driver for it. ACS keeps drivers for many older models on the same directory.
When in doubt, install the ACS driver: ACS publishes it for the reader, and it gives you a known version to compare when something goes wrong.
Step 1: Find Your Model's Driver in the ACS Drivers Directory
- Read the model name on the reader. The label underneath gives the full model, such as ACR1252U-M1 or ACR39U-U1. ACS drivers are listed by model, so the name matters more than the shape: readers that look alike can use different packages.
- Open the ACS drivers directory. Go to Drivers / Manuals / Datasheets at acs.com.hk. Readers are grouped by type, for example Contactless Readers for NFC readers and contact smart card readers in their own group.
- Select your model. Click it in the list, or use the Select Product menu on any driver page. You land on a page called Drivers & Utilities for your model.
- Pick the Windows file. Look for PC/SC Driver Installer with Windows in the OS Support column. The page also lists installers for Linux, macOS and Android, which do not work on Windows. Some models also show a PC/SC Drivers package of driver files: that is for installing the driver by hand, so choose the installer unless you know you need the files.
- Write down the version and date shown next to the file. You will compare the version in Device Manager in step 3.
Download drivers only from ACS. Driver files copied to other websites may be old, unsigned or altered, which is a common cause of Code 52. BSD Infotech does not host ACS drivers; we link to the ACS page so you always get the current signed release.
Step 2: Run the ACS Driver Installer
- Sign in with an administrator account, or have an administrator ready to approve the install. On company PCs, IT may need to do this step.
- Unplug the reader and close card software, such as attendance, access-control or ACS test tools. The installer can then update the driver without a program holding the reader open.
- Extract the download. ACS packages usually arrive as a ZIP archive. Right-click it, choose Extract All, and open the extracted folder. Running an installer from inside a ZIP often fails without a clear message.
- Start the installer. Double-click the installer file in the folder (an
.msipackage or a setup program). When the User Account Control prompt appears, check that it shows a verified publisher rather than "Unknown", then click Yes. - Follow the wizard to the end and accept the default install folder unless you have a reason to change it.
- Restart if asked. If Windows or the installer asks for a restart, do it now, before you plug in the reader.
- Plug in the reader, directly into a USB port on the PC rather than a hub or dock for this first check. Wait 10 to 20 seconds while Windows sets it up. The reader's LED normally lights up.
Installing on many PCs (IT teams)
If the package contains an .msi file, it can be installed without the wizard from an administrator Command Prompt, writing a log you can keep:
Language: Windows Command Prompt (run as administrator). Prerequisites: the extracted ACS .msi file; replace the file name with yours.
Not yet tested on hardware. msiexec is the standard Windows Installer command, but we have not yet run a silent install of an ACS package. Try it on one PC before rolling it out.
msiexec /i "ACS-driver-installer.msi" /qn /l*v "%TEMP%\acs-driver-install.log"
Expected result: the command returns with no window, and the log ends with a line saying the installation completed successfully. If it fails: open the log and search for "error"; most failures are a missing administrator right or a reader program still running.
Step 3: Confirm the Reader in Device Manager
- Open Device Manager. Right-click the Start button and choose Device Manager, the same on Windows 10 and 11.
- Expand "Smart card readers". Your reader should be listed, with no yellow warning mark. Some readers create more than one entry, for example one for the contactless interface and one for a SAM slot.
- Open the Driver tab. Double-click the reader and choose Driver. Driver Provider tells you which driver is running: ACS (Advanced Card Systems) means the ACS driver; Microsoft means the built-in CCID class driver. If you installed the ACS driver but still see Microsoft, unplug the reader, plug it back in, and look again.
- Compare the version. Driver Version should match the version you noted on the ACS page. The installer version and the driver version can differ slightly, so the model guides note both where ACS gives them.
- Read the device status. On the General tab, the status should say the device is working properly. Anything else gives a code; see common errors.
The same check from PowerShell, useful over remote support:
Language: Windows PowerShell. Prerequisites: none; standard Windows commands.
Not yet tested on hardware. Both commands are part of Windows, but we have not yet recorded their output with an ACS reader.
Get-PnpDevice -Class SmartCardReader
pnputil /enum-devices /class SmartCardReader /drivers
Expected result: one line (or block) per reader entry, with a status of OK for a working reader. The second command, available from Windows 10 version 2004, also lists the driver package the reader is using.
Step 4: Check the Smart Card Service (SCardSvr)
Every PC/SC program reaches the reader through the Windows Smart Card service, whose service name is SCardSvr. Microsoft documents it as the part of Windows that manages readers and lets programs use them in turn. If the service is not running, software reports "no reader found" even when Device Manager shows the reader.
The correct startup type
Microsoft configures the service for manual start by default. It is started automatically when a smart card reader is connected, so it runs only while it is needed. In services.msc this normally appears as Manual (Trigger Start). That is the right setting: it is normal for the service to show Stopped while no reader is plugged in.
- Leave it on Manual in normal use. Setting it to Automatic is harmless but rarely needed.
- Disabled is the problem setting. If the startup type is Disabled, no reader will work. On a company PC, a policy may have set it; ask IT before you change it.
- Microsoft's default recovery setting restarts the service if it fails (after 2 minutes, then after 5 minutes), so a service that stops and starts again on its own usually points to a driver or reader problem rather than the service itself.
How to check and restart it
- Plug in the reader. Press Windows + R, type
services.mscand press Enter. - Find Smart Card in the list. Its status should be Running.
- To restart it, right-click Smart Card and choose Restart (or Start if it is stopped). Close and reopen your card software afterwards: programs that were connected to the old service session will not reconnect by themselves.
From an administrator Command Prompt or PowerShell:
Language: Windows Command Prompt / PowerShell (run as administrator). Prerequisites: none; standard Windows commands.
Not yet tested on hardware. These are standard Windows service commands; we have not yet recorded their output on a PC with an ACS reader.
sc query SCardSvr
sc qc SCardSvr
sc config SCardSvr start= demand
net stop SCardSvr
net start SCardSvr
sc query: the STATE line should say RUNNING while a reader is plugged in.sc qc: START_TYPE should say DEMAND_START, which is Manual.sc config ... start= demand: puts a Disabled service back to Manual (the space afterstart=is required).net stopthennet start: restarts the service. In PowerShell,Restart-Service SCardSvrdoes the same.
If it fails: "Access is denied" means the window is not running as administrator. If the service starts but stops at once, check Device Manager for a reader with a warning mark: the service has nothing to manage if no reader driver loaded.
How to Remove an Old ACS Driver
Remove the old driver when an update does not take effect, when Device Manager shows a code after an upgrade, or when a driver for the wrong model was installed. Do it in this order, then install the current driver fresh.
- Unplug the reader and close all card software.
- Uninstall the ACS driver package if it appears as an app: Settings > Apps > Installed apps (Windows 11) or Apps & features (Windows 10). Look for an entry from ACS / Advanced Card Systems and choose Uninstall.
- Remove the device and its driver. Plug the reader in, open Device Manager, right-click the reader under Smart card readers and choose Uninstall device. Tick the box to remove the driver for this device, then click Uninstall.
- Clear old, hidden entries. With the reader unplugged, choose View > Show hidden devices. Greyed-out readers under Smart card readers are left over from earlier connections; uninstall the ACS ones in the same way.
- Restart the PC, then install the current driver from step 1.
Advanced: remove the package from the driver store
Windows keeps a copy of each installed driver package in its driver store and can reuse an old one. If the old version keeps coming back, list the third-party packages and delete the ACS one.
Language: Windows Command Prompt (run as administrator). Prerequisites: Windows 10 version 1607 or later.
Not yet tested on hardware. pnputil is Microsoft's driver tool; the oem number differs on every PC. Delete only a package whose provider is ACS. Deleting the wrong package can stop another device from working.
pnputil /enum-drivers
pnputil /delete-driver oem12.inf /uninstall
In the output of the first command, find the entry whose Provider Name is ACS (Advanced Card Systems) and note its Published Name. Use that name in the second command in place of oem12.inf, which is only an example.
Expected result: "Driver package deleted successfully". If Windows says the package is in use, unplug the reader and run the command again; avoid the /force option unless an administrator has checked that nothing else uses the package. Never delete Microsoft's own packages: the built-in CCID driver is part of Windows and is not listed by this command.
Common Errors and Safe Fixes
Device Manager shows these codes on the reader's General tab. Work through the fixes in order. Every fix here keeps Windows security settings on: never turn off driver signature enforcement, Secure Boot or memory integrity to force a reader driver to load.
| What you see | What it means | Safe fix |
|---|---|---|
| "This device cannot start. (Code 10)" | A driver in the reader's driver stack failed to start. Microsoft's general advice is to update the driver. | Unplug and replug into another USB port directly on the PC. If it persists, remove the old driver, restart and install the current ACS driver for your exact model. Also try the reader on a second PC: if it fails there too, the reader may be faulty. |
| "Windows cannot verify the digital signature for the drivers required for this device. (Code 52)" | The driver is not correctly signed, so 64-bit Windows refused to load it. Microsoft says the only fix for users is a properly signed driver. | Remove the driver, then download it again from your model's page on acs.com.hk (not from a third-party site or an old CD) and reinstall. If the error remains with the ACS file, contact ACS or your supplier about a signed version. Do not disable signature checks. |
| Unknown device, or the reader under Other devices with a yellow mark | Windows sees a USB device but no driver is installed for it (Device Manager may show Code 28). | Install the ACS driver for the model on the label, then replug. If it is still unknown, check the model name against the ACS page: a driver for a different model will not match. |
| Code 43, often shown as "Unknown USB Device (Device Descriptor Request Failed)" | The reader did not answer Windows correctly on the USB connection. This is a connection or hardware problem, not a driver choice. | Use a different USB port on the PC, not a hub, dock or front-panel port. Try another PC. If it fails everywhere, contact your supplier about the reader. |
| Memory integrity says a driver is incompatible | Windows security found a driver that cannot run with memory integrity turned on. | Microsoft recommends getting an updated driver from the device maker. Remove old ACS packages (they may be the incompatible ones) and install the current one from acs.com.hk. Leave memory integrity on. |
| Reader listed and working, but software says "no reader found" | The Smart Card service is stopped or disabled, or another program holds the reader. | Check and restart SCardSvr, then close other card programs and reopen yours. |
| Driver tab still shows Microsoft after installing ACS | Windows kept the built-in CCID driver it had already set up. | Unplug and replug. If it still shows Microsoft, choose Update driver > Browse my computer > Let me pick and select the ACS entry, or remove the device and replug. |
Model-specific symptoms, such as an NFC reader that appears as a keyboard, are covered in the model guides below.
Driver and Test Guides for Each ACS Reader
This page is the general method. The model guides give the exact ACS download for each reader, the driver version to expect in Device Manager, and how to test the reader with a card.
| Reader | Guide | What the guide adds |
|---|---|---|
| ACR1252U (USB NFC Reader III) | ACR1252U driver, software and test guide | The ACR1252U Windows package and version, ACS tools and the BSD ACR1252U utility |
| ACR1552U (USB NFC Reader IV) | ACR1552U driver and test guide | Driver version check, the SAM slot entry, keyboard mode and ISO 15693 tags |
| ACR122U (USB NFC Reader) | ACR122U driver and software guide | Which of the two ACR122U Windows packages to use, UID test without code, end-of-life note |
| ACR39U (contact smart card reader) | ACR39U smart card reader | Models, supported cards and operating systems (a separate driver guide is not yet published) |
| Any ACS reader | ACS reader testing and utilities centre | Which free tool to use to test the reader once the driver is installed |
Sources
ACS directory structure, file names, OS columns and CCID/PC/SC compliance were checked on the official ACS pages on 16 Nov 2026. Windows driver, service and error-code facts were checked in Microsoft's documentation on the same day.
- ACS Drivers / Manuals / Datasheets directory
- ACS ACR1252U drivers and utilities and ACS ACR39U drivers and utilities (examples of the page layout)
- ACS ACR1252U product page and ACS ACR39U product page (CCID and PC/SC compliance)
- Microsoft: USB device class drivers included in Windows
- Microsoft: Smart Cards for Windows service
- Microsoft: Code 10 and Code 52 device errors
- Microsoft: PnPUtil command syntax
- Microsoft Support: Core isolation and memory integrity
BSD Infotech is an independent ACS supplier and integrator, not the manufacturer. ACS, the ACS logo and ACS product names belong to Advanced Card Systems Ltd. Windows is a trademark of Microsoft Corporation.
