| Previous | Next |
| STATUS_PCP_ERROR_MASK | STATUS_PCP_INVALID_HANDLE |
STATUS_PCP_DEVICE_NOT_READY
Provisioning has not reached an operational state
STATUS_PCP_DEVICE_NOT_READY comes from the Platform Crypto Provider (PCP), the CNG key-storage provider that uses the TPM for hardware-backed keys. It means that Windows reached the provider but the TPM-backed platform state is not ready for the requested operation. This is different from a missing provider or an unknown key name.
Treat this as a platform-readiness problem, not as a reason to recreate a key blindly. TPM initialization, firmware state, ownership/provisioning and a recently changed platform configuration can all affect whether PCP can service a request. Recreating a credential before identifying the state can discard the only reference to a deployed key or certificate.
What to check
- Record the calling CNG operation, the provider name, the Windows security log context, and the complete
SECURITY_STATUSrather than only its translated application error. - Check TPM availability and readiness through the supported Windows management interfaces before attempting key enrollment, attestation, or recovery.
- If firmware or provisioning changed, verify the documented recovery path for the affected product; clearing a TPM can make TPM-protected material unavailable.
References
Looking for a different code? Search another status or error code.