| Previous | Next |
| STATUS_FVE_TPM_DISABLED | STATUS_FVE_TPM_INVALID_PCR |
STATUS_FVE_TPM_SRK_AUTH_NOT_ZERO
TPM SRK authorization is not zero
STATUS_FVE_TPM_SRK_AUTH_NOT_ZERO is a BitLocker/TPM provisioning status. In TPM 1.2 terminology, the Storage Root Key is the root for TPM-protected storage objects, and BitLocker expects Windows-managed TPM ownership and authorization state to match its protector model.
This status usually points at TPM ownership/provisioning history rather than encrypted-volume corruption. A machine that was pre-owned, manually provisioned, cleared inconsistently, or migrated from older TPM management can expose unexpected SRK authorization state.
Diagnostic focus
- Check TPM ownership/provisioning state before changing BitLocker protectors.
- Record whether the system uses TPM 1.2 or TPM 2.0 and whether Windows auto-provisioning was disabled.
- Use approved TPM clear/reprovision procedures only after recovery material is safely backed up.
References
- TCG: TPM Main Specification
- Microsoft: TPM Base Services
- Microsoft: BitLocker FAQ
- Microsoft: BitLocker preboot recovery screen
- Microsoft: BitLocker FAQ
- Microsoft: BitLocker preboot recovery screen
Looking for a different code? Search another status or error code.