SCARD_F_COMM_ERROR (0X80100013) Smart Card Fix

Quick answer for advanced users

Disconnect the reader, pull the card, clean the contacts with a dry cloth, reconnect. Then run certutil -scinfo to verify handshake. If that fails, uninstall the reader driver from Device Manager and reboot.

What this error actually means

SCARD_F_COMM_ERROR (0X80100013) shows up when the smart card reader and the card stop talking to each other mid-operation. I see this most often on Windows 10 and 11 machines with USB-connected readers like the HID OMNIKEY or Cherry TC series. It's not a broken card — it's a broken handshake. The reader sends a command, the card doesn't answer in time, and Windows throws this code.

This happens a lot after the computer wakes from sleep. The reader loses power briefly, the card resets, but the driver doesn't reinitialize properly. Or you'll get it when the card is slightly askew in the slot — common with worn-out readers in high-use environments like hospitals or government offices.

Step-by-step fix

1. Reseat the card. Pull the smart card out completely. Wait 5 seconds. Slide it back in until it clicks. Then open a Command Prompt as Administrator and type certutil -scinfo. You should see card details like the ATR string appear within 2 seconds. If you get the same error, move on.
2. Restart the Smart Card service. Press Win + R, type services.msc, and hit Enter. Find Smart Card in the list. Right-click it and choose Restart. After that, right-click again, pick Properties, and set Startup type to Automatic if it isn't already. Click Apply, then OK. Run certutil -scinfo again to test.
3. Update the reader driver. Open Device Manager (Win + X -> Device Manager). Expand Smart card readers. Right-click your reader (e.g., "HID OMNIKEY 3x21") and choose Update driver -> Browse my computer -> Let me pick from a list. If there's a newer driver shown, pick it. If not, stick with the current one — sometimes the generic Microsoft driver works more reliably than the vendor's.
4. Uninstall and reinstall the reader. Back in Device Manager, right-click the reader and choose Uninstall device. Check the box that says Attempt to remove the driver for this device if it appears. Unplug the reader, wait 10 seconds, plug it back in. Windows will redetect and reinstall the driver. Test again with certutil -scinfo.
5. Clean the card contacts. Get a soft, lint-free cloth. Lightly dampen it with isopropyl alcohol (70% or higher). Gently wipe the gold chip on the card front to back — don't scrub hard. Dry it with the other side of the cloth. Reseat and test.

If the main fix doesn't work

Try a different USB port — preferably a port directly on the motherboard, not a hub or front-panel port. I've seen power delivery issues cause this error on USB 3.0 ports with older readers. Stick to USB 2.0 ports if you have them.

Another thing: disable USB selective suspend. Go to Control Panel -> Power Options -> Change plan settings -> Change advanced power settings. Find USB settings -> USB selective suspend setting and set it to Disabled. This keeps the reader powered when the computer sleeps.

If you're using a virtual smart card (like for Windows Hello for Business), this error can also come from a corrupted PIN or certificate. Run certlm.msc and check under Personal -> Certificates. If the card's certificate shows a red X, it's expired or revoked — you'll need IT to issue a new one.

Prevention tip

Don't leave the card in the reader when you shut down or sleep the PC. That's the #1 cause I see. Pull the card, store it in a sleeve or holder, and only insert it when you need it. Also, keep your reader firmware updated — check the manufacturer's site every six months. For HID readers, their OMNIKEY Workbench tool is worth having installed.

Pro tip: If you manage multiple machines with smart card readers, create a scheduled task that restarts the Smart Card service daily at 3 AM. That alone cut our error tickets by about 70%.