Fix Smart Card Error 0x80100031: Server Too Busy

What's going on here?

You're trying to use a smart card — maybe for a VPN, a badge reader, or signing a document — and Windows hits you with 0x80100031. The message says the smart card resource manager is too busy. That usually means the SCardSvr service (the Smart Card Resource Manager) is hung, overloaded, or locked by a process that crashed without letting go.

I've seen this most often after a remote desktop session where the smart card was redirected, or after a third-party smart card middleware (like from Gemalto or ActivIdentity) left a dangling request. The fix is straightforward. You'll probably resolve it in under a minute.

Fix 1: Restart the Smart Card Service

This is the 30-second fix and works about 80% of the time.

Press Windows + R, type services.msc, and hit Enter.
Scroll down to Smart Card Resource Manager. It's listed as SCardSvr in the Service column.
Right-click it and choose Restart.

What you should see: The service status will briefly show "Stopping..." then "Starting..." then "Running." If it stops and stays stopped, or throws an error when you try to restart it, that's a different problem — usually a corrupted driver or a bad service dependency.

After the restart, try your smart card operation again. If it works, you're done. If not, move to Fix 2.

Fix 2: Kill Stuck Processes from Task Manager

Sometimes the service itself is running fine, but a child process or a third-party smart card helper app has locked the resource. This fix takes about 2 minutes.

Press Ctrl + Shift + Esc to open Task Manager. Or right-click the taskbar and pick Task Manager.
Click More details if you're in compact view.
Go to the Processes tab.
Look for anything named SCardSvr, scardsvr.exe, or any process from your smart card vendor (like acsCCID.exe, scmd.exe, or pksc11.dll hosts).
Right-click each one and choose End task.
Now restart the Smart Card Resource Manager service again (Fix 1).

What you should see: After killing the rogue process, the service restart should go smoothly. If you can't end a process because it says "Access Denied," you'll need to use the command line — see Fix 3.

Fix 3: Clear the Lock File Manually (Advanced)

This is the nuclear option. It takes about 15 minutes but works when nothing else does. The smart card resource manager stores a lock file in shared memory. A crash can leave a "phantom lock" that prevents new connections. I've seen this on Windows Server 2019 and Windows 10 22H2 specifically.

Open Command Prompt as Administrator. Right-click the Start button, select Command Prompt (Admin) or Windows PowerShell (Admin).
Stop the service: net stop scardsvr

Now delete the lock file. Run these three commands one at a time:

del /f /s /q %SystemRoot%\System32\SCardSvr.db
    del /f /s /q %SystemRoot%\System32\SCardSvr.bin
    del /f /s /q %SystemRoot%\System32\SCardSvr.lck

If any file says it's in use, reboot into Safe Mode (press F8 at startup, choose Safe Mode with Networking), then repeat steps 1-3.
Start the service: net start scardsvr

What you should see: The del commands should return without error. If you see "The process cannot access the file because it is being used by another process," you missed a running process — kill it or go to Safe Mode. After restarting the service, try your smart card operation again.

If none of these work

You might have a hardware issue. Try these:

Remove and reinsert the smart card reader from the USB port. Wait 10 seconds, plug it back in.
Install the latest driver from your smart card reader manufacturer — not the one Windows Update offers. Go to the vendor's site directly.
Check if the card itself is damaged. Test it on another computer. If it fails there too, the card is the problem.

One last thing: I've seen this error pop up when the smart card is trying to work through Remote Desktop. If you're in an RDP session, try running the smart card app locally on the machine where the reader is physically plugged in. That's not always possible, but it isolates the issue.