| Previous | Next |
| STATUS_PCP_KEY_USAGE_POLICY_INVALID | STATUS_PCP_KEY_NOT_AUTHENTICATED |
STATUS_PCP_SOFT_KEY_ERROR
The provider could not import this software-originated key into TPM storage
STATUS_PCP_SOFT_KEY_ERROR indicates a problem while importing software key material into the TPM-backed provider. Hardware-backed key storage is not a transparent file copy: the provider, key format, algorithm, policy, parent hierarchy, and intended use must all be compatible with the target TPM workflow.
This status does not prove that the original software key is corrupt. It says that the import path, as requested, could not establish a usable PCP key. Exportability and migration restrictions may be deliberate security properties of the source or destination key.
What to check
- Record the source key format, algorithm, export policy, provider, and the exact import API/property sequence.
- Confirm that the product officially supports importing that key class into PCP; do not transform protected key blobs with ad hoc tools.
- If the goal is hardware-backed identity, assess whether generating a new TPM key and re-enrolling it is the supported design.
References
- Microsoft: PCP and TPM error codes
- Microsoft: CNG Key Storage Providers
- Microsoft: NCryptCreatePersistedKey
Looking for a different code? Search another status or error code.