Smartcard reader drivers

In many cases, yes. However, the Microsoft CCID driver is designed to provide broad compatibility across many different readers. Where an OEM driver is available, it is the recommended option for achieving the best reliability and user experience.

This guidance is intended for local IT teams updating manufacturer-provided smartcard reader drivers, also known as OEM drivers. Administrator permissions may be required.

Before updating a reader, finish any smartcard operations and disconnect any smartcard printers. This helps prevent changes to the printer’s built-in reader, which may require a different driver. Keep the reader you intend to update connected.

1. Identify the reader and its current driver

1. Right-click Start and select Device Manager.
2. Expand Smart card readers.
3. Identify the reader you want to update. Check the manufacturer and model printed on the device. For an external reader, disconnecting and reconnecting it can help identify the corresponding entry.
4. Right-click the reader and select Properties.
5. Select the Driver tab and record the Driver Provider, Driver Date and Driver Version.

A generic name such as Microsoft Usbccid Smartcard Reader (WUDF) may indicate that the reader is using the Windows class driver. Use the reader model and hardware ID to identify the appropriate manufacturer package.

2. Check Windows Update

Manufacturer drivers can be distributed through Windows Update.

On Windows 11:

1. Open Settings → Windows Update.
2. Select Check for updates and allow the check to complete.
3. Open Advanced options → Optional updates.
4. Expand Driver updates, if available.
5. Select the applicable smartcard reader driver and choose Download and install.
6. Restart the computer if prompted.

Optional driver updates require selection unless your organisation manages their deployment. If no suitable update appears, continue with the Microsoft Update Catalog instructions below. The absence of an update does not establish that no manufacturer driver exists.

If Windows Update options are unavailable or managed by your organisation, contact the team responsible for device updates.

3. Find the reader’s VID and PID

1. Return to the reader’s Properties in Device Manager.
2. Select the Details tab.
3. From the Property list, select Hardware Ids.
4. Right-click an entry and select Copy.

Windows may list several hardware IDs, ordered from more specific to less specific. Do not assume that the second entry is always the correct one. For example:

USB\VID_17EF&PID_62A6&MI_01

Keep the MI_ value where present. A keyboard can expose separate keyboard and smartcard-reader interfaces, so selecting the correct interface matters.

4. Find a driver in the Microsoft Update Catalog

1. Open the Microsoft Update Catalog.
2. Paste the copied hardware ID into the search box and select Search.
3. If no results appear, try a less-specific ID from the device’s Hardware Ids list, such as one without the REV_ revision component. Retain the VID, PID and interface identifier where applicable.
4. Open a result’s title and review its details before downloading.

The Catalog supports searches using hardware IDs, manufacturers and device models.

Check that the package matches:

• the reader’s hardware ID, including its interface where applicable
• the manufacturer and reader model
• the supported Windows version
• the computer’s architecture, such as x64 or ARM64
• any version requirements in your organisation’s smartcard guidance.

You can check the computer’s architecture under Settings → System → About → System type.

Do not select a package solely because it has the newest date. Once you have identified a suitable package, select Download, then select the download link in the window that opens. If no suitable package is available, use the reader or computer manufacturer’s official support website.

5. Extract and install the downloaded driver

Microsoft Update Catalog driver downloads are commonly supplied as .cab files. Extract the package before installing it.

For example, create a destination folder and run these commands in Command Prompt, replacing the CAB filename with your download:

mkdir C:\DriverUpdates\Reader-expand.exe -F:* "C:\Downloads\reader-driver.cab" "C:\DriverUpdates\Reader"

Keep the extracted INF, catalogue and driver files together.

Then:

1. Open Device Manager and find the intended smartcard reader.
2. Right-click it and select Update driver.
3. Select Browse my computer for drivers.
4. Browse to the extracted folder and select Include subfolders.
5. Select Next and follow the instructions.
6. Restart if prompted.

If the manufacturer supplies an installer instead, follow its installation instructions.

6. Confirm the update

Return to the reader’s Properties → Driver tab and check the installed provider, version and date against the intended package. Check the General tab for any device error.

The reader’s displayed name may change, but a name change alone does not confirm that the intended driver is installed. Test smartcard authentication and any relevant card management operations.

If Windows reports that the best driver is already installed, it may prefer the existing driver under its matching and ranking rules. Do not force an incompatible package. Ask your local IT support team to check the hardware ID, package compatibility and installed driver details before proceeding.

Note: we include manufacturer driver packages to make suitable drivers available for the smartcard readers used across organisations. These packages are staged in the Windows Driver Store, ready for use when matching devices are connected. For devices already connected, Windows is also instructed to install or update the driver where appropriate, subject to its normal driver matching and ranking rules.

Windows controls driver selection through its Plug and Play process. It considers how closely a driver matches the device's hardware identifiers, together with signature and other ranking criteria. Driver date and version distinguish otherwise equally ranked candidates; the newest version is not automatically preferred over a better-ranked match.

The deployment does not force a supplied driver to replace a higher-ranked driver. Where Windows prefers an existing driver, the additional package remains staged and available for future device installation. Devices without matching hardware identifiers are not targeted by these packages.

We use the `/install` option because staging alone does not request an update to drivers already associated with connected readers. During testing, staging-only deployment required a subsequent manual installation step. This approach reduces manual intervention while retaining Windows control over which driver is selected.