| Previous | Next |
| STATUS_SMARTCARD_CARD_NOT_AUTHENTICATED | STATUS_SMARTCARD_NO_KEY_CONTAINER |
STATUS_SMARTCARD_NO_CARD
Presence is only the first layer
STATUS_SMARTCARD_NO_CARD means the authentication stack did not have a usable smart card available at the point it needed one. This can be as simple as an empty reader, but it can also involve a disconnected reader, a stopped smart-card service, a failed driver/provider, a virtual smart-card issue, session redirection, or an application selecting a different reader than the user expects.
The status does not prove a certificate problem because the card may never have been reached. Start by proving hardware and PC/SC availability, then move through card/provider enumeration, certificate visibility and domain logon requirements. Treating it as a domain password issue sends the investigation in the wrong direction.
Layered checks
- Confirm that the intended physical or virtual card is present and that the reader appears correctly to the operating system.
- Check smart-card service and reader/provider diagnostics before changing certificate or Active Directory settings.
- Verify which reader and certificate provider the sign-in UI selected, especially on systems with multiple readers or remote sessions.
- Once the card is visible, validate certificate eligibility and the Kerberos/PKINIT path separately.
References
- Microsoft Open Specifications: NTSTATUS reference
- Microsoft: smart-card troubleshooting
- Microsoft: smart-card certificate requirements
- RFC 4556: PKINIT
Looking for a different code? Search another status or error code.