| Previous | Next |
| STATUS_PCP_ATTESTATION_CHALLENGE_NOT_SET | STATUS_PCP_KEY_ALREADY_FINALIZED |
STATUS_PCP_NOT_PCR_BOUND
The operation requires PCR-bound key policy, but the key has none
STATUS_PCP_NOT_PCR_BOUND says that the key does not have the Platform Configuration Register (PCR) information needed by the request. PCR binding is a policy relationship between key use and measured platform state; it is not the same as merely having a TPM installed.
A key can be TPM-backed and still fail an operation that expects PCR policy. This status should lead to a policy comparison: which PCR selection and measurement assumptions does the workflow require, and was the key provisioned with compatible policy?
What to check
- Record the requested PCR policy, the key's provisioned policy, and the boot or configuration state relevant to the workflow.
- Distinguish a missing PCR binding from a current-PCR mismatch; the remedy may be different and should not be guessed from the code name alone.
- If policy must change, follow the application's supported re-provisioning procedure rather than editing opaque key metadata.
References
- Microsoft: PCP and TPM error codes
- Microsoft: TPM fundamentals
- Trusted Computing Group: TPM 2.0 Library Specification
Looking for a different code? Search another status or error code.