| Previous | Next |
| STATUS_PCP_KEY_ALREADY_FINALIZED | STATUS_PCP_KEY_USAGE_POLICY_INVALID |
STATUS_PCP_KEY_USAGE_POLICY_NOT_SUPPORTED
The policy concept is known, but this provider cannot implement it
STATUS_PCP_KEY_USAGE_POLICY_NOT_SUPPORTED means that the requested key-usage policy is not supported by the active Platform Crypto Provider environment. The key difference from an invalid policy is capability: a policy can be well-formed yet unavailable because of TPM version, provider implementation, firmware capability, or the selected key type.
Treat the status as a compatibility boundary. Substituting a weaker or software-only policy to keep an enrollment flow moving can defeat the requirement the policy was meant to enforce.
What to check
- Identify the exact policy and capability that the application requested, rather than logging a generic "TPM policy failed" message.
- Compare TPM version, provider configuration, Windows release, firmware level, and key algorithm with the deployment requirements.
- Decide explicitly whether the scenario permits a supported alternative; do not silently degrade hardware-backed assurance.
References
- Microsoft: PCP and TPM error codes
- Microsoft: CNG Key Storage Providers
- Trusted Computing Group: TPM 2.0 Library Specification
Looking for a different code? Search another status or error code.