SCARD_E_WRITE_TOO_MANY (0X80100028) – Smart Card Memory Full

1. The Card's Storage Is Actually Full – Clear Old Certificates

This is the #1 cause. Smart cards have tiny storage — typically 32KB to 128KB. Every certificate, private key, and PIN attempt counter takes up space. Once it hits the limit, you get 0X80100028.

I see this most often with government PIV cards or corporate smart cards used for VPN access. Users install one too many intermediate CA certs or let the PIN counter max out (usually 3–10 retries).

What to do:

1. Plug the card into a reader.
2. Open certmgr.msc (not the user store — run as admin).
3. Expand Smart Card Trusted Roots and Intermediate Certification Authorities.
4. Look for any expired or duplicate certificates. Delete them.
5. If you're using a government-issued card, check for multiple copies of the same CA cert. Delete extras.

After cleanup, re-insert the card and try your operation again. If the error persists, move to fix #2.

2. PIN Retry Counter Is Maxed – Unblock the PIN

Smart cards track failed PIN attempts in a small reserved area. Enter the wrong PIN 3 times, and that counter hits its limit. Some cards treat this as "storage full" and throw 0X80100028 instead of the usual blocked-PIN error.

How to fix:

1. Use the card vendor's management tool (e.g., ActivClient, Gemalto Classic Client, or your org's middleware).
2. Look for Unblock PIN or Reset PIN Counter.
3. You'll need the PUK (Personal Unblocking Key) — that's different from your PIN. If you don't have it, call your helpdesk.
4. Once unblocked, the counter resets to zero, freeing up that storage block.

Don't bother with generic Windows PIN reset tools — they rarely work on enterprise cards. Stick with the vendor's own software.

3. The Card Is Physically Full – Replace It

Some cards have a hard write limit. Once you've written data to every available sector, no amount of deleting will help. This is common on older cards (pre-2015) or cheap contactless cards with 8KB storage.

Check your card's specs:

• Look at the card's model number. If it's a JavaCard with less than 32KB, you're out of luck.
• If you've been using the same card for 3+ years, it's probably worn out.
• Some cards lock after a certain number of writes (e.g., 100,000). Yes, that's a real thing.

Fix: Get a new card from your IT department. There's no software workaround for physically full flash memory.

Quick Reference Table

If none of these work, the card's hardware has failed. You can't fix that. Get a replacement and move on.