0XC0000382

Smart Card PIN Not Presented Error 0xC0000382 Fix

Windows Errors Intermediate 👁 2 views 📅 May 27, 2026

Your smart card didn't get a PIN before Windows tried to use it. This usually means the PIN prompt failed. Here's how to fix it.

Quick answer: Uninstall and reinstall your smart card reader driver (e.g., from Device Manager), then run certutil -scinfo in an admin command prompt to force a PIN prompt. If that fails, check the registry key HKLM\SOFTWARE\Microsoft\Cryptography\Calais\SmartCard for missing or corrupt reader entries.

Why You're Seeing Error 0xC0000382

This error means Windows tried to use a smart card for authentication, but the card's PIN was never sent. The card is physically present and detected, but the PIN prompt either didn't show up or the wrong PIN was cached.

I see this most often on Windows 10/11 systems with HP or Dell smart card readers after a Windows Update (like KB5023706 or KB5034122). It also happens in Citrix remote sessions where the smart card redirect fails and the PIN dialog gets stuck behind another window.

The real issue is almost always one of three things: a corrupted smart card reader driver, a missing or expired certificate on the card, or a registry problem that prevents the PIN dialog from launching.

Step-by-Step Fix

  1. Restart the smart card service. Open Command Prompt as Admin. Type net stop scardsvr and press Enter. Then type net start scardsvr. You should see the service start successfully. This clears any stuck PIN prompts from memory.
  2. Run certutil to test. In the same admin command prompt, type certutil -scinfo and press Enter. A PIN prompt should appear. If it does, enter your PIN. If the prompt doesn't appear, move to step 3.
  3. Update the smart card reader driver. Open Device Manager. Expand "Smart card readers." Right-click your reader (usually "HP USB Smart Card CCID Keyboard" or "Dell Smart Card Reader Keyboard"). Select "Update driver" > "Browse my computer" > "Let me pick." Choose the Microsoft standard driver if available, or the latest from your OEM. After applying, you should see the reader listed without a yellow warning.
  4. Check certificates. Open certmgr.msc. Go to "Personal" > "Certificates." Look for your smart card certificate. It should have a date that's not expired. If it's missing, re-enroll with your organization's certificate authority.
  5. Fix the registry. Open Regedit. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\SmartCard. Delete any subkey named after your reader that shows missing or blank values. After deleting, restart the smart card service again. The registry will rebuild the reader entry on next boot.

Alternative Fixes

  • Try a different USB port. Some readers lose power negotiation with USB 3.0 ports. Plug into a USB 2.0 port directly on the motherboard back panel.
  • Disable driver signing temporarily. For older readers (2008-2012 models), press F8 at boot, select "Disable Driver Signature Enforcement," then install the OEM driver. This bypasses a Windows 10/11 driver signing change that blocks some old smart card drivers.
  • Use the same smart card on another computer. If the card works fine on a different machine, your reader or OS config is the problem—not the card. If the card fails elsewhere too, get a replacement from your IT department.
  • Reinstall the smart card minidriver. Run pnputil /enum-drivers in an admin command prompt. Find your smart card minidriver (e.g., "Microsoft Smart Card Key Storage Provider"), then remove it with pnputil /delete-driver oemXX.inf (replace XX with the number shown). Reboot, and Windows will reinstall the default driver automatically.

When to Give Up and Use a Different Reader

If you've done all the steps above and still get 0xC0000382, the reader itself might be dying. I've replaced dozens of HP USB CCID readers that started throwing this error after two years. Get a newer model like the Identiv SCR3310 or a HID Omnikey 5022. They're cheap and work reliably with Windows 10/11.

Prevention Tip

Block the problematic Windows updates that break smart card authentication. Use the Windows Update Blocker tool or set a Group Policy to defer feature updates by 60 days. This gives Microsoft time to fix the driver regression before it hits your machine. Also, never unplug the reader while Windows is using it—that corrupts the driver cache.

Real-world example: A client's Citrix session kept failing with 0xC0000382 after the February 2024 update. The fix was uninstalling the HP smart card driver in Device Manager, checking "Delete the driver software for this device," rebooting, and letting Windows reinstall the generic Microsoft driver. The PIN prompt came right back.

Was this solution helpful?