| Previous | Next |
| STATUS_PCP_CLAIM_TYPE_NOT_SUPPORTED | STATUS_PCP_BUFFER_LENGTH_MISMATCH |
STATUS_PCP_TPM_VERSION_NOT_SUPPORTED
The requested PCP operation exceeds the TPM version supported by the workflow
STATUS_PCP_TPM_VERSION_NOT_SUPPORTED is a compatibility result: PCP found a TPM, but the active TPM version cannot support the requested feature or policy. It is distinct from device-not-found, device-not-ready, and a malformed request.
Do not infer feature support from the presence of a TPM alone. TPM 1.2 and TPM 2.0 have different command and policy models, while an enterprise workflow can impose additional provider and Windows-version constraints.
What to check
- Record TPM version, manufacturer/firmware details, Windows version, and the exact PCP feature or key policy being requested.
- Compare the deployment requirements with the platform instead of changing a policy to a weaker setting without approval.
- For a managed fleet, segregate unsupported hardware in the enrollment plan rather than repeatedly attempting the same incompatible operation.
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.