ACR1252U Driver, Software and Reader Test Guide
← Back to the ACS testing and utilities centre
Which ACR1252U driver do you need, and how do you prove the reader works? For Windows 10 and Windows 11, download the Windows PC/SC Driver Installer from the official ACS ACR1252U download page (version 4.4.2.1 when we checked) and run it before you connect the reader. Then check three things in order: the reader is listed under Smart card readers in Device Manager, the Windows Smart Card service is running, and a test tool such as ACS QuickView or the free BSD ACR1252U utility sees a card arrive and leave. Pass all three and the reader, its driver and the Windows PC/SC layer are working.
The ACR1252U has two things most low-cost NFC readers lack: a built-in SAM slot and NFC Forum certification. Both change how the reader appears in Windows and what you can test, so this guide explains them alongside the usual setup steps. For the price, specifications and connector versions, see the ACR1252U USB NFC Reader III page. BSD Infotech is an independent ACS supplier and integrator, not the manufacturer: driver and ACS tool links on this page go to acs.com.hk, and BSD's own software is labelled as BSD software.
Before You Start: What to Have Ready
- The reader, and which version it is. ACS sells the ACR1252U with a USB Type-A plug (order code ACR1252U-M1) or a USB Type-C plug (ACR1252U-MF). The 1 m cable is fixed, so plug it into a matching port on the PC itself for the first test. Adapters, docks and monitor hubs add a second thing that can fail.
- A Windows 10 or 11 account that can install drivers. The installer asks for administrator approval.
- Cards you are free to experiment with. A MIFARE Classic 1K card, an NTAG sticker and a DESFire card between them exercise every part of the reader that a typical project uses. Keep them on their factory keys if you want to try the free BSD utility, and never use a card that is already enrolled in a live system.
- One card at a time. ACS states that the ACR1252U's anti-collision feature lets it work with only one tag at any moment. Two cards stacked on the reader, or a card left in a wallet next to another, gives confusing results.
- Other card programs closed. Attendance, access-control or other test software that is already connected to the reader can stop a new tool from reaching the card.
Setting up several ACS models, or rolling drivers out across many PCs? The guide to installing ACS reader drivers on Windows 10 and 11 covers the method for every model.
Step 1: Choose the Right ACR1252U Driver
The ACS ACR1252U drivers and manuals page (acs.com.hk, free, no form) offers two packages that run on desktop Windows. They are easy to mix up, because both are called "PC/SC":
| File name on the ACS page | Version, ACS date, size | Windows listed by ACS | Our advice |
|---|---|---|---|
| PC/SC Driver Installer (OS column: Windows) | 4.4.2.1, 11 Dec 2025, 5.02 MB | "Windows", with no versions named | Start here on Windows 10 and 11. It is the most recent Windows release for this reader and installs like any other Windows program. |
| PC/SC Drivers | 4.2.8.0, 20 Mar 2018, 955.93 KB | Windows XP to Windows 11, and Windows Server 2003 to 2016 R2 | A fallback for older or server systems, or for IT teams that deploy driver files with their own tools. |
We copied these details from the ACS ACR1252U download page on 16 Nov 2026. Files there can change without notice, so download from the ACS page on the day and note the version you installed. The same page lists Linux and macOS installers, an Android library, the ACS ApduTool for iPhone and iPad, a Windows CE driver, the technical specification and the API driver manual. The full ACR1252U download table on the product page lists every one of them with its date.
Only from ACS. BSD Infotech does not host ACS driver files. A driver copied to a download site can be outdated or modified, and you lose the ability to check its version against the manufacturer's list.
Step 2: Install the ACR1252U Driver on Windows 10 or 11
Windows 10 and Windows 11 use the same steps; only the dialog styles differ.
- Disconnect the ACR1252U before you start, so that Windows meets the reader for the first time with the ACS driver already in place.
- Unpack the download. If the browser saved a ZIP file, right-click it and choose Extract All. Then open the new folder and find the setup program.
- Run the setup program and choose Yes at the User Account Control prompt. If Microsoft Defender SmartScreen warns about the file, confirm it came from acs.com.hk before you allow it.
- Finish the installer, and restart the PC if it asks.
- Connect the reader and give Windows up to half a minute. The reader's LED should light, and the PC may announce that a device is being set up.
Reader connected before the driver? No harm done. The ACR1252U is a USB CCID reader and ACS lists Microsoft WHQL among its certifications, so Windows may already have set it up, either with its built-in CCID driver or with a driver from Windows Update. Run the ACS installer anyway, then disconnect and reconnect the reader. Step 3 shows how to see which driver Windows ended up using.
Step 3: Check the Reader in Device Manager and the Smart Card Service
Device Manager
- Right-click Start and open Device Manager.
- Open the Smart card readers group. The ACR1252U should be there with no yellow warning triangle, under a name that includes ACR1252.
- Double-click the entry and open the Driver tab. Note the Driver Provider and Driver Version. A provider of ACS (Advanced Card Systems) means the ACS driver is in use. The version shown here is the driver file's own number and may not be the same as the installer's 4.4.2.1, so keep a note of it as your reference for this PC.
- Disconnect the reader and watch the entry vanish, then reconnect and watch it return. An entry that flickers or disappears on its own points to the USB port or cable route, not the driver.
No entry under Smart card readers? An unknown device marked with a warning sign under Other devices or Universal Serial Bus devices is probably the reader without a driver: see the troubleshooting table.
Why software shows two ACR1252U readers
Because the ACR1252U has a SAM slot as well as its antenna, PC/SC programs usually list it as two readers: one name for the contactless interface, typically ending in PICC, and one for the SAM slot, typically ending in SAM. This is normal and does not mean a second device is attached. For every card test on this page, choose the PICC entry. A tool pointed at the SAM entry reports that no card is present, however you hold the card, because the SAM slot only takes a SIM-sized SAM chip, not a contactless card.
The Windows Smart Card service
Windows routes all PC/SC traffic for the ACR1252U through this service, whichever program sends it: an ACS tool, the BSD utility or an application you wrote. With the service down, those programs claim there is no reader, while Device Manager still lists it.
- Open the Run box with Windows + R, type
services.mscand confirm. - Scroll to the service called Smart Card. While the ACR1252U is plugged in, its status should read Running. Windows starts it on demand, so Stopped is normal while no reader is attached.
- Stopped even though the reader is plugged in? Right-click the service and pick Start. A startup type of Disabled usually comes from company policy, so ask your IT team before you change it.
From a Command Prompt, sc query SCardSvr gives the same answer: look for RUNNING on the STATE line.
Step 4: Test the ACR1252U with Free ACS Tools
ACS's free tools are on its utility tools page. The tools are listed for ACS PC/SC readers as a family, not per model; the ACR1252U is one of those readers. Its own download page adds one more, the ACS ApduTool for iOS. These are the ones worth using, in this order:
QuickView: is the card seen?
Open QuickView and select the ACR1252U PICC reader. Place a MIFARE Classic 1K card flat on the reader: QuickView should report a card present and show its details, such as the ATR. Lift it away and it should report the card gone. Repeat with the NTAG and the DESFire card. Clean arrivals and removals for all three are a pass.
Windows, macOS and Linux versions (v2.18 when checked) · ACS utility tools page
Script Tool: what does the reader answer?
Sends APDU commands and shows the reader's exact response, byte by byte. It is the tool for the UID command in reading a card UID, and for checking any command before it goes into your own code.
Windows (5.2 when checked), with separate macOS and Linux editions · ACS utility tools page
Smart Card and Reader Tool: MIFARE without commands
Ready-made widgets for card functions. ACS lists MIFARE Classic, Ultralight and Ultralight C among its cards, so you can load the factory key FF FF FF FF FF FF and read a block of a MIFARE Classic 1K card. DESFire is not in its list. ACS describes the NFC and NDEF tools for the ACR1252U's peer-to-peer and card emulation modes as part of the ACR1252U SDK edition of this tool.
Windows (v4.0.1.8 when checked) · ACS utility tools page
Web APDU Tool: commands from Chrome or Edge
A browser version of the command test, for PCs where installing a desktop tool is awkward. It needs ACS's APDU Bridge browser extension and a small bridge program. ACS states that it supports all its USB smart card readers and Windows 10 or later.
Chrome or Edge · ACS Web APDU Tool page
Not for the ACR1252U: the ACS keyboard configuration tool, which turns some ACS readers into a device that types card UIDs as keystrokes, lists other models and not the ACR1252U. Treat the ACR1252U as a PC/SC reader that needs software to read cards. The ACS testing and utilities centre compares every ACS and BSD tool across reader models.
Step 5: Read and Write Test Cards with the BSD ACR1252U Utility
QuickView proves the card is seen. To go one step further and work with the data on the card without programming, BSD Infotech publishes its own ACR1252U NFC Card Utility, a Windows 10 and 11 program. BSD Infotech wrote and supports it; it is not made, sold or supported by ACS.
BSD ACR1252U NFC Card Utility: how to get it and what it covers
- Download: free, after a one-time email check. Pick the ACR1252U utility in the download box, fill in your details and enter the one-time password (OTP) that arrives by email. The download then starts.
- Factory keys only in this edition: the Default Key edition works with MIFARE Classic cards still on the factory key
FF FF FF FF FF FF, and handles DESFire cards for reading and writing as long as nobody has changed their factory (all-zero) keys. - Licence: detecting the reader and the card costs nothing; reading and writing card data needs a licence key from BSD Infotech.
- Your own keys? Cards that already carry your keys need the Custom Key edition: ask for the Custom Key edition.
A short test session with the three common card types
- Reader, beep and LED (free). Start the utility with the reader connected. It should find the ACR1252U and can show the reader's firmware. Its beep and LED tests use the reader's own buzzer and red/green LED, which ACS describes as controllable by software: a quick way to confirm the PC can send commands to the reader, not just receive card events.
- Card detection (free). Tap the MIFARE Classic 1K card, then the NTAG, then the DESFire card. Each should be recognised as its card type.
- MIFARE Classic 1K (licence). Read all sectors, put a short text into an unused data block, then read that block again: the text should come back unchanged.
- NTAG (licence). Write a short web link, then tap the tag with a phone: the link should open. That checks the write and the tag's NDEF format in one go.
- DESFire (licence). Write and read back a test file on a new card. If the card's keys were changed earlier, this edition cannot open it. That is expected and not a reader fault.
Writing changes what is stored on a card, so keep every write test to spare cards that belong to you.
Read a Card UID on the ACR1252U Without Writing Code
The UID is the identifier the card reports when the reader selects it. Plenty of attendance, canteen and door systems use nothing else. You can see it in two ways without programming.
With one command in the Script Tool or Web APDU Tool
- Select the ACR1252U PICC reader, not the SAM reader (see two reader names).
- Place one card on the reader and leave it still.
- Send
FF CA 00 00 00. This is the standard PC/SC Get Data command that asks the reader, rather than the card, for the UID, so it works the same way across card types. - The reply is the UID followed by
90 00, which means the command succeeded. Any other ending usually means the card moved or was not there when the command ran: place it again and resend.
Not yet tested on hardware. BSD has not yet sent this command to an ACR1252U with each of the three card types; the results will be added after our bench test. The ACR1252U API driver manual on the ACS download page is the reference for the reader's commands and status words.
With the BSD utility
When the BSD ACR1252U utility detects a card it shows the card's identity, which is free and needs no licence. For FeliCa and other ISO 14443-4 cards, identity is all this utility shows.
What UID length to expect
| Card | Usual UID length | Worth knowing |
|---|---|---|
| MIFARE Classic 1K | 4 bytes, or 7 bytes on 7-byte UID versions | ACS lists MIFARE 7-byte UID support for the ACR1252U, so both kinds should read. If your system expects 4 bytes, check which kind of card you bought. |
| NTAG (NFC Forum Type 2 tag) | 7 bytes | The first byte is the chip maker's code, so tags from one maker share it. |
| DESFire | 7 bytes | If the card's random-ID option has been switched on, it gives a different 4-byte value on every tap. A UID that never repeats is a card setting, not a reader fault. |
Ready to read the UID in your own application? The ACR1252U SDK and developer resources page covers the programming side.
SAM Slot, NFC Forum Certification and NFC Modes: What They Mean for Testing
These features are confirmed on the ACS ACR1252U product page. Here is how each one affects setup and testing.
The SAM slot
Inside the ACR1252U is one slot for a standard SIM-sized SAM (Secure Access Module) card. ACS specifies it as ISO 7816 Class A (5 V) with the T=0 and T=1 protocols. A SAM holds secret keys inside a chip, so an application can derive card keys or authenticate cards without exposing the keys on the PC. That matters for payment, transport and high-security access systems, and not at all for simple UID or NDEF projects.
- The slot is not a card reader for bank or ID cards. Only a SAM-format chip fits.
- An empty slot is normal. The SAM reader entry in Windows simply shows no card.
- To check the slot, switch off the PC or disconnect the reader, fit a SAM, reconnect, and select the SAM entry in QuickView: it should report a card present with an ATR.
Not yet tested by BSD. Our test bench has no SAM card at the moment, so the SAM check above is based on ACS's specification and normal PC/SC behaviour. ACS includes an ACOS6-SAM card in its ACR1252U SDK kit for this purpose.
NFC Forum certification
The ACR1252U carries the NFC Forum Certification Mark, which means it passed the NFC Forum's interoperability tests. ACS states that it reads all four NFC Forum tag types defined over ISO/IEC 18092. For you, this means NFC stickers and cards formatted by phones and other certified devices should behave predictably. NTAG stickers are Type 2 tags, so they are the simplest way to test it: write a link with the BSD utility, then check it on a phone, or the other way round.
The three NFC modes
| Mode | What the reader does | How to test it |
|---|---|---|
| Reader/writer | Reads and writes cards and tags. This is the mode every step on this page uses. | QuickView, Script Tool and the BSD utility, as above. |
| Card emulation | The reader behaves like a contactless card towards another reader or phone. | Needs commands from the ACR1252U API driver manual or the SDK tools. Not covered by the free tools or the BSD utility. |
| Peer-to-peer | Exchanges data directly with another NFC device. | Needs software on both sides. Many current phones no longer include a built-in peer-to-peer sharing feature, so plan this test around your own app. |
ACS also states that the ACR1252U works with FIDO authenticators over NFC, for passwordless sign-in. That depends on the browser or service, not on a setting in the reader.
What the ACR1252U does not do
It reads 13.56 MHz contactless cards only. Contact chip cards have nowhere to go (the only slot is for a SAM), 125 kHz proximity badges are outside its frequency, and ACS does not list ISO 15693 vicinity tags, the kind used on library books and industrial labels, among its cards. For ISO 15693, see the ACR1552U driver and test guide.
ACR1252U Not Working? Troubleshooting Table
Fix the first problem that matches. A fault near the top of the table can hide the ones below.
| What you see | Likely cause | What to do |
|---|---|---|
| No LED, and Device Manager does not change when the reader is connected | USB port, hub, dock or adapter | Connect straight to the PC. On the Type-C model, try a different Type-C port before blaming the reader. Try a second PC if you have one. |
| Unknown device with a yellow warning mark | Driver missing or the installation failed | Run the ACS Windows PC/SC Driver Installer again from the ACS ACR1252U page, then disconnect and reconnect. |
| The Driver tab shows Microsoft, not ACS | Windows set the reader up with its built-in CCID driver first | Install the ACS package and reconnect the reader. If Microsoft is still shown, use Update driver > Browse my computer > Let me pick and choose the ACS entry. |
| Device Manager is fine, but every tool says no reader is installed | The Windows Smart Card service is not running | Start it as shown in step 3. If a policy has disabled it, involve IT. |
| The tool lists the reader, but a card on it is never detected | The SAM reader entry is selected instead of PICC | Select the entry ending in PICC (two reader names). |
| Two cards on the reader, and only one, or neither, is read | The reader works with one tag at a time | Remove the other card. Keep wallets and phones off the reader during tests. |
| A card is not detected at all, on the PICC entry | Unsupported card (contact chip card, 125 kHz card, ISO 15693 tag) or poor placement | Test with a 13.56 MHz ISO 14443 card (MIFARE Classic 1K or NTAG are ideal), lying flat on the centre of the reader with no metal close by. |
| Tapping a card types nothing into Notepad | Expected: the ACR1252U has no keyboard-emulation setting in ACS's tools | Use a PC/SC tool, the BSD utility or your own application to read the UID. |
| A DESFire card shows a different UID on every tap | The card's random-ID option is on | Normal for that card setting. Use a card without random ID, or identify the card by its application data. |
| MIFARE Classic data cannot be read, although the UID is shown | The card no longer uses the factory key | Use the card's real key. The BSD Default Key edition reads factory-key cards only: ask for the Custom Key edition. |
| The BSD utility detects cards but will not read or write | No licence key, or the card's keys are not the factory keys | Check the licence status in the utility, then retest with a new card. |
| A tool worked a moment ago but now reports a sharing or connection error | A second program has opened the card exclusively | Quit the other card programs, test tools included, then retry in one tool only. |
No row matches? Tell BSD Infotech which Windows version you use, what Device Manager lists and which card you tried, and we will look at it.
Sources
Driver files, versions, dates and sizes, the supported cards, the SAM slot specification, NFC modes, certifications and tool names were checked on these official ACS pages on 16 Nov 2026. ACS updates its downloads, so check the ACS page before you install.
- ACS ACR1252U drivers, manuals and datasheets (Windows PC/SC Driver Installer 4.4.2.1; PC/SC Drivers 4.2.8.0; ACS ApduTool for iOS 1.2; API driver manual)
- ACS ACR1252U product page (M1 and MF connector versions, SAM slot ISO 7816 Class A, three NFC modes, NFC Forum Certification Mark, Microsoft WHQL, one tag at a time, FIDO)
- ACS ACR1252U SDK (kit contents, including the ACOS6-SAM card and the NFC and NDEF tools)
- ACS utility tools (QuickView v2.18, Script Tool 5.2, Smart Card and Reader Tool v4.0.1.8, ACR15XX Keyboard Configuration Tool model list)
- ACS Web APDU Tool (all ACS USB readers; Windows 10 or later; Chrome or Edge)
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. Other card and technology names belong to their owners.
