YubiKey Not Recognized on Windows 11 — Complete Fix Guide

Symptom fingerprint

The exact strings, error codes, and UI surfaces that map to this issue:

What you'll learn in this guide

If your YubiKey is not recognized on Windows 11 — no signing certificate appears, the smart card prompt says "no card detected," or Device Manager shows an unknown USB device — the break is almost always in one of three layers: the USB/driver layer, the Windows Smart Card service, or the PIV certificate selection inside your signing application. None of these require replacing the key.

In this guide you'll learn why Windows 11 stops detecting a YubiKey, how to fix it step by step (USB and driver checks, the Smart Card service, minidriver and PIV enumeration, and certificate selection), an advanced fix for power users, and answers to the questions IT admins search for most. The steps work for YubiKey 5 Series and 5 FIPS keys used for PIV smart card signing and login.

Why Is My YubiKey Not Working on Windows 11?

A YubiKey not recognized on Windows 11 is rarely a dead key. Match your symptom to one of these root causes before changing anything:

• USB or port fault — a flaky cable, unpowered hub, or a USB port in selective-suspend power saving drops the CCID interface intermittently.
• Smart Card service stopped — the 'Smart Card' (SCardSvr) or 'Certificate Propagation' (CertPropSvc) service is set to Manual and isn't running, so Windows never enumerates the PIV applet.
• Missing or mismatched minidriver — Windows 11 usually loads a generic PIV minidriver, but a stale or conflicting YubiKey Smart Card Minidriver install can block enumeration.
• No certificate in the PIV slot — the key is detected but slot 9c (Digital Signature) or 9a (Authentication) has no certificate, so the signing app shows nothing to select.
• Conflicting middleware — vendor middleware (OpenSC, SafeNet, or an old YubiKey manager) claims the CCID device and hides it from Windows CAPI.
• Feature-update regression — a Windows 11 23H2/24H2 update reset smart card services to Manual or reinstalled the USB host driver, breaking a previously working setup.

Windows vs macOS — what differs

Browser-specific behaviour

• Chrome

  Uses Windows CAPI for client certificates; if the YubiKey was inserted after launch, fully restart Chrome (chrome://restart) so it re-enumerates the PIV certificate.

• Edge

  Reads the same CAPI store as Chrome; disable IE Mode for the signing site, which can suppress smart card enumeration.

• Firefox

  Maintains its own NSS store — load the PKCS#11 module manually via Settings → Privacy & Security → Security Devices → Load if the key isn't offered.

Diagnostic sequence

Run each step in order. Stop at the first failing expectation — that's where the root cause lives.

1. 1. Confirm the hardware layer (rule out USB)

   Reinsert directly into a rear motherboard USB-A port — no hub. The YubiKey LED should be lit/steady.

   Expected: Key powers on; Device Manager no longer shows 'Unknown USB Device'. ⚠️ If still unknown, swap cable/port before continuing — this is a USB fault, skip to Step 5.

2. 2. Start the Smart Card services

   Get-Service SCardSvr,CertPropSvc | Format-Table Name,Status,StartType
   # then, if not running/automatic:
   Set-Service SCardSvr -StartupType Automatic; Start-Service SCardSvr
   Set-Service CertPropSvc -StartupType Automatic; Start-Service CertPropSvc

   Expected: Both services Running and Automatic. Reinsert the YubiKey afterward.

3. 3. Confirm Windows enumerates the card and its certificates

   certutil -scinfo

   Expected: Reader name, YubiKey serial, and at least one X.509 certificate listed. ⚠️ Reader shown but no certificate = empty PIV slot, skip to Step 4.

4. 4. Verify the PIV certificate slot

   Open YubiKey Manager (or 'ykman piv info') and check slot 9c (Digital Signature) / 9a (Authentication).

   Expected: Slot 9a/9c shows a valid certificate with your name and a future expiry. If empty, import or re-enroll the certificate into the slot.

5. 5. Resolve driver / middleware conflicts

   Device Manager → Smart cards → uninstall any 'YubiKey Smart Card Minidriver' AND remove OpenSC/old middleware → reboot to let Windows load its native PIV minidriver.

   Expected: After reboot, 'Microsoft Usbccid Smartcard Reader' appears with no yellow bang and certutil -scinfo lists the certificate.

6. 6. Confirm app-layer visibility

   Acrobat → Sign with Certificate, or your login/VPN prompt.

   Expected: The PIV certificate appears in the chooser and signing/authentication succeeds.

Frequently asked questions