SD card reader not working in Windows
DeviceInBox editorial team · Last updated October 6, 2026
A card reader that stopped working has a short list of causes: the reader has no driver and sits under Other devices, the driver is there but the reader was put to sleep for power saving, or the card itself is at fault. Built-in readers on laptops are PCI Express devices from Realtek, O2Micro or Genesys; readers in USB hubs and dongles are USB devices, and the two need different drivers.
Is the reader there at all?
Insert a card first: some readers only appear once a card is in. Then check Device Manager under Memory technology devices, Universal Serial Bus controllers and Other devices. A reader without a driver shows up as Base System Device, Unknown device or SD Host Controller.
Read its hardware ID (how). The common ones:
| Hardware ID | Device | Drivers |
|---|---|---|
| PCI\VEN_10EC&DEV_5227 | RTS5227 PCI Express Card Reader | 10 |
| PCI\VEN_10EC&DEV_522A | RTS522A PCI Express Card Reader | 10 |
| PCI\VEN_10EC&DEV_525A | RTS525A PCI Express Card Reader | 10 |
| PCI\VEN_10EC&DEV_5229 | RTS5229 PCI Express Card Reader | 3 |
| PCI\VEN_1217&DEV_8621 | Integrated MMC/SD controller | 18 |
| PCI\VEN_1217&DEV_8620 | Integrated MMC/SD controller | 20 |
| USB\VID_0BDA&PID_0129 | RTS5129 Card Reader Controller | 21 |
| USB\VID_05E3&PID_0751 | microSD Card Reader | 9 |
- Realtek PCIE CardReader Driver 10.0.26200.21389 (Apr 26, 2026, Windows 10, 11)
- Alcorlink USB Smart Card Reader Driver (ARM64) 1.10.7.1002 (Mar 10, 2026, Windows 11)
- Realtek PCIE CardReader Driver 10.0.26200.21388 (Jan 21, 2026, Windows 11)
- Alcorlink USB 2.0 Card Reader Driver 2.0.160.24533 (Oct 15, 2025, Windows 10, 11)
The power saving trap
Realtek readers are the usual suspects here: the reader works after a restart and is gone after the laptop sleeps.
- Properties of the reader, Power Management tab, clear "Allow the computer to turn off this device to save power".
- In Control Panel, Power Options, Change plan settings, Change advanced power settings, open PCI Express, Link State Power Management, and set it to Off for both battery and mains.
- Restart and test with a card inserted and the lid closed once.
Rule out the card
- Try a second card. A card that fails in two readers is the problem.
- Check the physical lock switch on full-size SD cards. In the lock position the card mounts read-only or not at all.
- Open Disk Management (Win + X): a card that appears there with no drive letter only needs one assigned.
- Cards over 32 GB are usually exFAT. Very old readers and card firmware handle SDXC badly; in that case the card works in a USB reader but not in the built-in one.
Reinstall the driver
- Right-click the reader, Uninstall device, tick the option to remove the driver, restart.
- If Windows installs a generic SD Host Controller driver and the reader is slow or unstable, install the vendor package for the ID instead.
- On laptops, install the chipset package before the reader driver. The reader hangs off a chipset bridge, and without the chipset INF files Windows may not even enumerate it.
USB readers and hubs
USB card readers use the standard mass storage class and need no driver at all. When one does not work, the cause is the port, the cable or the hub, not a missing package. See USB device not recognized. Readers built into monitors and docks sit behind an internal hub, so check that the hub itself is listed under Universal Serial Bus controllers.
Related: Base System Device and Code 10.
More guides
- Find your hardware ID
- Unknown USB Device (Device Descriptor Request Failed)
- Code 43: device reported problems
- Code 10: this device cannot start
- SM Bus Controller driver
- PCI Simple Communications Controller
- PCI Data Acquisition and Signal Processing Controller
- Base System Device driver
- PCI Device driver missing
- Ethernet Controller driver missing
- Network Controller driver missing
- Unknown device in Device Manager
- Code 28: drivers are not installed
- Code 31: Windows cannot load the drivers
- Code 39: driver corrupted or missing
- Code 52: digital signature problem
- USB device not recognized
- Install a driver from an INF file
- Wi-Fi gone after a Windows update
- Bluetooth missing from Windows