Fix SCARD_W_UNSUPPORTED_CARD (0X80100065) Smart Card Error
Your reader sees the card but won't talk to it. The culprit is almost always a mismatched ATR configuration in the registry. Here's the exact fix.
Yeah, I know the drill. You pop in a smart card, the reader blinks, you expect it to work, and instead you get 0X80100065 — "unsupported card." The reader sees the card but refuses to talk to it. Frustrating as hell. Let's cut through the noise.
The Quick Fix: Delete the Broken ATR Entry
The reader and card agree on the physical connection, but a bad ATR (Answer To Reset) configuration in Windows is blocking communication. The fix is dead simple.
- Open Regedit as Administrator.
- Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\Readers - Under
Readers, you'll see a subkey named after your reader (e.g., "OMNIKEY CardMan 3121"). Expand it. - Look for a REG_BINARY value named ATR. If it exists, delete it. Right-click → Delete.
- Close Regedit, restart the smart card service or reboot.
That's it. Nine times out of ten, this resolves the error instantly.
Why This Works
Windows maintains a cache of ATR strings for cards it's seen before. When a card is inserted, the reader sends its ATR — a string of bytes identifying the card type and protocol. Windows checks its cache. If the cached ATR is corrupt, partial, or matches a different card profile, it throws 0X80100065 instead of negotiating a protocol.
Deleting the cached ATR forces Windows to re-read the card fresh. No more stale or corrupted data blocking the handshake.
Less Common Variations & Edge Cases
1. Multiple ATR Entries
Sometimes the registry holds multiple ATR entries for the same reader — one per card type. If you delete the wrong one, the error might persist. Check the data column in Regedit: each ATR value looks like a long hex string (e.g., 3B 9F 96 80 1F C7 80 31 A0 73 BE 21 13 67). If you see more than one, delete them all. Windows will rebuild them as cards are inserted.
2. Third-Party Smart Card Software Interference
Software like ActivClient, SafeNet, or Oberthur can override the Windows ATR cache. If deleting the registry key didn't help, check if you have one of these installed. Uninstall, reboot, test with the card. If it works, reinstall the software fresh — it may have corrupted its own ATR database.
3. Card-Specific Protocol Mismatch
Some older cards (e.g., Gemalto .NET v1.0) only speak T=0 protocol. Newer readers default to T=1. The registry sometimes locks the protocol. To check: in the same registry path, look for a DWORD value Protocols under your reader key. If it's set to 1 (T=1 only), change it to 3 (both T=0 and T=1). Reboot.
4. Physical or Driver Issues (Rare)
Don't bother replacing the reader unless the error persists across multiple cards and multiple PCs. But do check the card's gold contacts for dirt. A dirty card can give a garbled ATR that Windows interprets as unsupported. Clean with a soft, dry cloth.
Prevention: Keep the ATR Cache Clean
You can prevent this from recurring with a simple scheduled task. Create a script that clears the ATR registry key on system startup:
reg delete "HKLM\SOFTWARE\Microsoft\Cryptography\Calais\Readers" /v ATR /fSave it as ClearSmartCardATR.bat. Drop it into shell:startup. No more manual registry edits when a new card shows up.
One last thing: If you're using a virtual smart card (like Windows Hello for Business), this error can also pop up when the TPM is misconfigured. That's a different beast — check the TPM status in tpm.msc and make sure it's initialized.Was this solution helpful?