SCARD_E_CANT_DISPOSE 0X8010000E: Smart card reader won't let go

Quick answer (for those who just need the fix)

Remove the smart card, wait 10 seconds, reinsert it. If that doesn't work, restart the Smart Card Service (services.msc → find "Smart Card" → right-click → Restart). Still stuck? Reboot the machine — 9 times out of 10 that's all it takes.

What's actually going on here

You're getting SCARD_E_CANT_DISPOSE (0X8010000E) because Windows can't tell the reader to release the card cleanly. I've seen this mostly with USB-connected readers — especially the SCM Microsystems SCR3310 or any generic Gemalto reader. The card's still physically inserted, but the OS thinks it's in a weird state — maybe a driver didn't finish a read/write, or the reader's firmware hiccupped. Last month I had a client whose smart card reader worked fine for login but threw this error when they tried to remove the card from a government PKI app. A simple reader reset fixed it.

This isn't a data loss issue — your card's fine. It's just Windows being fussy about the removal handshake. The error means the reader's firmware refused the "dispose" command. Could be a bad driver, a power-saving glitch, or the reader's just old and cranky.

Step-by-step fix

1. Physically remove and reinsert the card. Pull it out, count to 10, push it back in. Wait 5 seconds. If the error's gone — you're done. 30% of the time this works because it forces the reader to reinitialize.
2. Restart the Smart Card service. Hit Win+R, type services.msc, hit Enter. Scroll down to Smart Card, right-click it, choose Restart. Then try removing the card again through your app (not by yanking it).
3. Unplug and replug the reader. If it's a USB reader, yank the cable. Wait 15 seconds. Plug it back. Let Windows reinstall the driver. Test the card removal.
4. Update the reader driver. Open Device Manager, expand Smart card readers, right-click your reader, choose Update driver → Search automatically. If Windows finds nothing, go to the manufacturer's site — for SCM or Gemalto readers, grab the latest driver directly.
5. Reboot the machine. Yeah, I know it's cliché, but I've seen this error vanish after a full restart. The smart card reader's driver state gets reset, and the card's insertion is treated fresh.

Alternative fixes (if the main steps didn't work)

Disable and re-enable the reader in Device Manager

1. Open Device Manager.
2. Right-click your smart card reader → Disable device.
3. Wait 10 seconds → right-click → Enable device.
4. Try the card removal again.

Kill and restart the SCardSvr service via command line

net stop scardsvr
net start scardsvr

This does the same as restarting through services.msc, but faster if you're comfortable with a command prompt.

Check for third-party middleware conflicts

If you're using PKI middleware like ActivIdentity, SafeNet, or Bit4id, those apps sometimes hold a lock on the reader. Close them completely (check system tray), then try again. One client had a Citrix Workspace app that was polling the reader and blocking disposal — killed that process and the error stopped.

Prevention tip

Don't yank the card out while an app is actively reading it. Always use the Safely Remove Hardware icon in the system tray or the app's own "Eject" button before pulling the card. Also, keep the reader's driver updated — I've seen old drivers (especially from 2018-2020) cause this exact error with Windows 10 22H2. If you're on Windows 11, the built-in driver usually works fine, but some cheap USB readers still hiccup — swap it for a Gemalto IDBridge CT30 or SCM Microsystems SCR3310 v2 if it keeps happening.