| Previous | Next |
| STATUS_FVE_TPM_SRK_AUTH_NOT_ZERO | STATUS_FVE_TPM_NO_VMK |
STATUS_FVE_TPM_INVALID_PCR
What this BitLocker status means
TPM protectors can bind key release to measured boot state. This status indicates that the expected PCR-based validation did not succeed, or that the TPM temporarily prevents access until restart; it is not simply a wrong user PIN.
State to verify
Record recent firmware, Secure Boot, boot-order, BCD, boot-manager, or hardware changes and compare them with the expected maintenance process. Use the approved recovery method to regain access, then investigate the measurement change rather than disabling security features to suppress the symptom.
Recovery and confirmation
The distinction matters: STATUS_FVE_AUTH_INVALID_APPLICATION is about a boot application hash, while STATUS_FVE_AUTH_INVALID_CONFIG is about boot configuration. This status is the protector’s PCR validation outcome.
Official references
BitLocker preboot recovery guidance | TCG TPM 2.0 Library | BitLocker recovery overview
Looking for a different code? Search another status or error code.