Fix: YubiKey Not Detected on Windows 11 (Kleopatra)

If Kleopatra can’t see your YubiKey, it’s usually one Windows service, one daemon, or one hidden PIN prompt.

This guide is built like a checklist: do the fast tests first, then the deeper fixes. Every step has a “prove it’s fixed” check.

What “Not Detected” Usually Means

Kleopatra is the UI. Detection depends on Windows and GnuPG components working together:

• Windows Smart Card service (PC/SC) exposes readers/tokens
• GnuPG smartcard daemon (scdaemon) talks to the token
• USB stability (ports/hubs/power saving)

So “not detected” rarely means the key is broken. It usually means one layer stopped talking.

Symptoms → Exact Fix Mapping (Start Here)

30-Second Quick Test (Fastest Win)

• Unplug YubiKey → plug directly into the PC (skip hubs for this test)
• Try a different USB port (prefer back ports on desktops)
• Close Kleopatra completely and reopen
• Reboot once (not forever; just to clear a stuck stack)

Verification Loop (Prove It’s Fixed)

After every change, run this one command:

gpg --card-status

Step 1: Start / Restart Windows Smart Card Service

This is the #1 cause on Windows 11.

1. Press Win and type Services → open Services
2. Find Smart Card
3. Set Startup type to Automatic
4. Click Start (or Restart if it’s already running)

Now rerun:

gpg --card-status

Step 2: Kill Stuck GnuPG Daemons (Better Than Rebooting)

When Windows sleep/wake or app crashes happen, the smartcard daemon can get stuck.

gpgconf --kill scdaemon
gpgconf --kill gpg-agent
gpg --card-status

Step 3: The Hidden PIN Prompt (The “It’s Frozen” Illusion)

Sometimes the PIN dialog opens behind another window, so you think nothing is happening.

• Press Alt + Tab and look for a PIN prompt
• Minimize all windows (or press Win + D)
• Check the taskbar for a small PIN dialog

Then rerun:

gpg --card-status

Step 4: Conflicts (Another App Is Holding the Token)

Close these completely for testing (not minimized):

• Yubico Authenticator
• Any other GPG tools
• Browser “security key” popups
• Smartcard/token utilities

Step 5: USB + Power Problems (Yes, It’s Real)

• Prefer direct connection to the PC
• Avoid USB hubs/extenders while debugging
• Try a different port (rear ports are often more stable)

Device Manager Check (When Nothing Makes Sense)

Open Device Manager and inspect:

• Smart card readers
• Smart cards
• Universal Serial Bus devices

If you see a warning icon, unplug the key, uninstall the device entry (device only), then replug.

Last Resort (Only After the Verification Loop)

• Reinstall Gpg4win (sometimes a corrupted component breaks scdaemon)
• Try a new Windows user profile (rare profile-level permission/agent weirdness)
• Test on another PC to isolate key vs PC issue

Quick Summary (If You Only Want the Fix)

• 1) Restart Smart Card service
• 2) Run gpg --card-status
• 3) If stuck: gpgconf --kill scdaemon + gpgconf --kill gpg-agent
• 4) Check hidden PIN prompt (Alt+Tab)
• 5) Switch USB port (avoid hubs)

FAQ

Does this affect passkeys / FIDO login too?

This post focuses on OpenPGP smartcard detection for Kleopatra. Your browser passkeys can still work even if OpenPGP is failing.

Is CCID driver required on Windows 11?

Usually no manual install is needed. Windows handles it. If detection is flaky, it’s more often service/USB/conflicts than “missing driver”.

Does YubiKey Manager interfere with Kleopatra?

It can during debugging. Close token-related apps fully when running gpg --card-status.

Why does reboot “fix” it temporarily?

Because reboot resets services and daemons. Use the daemon reset commands so you don’t live in reboot-land.

gpg --card-status works, but Kleopatra still shows nothing

Restart Kleopatra. If still broken, reboot once and then avoid conflicts (other tools grabbing the token).

Related articles