cisco secure client no valid certificates available fix

TL;DR

"No valid certificates available" means the client cannot find a usable machine or user certificate for authentication. Open certlm.msc and check the Personal store for an expired or missing computer certificate; if it is expired, renew it through your SCEP or NDES flow or re-enroll the device. If the cert exists and is valid, the Secure Client profile is probably pointing at the wrong certificate store or filter.

The error

No valid certificates available for authentication

Steps

1. On the machine, open certlm.msc (computer certificates) and look under Personal > Certificates. Expected: a computer certificate issued by your CA, not expired. If it is missing or expired, that is the whole problem.
2. If expired or missing: renew through your normal flow (SCEP or NDES auto-enrollment, or re-run device enrollment). Expected: a fresh certificate appears in the Personal store with a future expiry.
3. Check certmgr.msc (user certificates) too if your VPN uses user certs instead of machine certs. Expected: clarity on which store the VPN is supposed to use. Mixing these up is common.
4. In the Secure Client (AnyConnect) profile XML on the client, verify the certificate match criteria point at the right store and issuer. Expected: the profile's certificate settings match the actual certificate. A profile copied from another org often filters for the wrong CA.
5. Restart the Cisco Secure Client service (vpnagent) after fixing the certificate. Expected: the client now lists a certificate and connects. The agent caches the "no valid certificates" state.
6. If the cert is valid and the profile is right: repair the Secure Client install or update to the supported version. Expected: the client enumerates certificates correctly.

Use this when

• Cisco Secure Client shows "no valid certificates available"
• Certificate-based VPN auth suddenly breaks across many machines (likely mass expiry)
• A reimaged machine cannot use VPN until its certificate is reissued

Not for this skill when

• VPN uses username and password or SAML (no certificates involved)
• Duo or other MFA push is failing after the certificate step succeeds
• The certificate is for Wi-Fi 802.1X, not VPN (different profile, same store)

Compatibility

• Cisco Secure Client (AnyConnect) 5.x on Windows 10/11 and macOS; machine or user certificate authentication

Variants

Works for some users but not others

Compare a working and a broken machine's Personal store; the broken ones usually have an expired cert from a failed auto-renewal. Check the SCEP server logs for renewal failures.

Certificate exists but the client still says none available

The certificate may lack the client-authentication EKU, or the private key is missing (cert imported without the key). Re-enroll with the key handled properly.

Why it happens

Certificate VPN auth needs three things to line up: a non-expired certificate, in the right store, with a private key, matching the profile's selection criteria. Any one missing produces the same message, which is why the fix is a checklist through the stores and the profile rather than a single setting.

Edge cases

• Machine certs issued with short lifetimes (90 days) expire silently; monitor expiry centrally instead of waiting for VPN tickets.
• Clock skew on the machine can make a valid cert look expired; check the clock if the cert looks fine.
• Smart card certs need the card inserted AND the middleware running; "no valid certificates" with the card out is expected behavior.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_SPZiLmUw5P0L01g3aX2O4Q