| Previous | Next |
| STATUS_PCP_PROFILE_NOT_FOUND | STATUS_PCP_DEVICE_NOT_FOUND |
STATUS_PCP_VALIDATION_FAILED
The provider could not validate the supplied or derived security data
STATUS_PCP_VALIDATION_FAILED is a validation result from the Platform Crypto Provider. It does not name a single root cause; it says that the data or security evidence presented to the provider did not pass the validation needed for this operation.
For attestation and policy workflows, the validation inputs can include key properties, evidence, challenge material, or platform measurements. Replacing the TPM or issuing a new certificate before preserving the rejected input can turn a diagnosable validation mismatch into an unreproducible incident.
What to check
- Collect the operation type, provider properties, key name or handle, input sizes, and the complete status chain.
- For attestation, keep the challenge, evidence metadata, and CA-side rejection detail together; do not treat a certificate-enrollment failure as proof that the TPM hardware is defective.
- Check whether a prior boot, policy update, or firmware change altered the expected validation context.
References
- Microsoft: PCP and TPM error codes
- Microsoft: TPM key attestation
- Trusted Computing Group: TPM 2.0 Library Specification
Looking for a different code? Search another status or error code.