How to Check Whether an ACS Reader Is Detected by Windows
← Back to the ACS testing and utilities centre
How do you know if Windows has detected your ACS reader? Open Device Manager and expand Smart card readers. If the reader is listed there with no warning mark and its status says the device is working properly, Windows has detected it and loaded a driver. If it is not there, look under Other devices, Universal Serial Bus devices or Keyboards: where it shows up tells you what is wrong. To confirm that card software can reach it too, run certutil -scinfo or check that the Smart Card service is running.
"Detected" can mean three different things, and a reader can pass one and fail the next. This guide shows every place Windows 10 and 11 list a reader, what the entries and names mean, two command-line checks you can run or send to support, and what to do when the reader is missing, shows a warning or appears as an unknown device. It assumes the driver is already installed; if it is not, start with installing ACS reader drivers on Windows 10 and 11. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer.
The Three Levels of "Detected"
Work through them in order. Each level depends on the one above it, so a failure at the first level hides everything below it.
| Level | Where you check | What a pass proves |
|---|---|---|
| 1. USB: Windows sees a device on the port | Device Manager, any category; the reader's LED | Power, cable and USB connection work. It says nothing yet about the driver. |
| 2. Driver: Windows knows it is a smart card reader | Device Manager > Smart card readers, with no warning mark; Get-PnpDevice | A reader driver (ACS or the built-in Windows one) loaded and started. |
| 3. PC/SC: card software can use the reader | certutil -scinfo; the Smart Card service | The Windows Smart Card service sees the reader, so PC/SC programs can open it. |
Passing level 3 means detection is solved. Testing what the reader does with a card (does it see the card arrive and leave, does it read the UID) is the next step, covered on the testing and utilities centre.
Where an ACS Reader Can Appear in Device Manager
Device Manager is the most complete view, and it looks the same on Windows 10 and Windows 11. Open it by right-clicking the Start button and choosing Device Manager, or press Windows + R, type devmgmt.msc and press Enter.
- Unplug the reader, then plug it straight into a USB port on the PC (not a hub, dock or monitor port). Keep Device Manager open: the list redraws when a device arrives or leaves.
- Expand Smart card readers. This is where a working reader belongs. The category only exists while at least one reader is present, so if you cannot see the heading at all, no reader driver is loaded right now.
- If the reader is not there, check the other categories in the table below. A new or changed entry that appears as you plug in and disappears as you unplug is your reader.
- If nothing changes at all, choose Action > Scan for hardware changes, which Microsoft suggests when a reader is not listed. If still nothing appears, Windows is not seeing the device on the USB port: go to not detected.
| Where it appears | What it means | Next step |
|---|---|---|
| Smart card readers, no warning mark | Detected, and a reader driver is running. This is the result you want. | Open it and read the status (see below), then check level 3. |
| Smart card readers, with a yellow warning mark | Windows knows it is a reader, but the driver failed to start or has a problem. | Read the code on the General tab; see reader with a warning. |
| Other devices, often as "Unknown device" or with the model name and a warning mark | Windows sees a USB device but has no driver for it. | Install the ACS driver for the model on the label; see unknown device. |
| Universal Serial Bus devices or Universal Serial Bus controllers, as an unknown USB device with a warning | The device did not identify itself properly on the USB connection. This is a connection or hardware issue, not a driver choice. | Change port and cable route; try another PC. |
| Keyboards or Human Interface Devices, and not under Smart card readers | Possible on readers that support keyboard emulation, such as the ACR1552U. ACS describes this mode as HID keyboard output, not CCID, so PC/SC software will not see the reader. | Use the reader's ACS configuration tool to check the mode; see the ACR1552U guide. |
| A warning entry that appears only while a card is on the reader | This is the card, not the reader. Windows' smart card Plug and Play looks for a driver (minidriver) for the inserted card, which a MIFARE, NTAG or memory card does not have. | The reader is fine if it stays under Smart card readers without a warning. Your card software can still use the card. |
Read the reader's status
Double-click the entry under Smart card readers. On the General tab, the Device status box should say the device is working properly. Any other text includes a code number; note it, because it tells you which fix applies. The Driver tab shows which driver is running (ACS or Microsoft) and its version; the driver installation guide explains how to read it.
Two Device Manager views that help
- View > Show hidden devices. With the reader unplugged, greyed-out entries under Smart card readers are readers that were connected before, for example on another USB port. They prove the reader was detected at some point, and they are harmless. Several greyed copies of the same reader usually just mean it has been used on several ports.
- View > Devices by connection. Lists devices under the USB controller and hub they are plugged into. It helps when you are not sure which unknown entry is the reader: unplug and replug, and watch which branch changes.
What the Reader Names in Windows Mean
Device Manager shows the name the driver gives the reader, and PC/SC software shows the reader name the Smart Card service reports. The two are often similar but do not have to be identical. Three things affect what you see:
Which driver is running
With the ACS driver installed, the name normally includes ACS and the model family, for example ACR1252, ACR1552 or ACR122. With the built-in Windows CCID driver, Device Manager can show a generic Microsoft reader name instead of the model. Both are "detected"; the driver guide explains when to switch to the ACS driver.
One entry per card interface
Windows creates one smart card reader entry for each card interface the reader reports. A reader with a contactless antenna and a SAM slot, such as the ACR1252U or ACR1552U, can therefore appear twice: once for the contactless (PICC) interface where you tap cards, and once for the SAM slot. Two entries are normal and do not mean the driver installed twice. In card software, pick the contactless entry to test a tapped card. A single-slot contact reader such as the ACR39U shows one entry.
The exact names differ by model and driver version, so we do not list them here. To check what your model should report, look in the reference or API manual on the model's ACS drivers and manuals page, or compare with a second reader of the same model.
Hardware IDs: proof of what is plugged in
When the name is unclear, or the device is listed only as unknown, the hardware ID identifies it. Double-click the entry, open the Details tab and choose Hardware Ids from the Property list.
- USB devices show IDs in the form
USB\VID_xxxx&PID_yyyy: VID is the vendor code assigned to the manufacturer and PID the product code the manufacturer assigns to the model. The same VID on an unknown device and on a working ACS reader tells you the unknown device is made by the same vendor. - A reader with several interfaces adds
&MI_zz, the interface number. Two entries with the same VID and PID but different MI numbers are the two interfaces of one reader, as described above. - Under Compatible Ids, a class code of
0Bmarks a smart card (CCID) interface, the USB class Windows' built-in reader driver serves.
The Details tab is also the quickest thing to copy for a support request: right-click the value and choose Copy.
Checking in Settings and Devices and Printers
These views are easier to find than Device Manager but show less: no category, no status code and no driver details. Use them for a quick "is it plugged in" check, then go to Device Manager for anything more.
- Windows 11: Settings > Bluetooth & devices > Devices. Wired USB devices are listed under Other devices. Look for an entry that appears when you plug the reader in.
- Windows 10: Settings > Devices > Bluetooth & other devices, then the Other devices list.
- Devices and Printers (Control Panel > Hardware and Sound): shows each connected device as an icon, with a warning symbol if Windows reports a problem. On recent Windows 11 versions this link may open the Settings page above instead.
A reader that appears here but not under Smart card readers in Device Manager is at level 1 only: Windows sees a USB device, but no reader driver is running. A reader that is missing here and in Device Manager is not being seen on the USB port at all.
Check Detection from PowerShell
Get-PnpDevice is a standard Windows PowerShell command that lists Plug and Play devices. It is useful for remote support, because the person at the PC can copy the text instead of describing a screen. A normal (non-administrator) PowerShell window is enough.
Language: Windows PowerShell (Windows 10 or 11). Prerequisites: none; the PnpDevice module is part of Windows.
Not yet tested on hardware. These are documented Windows commands, but we have not yet recorded their output with an ACS reader connected. The output below is described in general terms.
# 1. Readers connected right now
Get-PnpDevice -Class SmartCardReader -PresentOnly
# 2. Every reader Windows has seen, including unplugged ones
Get-PnpDevice -Class SmartCardReader
# 3. Any connected device with a problem (finds an unknown device or a reader with a code)
Get-PnpDevice -PresentOnly -Status ERROR,DEGRADED,UNKNOWN
Expected result: each command prints a table with the columns Status, Class, FriendlyName and InstanceId. For a detected, working reader, command 1 prints one line per reader entry (two for a reader with a SAM slot) with Status OK and Class SmartCardReader; the InstanceId starts with the USB hardware ID described above. Command 2 can also list readers that are not connected now; those do not show OK. If command 1 prints nothing, no reader driver is loaded at this moment.
If it fails: if command 1 is empty, run command 3 with the reader plugged in. An entry there whose InstanceId begins with USB\VID_ and that disappears when you unplug the reader is the reader without a working driver: see not detected. To see the full text of a long line, add | Format-List to the end of the command.
Check What the Smart Card Service Sees: certutil -scinfo
Device Manager proves the driver loaded. certutil -scinfo checks level 3: it asks the Windows Smart Card service which readers it can use, then looks at the card in each one. certutil is built into Windows. Microsoft documents -scinfo as the command to list the certificates on a smart card, but the first part of its output is a quick, reliable reader check for any card type.
Language: Windows Command Prompt or PowerShell. Prerequisites: the reader plugged in; a card on or in the reader is optional.
Not yet tested on hardware. certutil is a standard Windows tool; we have not yet recorded its output with an ACS reader, so the description below is general.
certutil -scinfo
Expected result: near the top, certutil reports whether the Smart Card resource manager (the Smart Card service) is running, then lists the readers it can see, with each reader's name and whether a card is present. If your ACS reader's name is in that list, PC/SC software can reach it. The rest of the output is about certificates on the card.
- Errors about certificates or keys are expected with MIFARE, NTAG, DESFire or memory cards, which carry no Windows certificates. They do not mean the reader failed.
- If you are asked for a PIN, press Esc. Microsoft notes that no PIN is needed for this command.
- If certutil says the service is not running or lists no readers while Device Manager shows the reader, the problem is at the service level: see the next section.
For a full PC/SC-level check, including listing readers and testing communication from software, see how to check PC/SC reader status and reader communication.
The Smart Card Service: Detected but "Not Found"
The most confusing case is a reader that looks fine in Device Manager while every program says "no reader found". The usual cause is the Windows Smart Card service (service name SCardSvr): every PC/SC program reaches the reader through it. Microsoft sets it to start on demand when a reader is connected, so "Stopped" with no reader plugged in is normal.
Quick check, with the reader plugged in: press Windows + R, type services.msc, find Smart Card and confirm the status is Running. Or run sc query SCardSvr and look for RUNNING on the STATE line. If it is stopped or Disabled, follow the restart and startup-type steps in the driver guide's Smart Card service section, then close and reopen your card software.
What to Do When the Reader Is Not Detected
Find the case that matches what Device Manager shows. Every step keeps Windows security settings as they are: you never need to turn off driver signature checks or memory integrity to make an ACS reader appear.
Case 1: Nothing appears anywhere
No new entry in any Device Manager category, nothing in Settings, and the list does not change when you plug in. Windows is not seeing a USB device, so no driver can help yet.
- Look at the reader's LED. On most ACS readers it lights when the reader has power. No light at all points to the port, the cable or the reader.
- Use a different USB port on the PC itself, preferably at the back of a desktop. Avoid hubs, docks, keyboard ports and monitor ports for this test.
- If the cable is detachable (for example a USB-C model), try another cable that you know carries data, not only charging.
- Choose Action > Scan for hardware changes in Device Manager.
- Try a second PC. If the reader appears there, the first PC's port or USB policy is the cause; on a company PC, IT may block unknown USB devices. If it appears nowhere, contact your supplier about the reader.
Case 2: The reader appears, but with a warning
Double-click the entry and read the code on the General tab. The common ones:
- Code 10 (device cannot start) or Code 52 (digital signature not verified): a driver problem. Remove the old driver and reinstall the current one from acs.com.hk, as the driver guide's error table describes.
- Code 43, often shown as an unknown USB device whose device descriptor request failed: a USB connection problem. Work through case 1.
- Code 28 (drivers not installed): treat it as case 3.
After any fix, unplug the reader, wait a few seconds and plug it back in, then check the status again.
Case 3: Unknown device or Other devices
- Confirm it is the reader. Unplug and replug: the entry should disappear and return. Its hardware IDs (Details tab) should begin with
USB\VID_. - Read the model on the reader's label and install the Windows PC/SC driver from that model's ACS page. The model guides below link to the right page for the ACR1252U, ACR1552U and ACR122U.
- Unplug and replug after the install, then check Smart card readers again.
- Still unknown? The driver may be for a different model. ACS publishes drivers per model, and a package for one model does not match another's hardware IDs.
Case 4: Detected, but it keeps disappearing
An entry that comes and goes on its own, without you touching the reader, points to the USB connection: a loose port, a long extension cable or an unpowered hub. Connect directly to the PC. If you are using a laptop, check whether Windows power saving turns off the USB port: on the USB Root Hub entries under Universal Serial Bus controllers, the Power Management tab (where present) has an option to let the computer turn the device off to save power.
| What you see | Likely cause | What to do |
|---|---|---|
| No entry anywhere, reader LED off | No power or no USB connection | Another port directly on the PC, another cable, another PC (case 1) |
| Unknown device under Other devices | Driver missing or for a different model | Install the ACS driver for the model on the label (case 3) |
| Under Smart card readers with a yellow mark | Driver failed to start or is not trusted | Read the code; reinstall the driver from acs.com.hk (case 2) |
| Under Keyboards or Human Interface Devices only | Reader set to keyboard emulation mode | Check the mode with the ACS configuration tool for your model |
| Listed and OK, but software says "no reader found" | Smart Card service stopped or disabled | Start the service (Smart Card service), reopen the software |
| Two entries for one reader | Normal: one per interface (contactless and SAM) | Choose the contactless entry in your software |
| Greyed-out readers with Show hidden devices | Readers used earlier on other ports | Nothing; they are harmless |
| Warning entry only while a card is on the reader | Windows looking for a driver for the card, not the reader | Ignore it if the reader itself stays OK |
What to send to support
If you contact BSD Infotech or ACS about a reader that is not detected, these four items answer most first questions: a screenshot of Device Manager with Smart card readers (and any warning entry) expanded; the General tab of the reader's Properties; the Hardware Ids from the Details tab; and the text output of Get-PnpDevice -Class SmartCardReader. Add the model from the label and your Windows version (Settings > System > About).
What to Look For on Each ACS Reader
The method above works for any ACS USB reader. These points are specific to the models BSD Infotech supplies most often; the guides cover the driver and card tests for each.
| Reader | What to expect in Device Manager | Guide |
|---|---|---|
| ACR1252U (USB NFC Reader III) | Under Smart card readers, a name containing ACR1252 with the ACS driver. It has a SAM slot, so expect a contactless entry and a SAM entry. | ACR1252U driver, software and test guide |
| ACR1552U (USB NFC Reader IV) | Under Smart card readers, a name containing ACR1552 with the ACS driver; can show two entries, the second usually for the SAM slot. In keyboard emulation mode it appears as a keyboard instead. | ACR1552U driver and test guide |
| ACR122U (USB NFC Reader) | Under Smart card readers, a name containing ACR122 with the ACS driver. | ACR122U driver and software guide |
| ACR39U (contact reader) | One entry under Smart card readers for its single card slot. | ACR39U smart card reader |
Sources
Windows facts were checked in Microsoft's documentation, and ACS model facts on the official ACS pages, on 16 Nov 2026:
- Microsoft: Smart card troubleshooting (certutil -scinfo, the Smart Card service, Device Manager and Scan for hardware changes)
- Microsoft: Get-PnpDevice (parameters, status values, output columns)
- Microsoft: Standard USB identifiers (VID, PID and MI in hardware IDs)
- Microsoft: USB device class drivers included in Windows (smart card class 0Bh)
- Microsoft: Smart Cards for Windows service
- ACS Drivers / Manuals / Datasheets directory and the ACS ACR1552U drivers and manuals page
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.
