| Previous | Next |
| FVE_E_NO_EXISTING_PASSPHRASE | FVE_E_PASSPHRASE_TOO_LONG |
FVE_E_PROTECTOR_CHANGE_PASSPHRASE_MISMATCH
The exact BitLocker condition
FVE_E_PROTECTOR_CHANGE_PASSPHRASE_MISMATCH (0x803100A9) identifies the point where the current password supplied for an in-place protector change does not match the existing password protector. 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.
Do not confuse it with a nearby failure
Keep this separate from a new password that violates length or complexity policy. That distinction determines whether the next check belongs to policy, protector inventory, volume geometry, firmware, account escrow or the calling application's buffer contract.
Evidence that distinguishes the condition
manage-bde -protectors -get C:
powershell -NoProfile -Command "Get-BitLockerVolume C: | Format-List KeyProtector,ProtectionStatus,VolumeStatus"Safe corrective sequence
- Use the correct current password or an authorized reset/recovery workflow and stop automated retries with stale credentials.
State checks specific to FVE_E_PROTECTOR_CHANGE_PASSPHRASE_MISMATCH
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call key-protector lifecycle state. The current password supplied for an in-place protector change does not match the existing password protector. |
| At failure | Preserve protector GUID, change versus reset path, failed-attempt history, policy result and caller authorization without recording the password. |
References
Looking for a different code? Search another status or error code.