Fix SCARD_E_UNSUPPORTED_FEATURE 0X80100022 (Smart Card)

Smart card readers throw this when the card or driver lacks a feature. We'll show you how to update drivers, adjust registry settings, and test the card.

Quick answer for the impatient

Update the smart card reader driver, then check if the card itself supports the operation you're requesting. If that fails, clear the cached card handle via scardsvr restart or registry tweak.

This error — 0X80100022 — is Windows' way of saying "I asked the smart card to do something, and it either doesn't have that capability or the driver didn't expose it." It's not a hardware failure. Most of the time, you're hitting an API call like SCardGetAttrib or SCardControl that the card's applet doesn't implement. I've seen it plague corporate badge readers, especially old Gemalto or OMNIKEY units, when the IT department deploys a new authentication app that expects a newer card feature set.

Before you rip out the reader and throw it in the bin, run through these steps. They'll solve it in 9 out of 10 cases.

Update the reader driver. The culprit is almost always a stale driver. Go to Device Manager, expand "Smart card readers," right-click your reader, and choose "Update driver." Let Windows search. If nothing, hit the manufacturer's site and grab their latest — don't bother with generic Microsoft drivers unless you're desperate.
Try a different card. If you have another smart card lying around (a spare employee badge works), plug it in and run the same operation. If it works, your card is the problem — it's old or its applet doesn't support the feature. That's a card provisioning issue, not a Windows one.
Restart the Smart Card service. Sometimes the service gets wedged. Open an admin command prompt and run:
```
net stop scardsvr
net start scardsvr
```
Then try again.
Clear the cached reader state. Windows caches card attributes per session. Reboot your machine. Still failing? Plug the reader into a different USB port — this forces a fresh enumeration.
Check the registry for feature flags. This is a long shot, but I've seen it work. Open regedit and go to:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\Readers
```
Find your reader's key. Look for a DWORD named dwFeatures. If it's set to a weird value, back it up and delete it. Let Windows recreate it on next service start.

If the main steps don't fix it

Try these alternatives. They're more invasive, so save them for when you're stuck.

Use a different API call

If you're a developer, stop using SCardGetAttrib for every attribute. Some readers only support a subset. Use SCardGetStatusChange or SCardTransmit for basic operations. Check your calling code — maybe you're requesting something like SCARD_ATTR_ICC_PRESENCE that the reader doesn't expose.

Replace the driver with a vendor-specific one

Windows' inbox drivers are minimal. For an OMNIKEY 3121, you need the HID Global driver. For a Gemalto PC Twin, you need the Gemalto one. Don't rely on Microsoft Update. Download from the vendor, uninstall the old driver fully (check "Delete the driver software for this device" in Device Manager), then install fresh.

Bypass the reader entirely

If this is for a VPN cert or a login, consider using a USB token instead. It's not the same, but it sidesteps the unsupported feature. I've recommended this to plenty of managers who just need to get people working.

Prevention — stop this from recurring

Keep your reader drivers current. Schedule a monthly check — put it on your calendar. Also, when you roll out new smart card apps, test them against every reader model you have in stock. That sounds like common sense, but I've seen orgs buy 500 new readers and then wonder why the old cards fail.

And for the love of all that is sysadmin, don't buy no-name readers from Amazon. Stick with HID, Identiv, or Gemalto. They have decent driver support and you won't be chasing this error at 3 a.m.