| Previous | Next |
| FVE_E_NO_PASSPHRASE_WITH_TPM | FVE_E_NOT_ALLOWED_ON_CSV_STACK |
FVE_E_NO_TPM_WITH_PASSPHRASE
What BitLocker has already established
At HRESULT 0x803100AC, BitLocker has determined that the requested TPM protector conflicts with an existing password protector on the volume. The FVE_E_NO_TPM_WITH_PASSPHRASE code does not by itself say that the volume master key is lost or that user data is corrupt.
Operational boundary: key-protector lifecycle.
A BitLocker key protector wraps access to the volume master key. TPM, TPM+PIN, startup key, recovery password, password, certificate and Network Unlock protectors have different volume and policy rules; changing one is not the same as decrypting the volume. Never capture PINs, passwords or recovery passwords in logs. IDs, types, policy, call result and attempt counters are sufficient for most diagnosis.
Data to preserve before changing state
Related state to rule out
Do not merge this incident with TPM not ready or disabled; here the conflict exists even if the TPM is healthy. If both appear with this result in one trace, preserve ordering because the first HRESULT normally identifies the prerequisite that caused later cleanup or fallback messages.
How to retest without losing evidence
Remove the incompatible password protector only after validating another recovery path, then add the approved TPM combination.
manage-bde -protectors -get C:
powershell -NoProfile -Command "Get-BitLockerVolume C: | Format-List KeyProtector,ProtectionStatus,VolumeStatus"State checks specific to FVE_E_NO_TPM_WITH_PASSPHRASE
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call key-protector lifecycle state. The requested TPM protector conflicts with an existing password protector on the volume. |
| At failure | Preserve protector list, volume type, TPM readiness, policy and the order in which protectors were added. |
Microsoft references
Looking for a different code? Search another status or error code.