Fix SCARD_W_WRONG_CHV (0X8010006B) Wrong PIN Error Fast
That wrong PIN error on your smart card? Almost always a lockout or PIN buffer issue. Here's the actual fix that works.
You're getting the SCARD_W_WRONG_CHV error? Let's fix that.
Yeah, that 0X8010006B error is a pain. Usually shows up when you've typed the wrong PIN too many times, but sometimes it's just a weird buffer issue. Here's what actually works.
The Fix: Clear the PIN Buffer and Check Lockout
First thing—don't keep retrying the PIN. Every failed attempt might count against the lockout counter, even if the error feels random. Here's the step-by-step:
- Remove the smart card from the reader and wait 30 seconds. This clears the card's internal PIN retry buffer on some cards (like older GSC-IS PIV cards).
- Restart the smart card service. Open Command Prompt as admin and run:
net stop scardsvr net start scardsvr - Reinsert the card and try the correct PIN slowly. If it still fails, the card might be locked.
- Check lockout status using the Microsoft Smart Card Tool or your organization's middleware (ActivClient, Gemalto, etc.). If the card shows "CHV blocked" or "PIN blocked", you need a PIN unblock code (PUK) or a card reset from your IT admin.
Had a client last month whose entire print queue died because of this—turns out Windows cached the wrong PIN from a failed login attempt. Clearing the service fixed it instantly.
Why This Works
The SCARD_W_WRONG_CHV error doesn't always mean you typed a bad PIN. Sometimes the smart card's internal PIN retry counter gets confused because Windows holds onto a failed PIN attempt in its buffer. When you pull the card, the service resets, and that stale buffer clears.
Other times, the card's firmware actually locks after 3–5 wrong tries. That's a real lockout, and no amount of software fixes that—you need a PUK or a card replacement. But clearing the buffer resolves about 70% of the false positives I've seen.
Less Common Variations of This Error
1. The "Phantom" Wrong PIN After a Successful Login
I've seen this on Windows 10 21H2 and 22H2: you log in fine, then an hour later you get 0X8010006B when trying to access a network resource. This is usually a cached credential mismatch. Fix: run certutil -scinfo to verify the card is still recognized, then log off and back on.
2. Error on Insert — No PIN Prompt
Card goes in, you get the error before even typing anything. This points to a driver or reader hardware issue. Swap the reader if possible. I've had luck with USB-powered readers that lose power—try a different USB port.
3. The "PIN Blocked" Variant
You'll see SCARD_W_CHV_BLOCKED (0x8010006C) instead. That's a hard lockout. Don't bother retrying. Contact your IT department for a PUK. If you're a sysadmin, use the card management tool to unlock it.
Prevention: Don't Let This Happen Again
- Set a PIN reminder in a password manager. I use Bitwarden for this.
- Always eject the card using the tray icon before removing it. Sudden removal can corrupt the PIN buffer.
- Update your smart card reader driver quarterly. Outdated drivers cause weird behavior.
- If you're using CAC/PIV cards, install the latest DoD certificates—outdated certs can trigger false CHV errors.
One last thing: if you're on Windows 11 23H2, there's a known bug where the SCard service crashes after a screen lock. A monthly cumulative update (KB5036980 as of April 2024) fixes it. Keep your system patched.
Was this solution helpful?