| Previous | Next |
| FVE_E_INVALID_PIN_CHARS_DETAILED | FVE_E_DEVICELOCKOUT_COUNTER_MISMATCH |
FVE_E_DEVICE_LOCKOUT_COUNTER_UNAVAILABLE
What BitLocker has already established
At HRESULT 0x803100CD, BitLocker has determined that BitLocker requested a hardware-backed replay or lockout counter, but the platform exposes no usable counter. The FVE_E_DEVICE_LOCKOUT_COUNTER_UNAVAILABLE code does not by itself say that the volume master key is lost or that user data is corrupt.
Operational boundary: automatic Device Encryption.
Automatic Device Encryption is a provisioning and compliance workflow layered on BitLocker. It evaluates platform eligibility, account-backed recovery escrow, all applicable fixed volumes and protection state; failure of Auto-DE does not automatically mean manual BitLocker is unavailable. “Encrypted” and “protected” are not synonyms. Compliance normally requires active protectors and recoverable escrow, not merely a completed sector conversion.
Data to preserve before changing state
Related state to rule out
Do not merge this incident with a counter mismatch after a counter exists; this platform cannot supply the capability at all. 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
Update supported firmware if a counter should exist or use a policy design that does not depend on unavailable hardware replay protection.
msinfo32.exe
powershell -NoProfile -Command "Get-BitLockerVolume | Format-Table MountPoint,VolumeType,VolumeStatus,ProtectionStatus"
State checks specific to FVE_E_DEVICE_LOCKOUT_COUNTER_UNAVAILABLE
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call automatic Device Encryption state. BitLocker requested a hardware-backed replay or lockout counter, but the platform exposes no usable counter. |
| At failure | Preserve TPM/platform capability, firmware version, device-encryption support reason, counter-provider events and requested lockout policy. |
Microsoft references
Looking for a different code? Search another status or error code.
