What does HRESULT 0x80310098 (FVE_E_FIPS_HASH_KDF_NOT_ALLOWED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments.

Previous	Next
FVE_E_CANT_LOCK_AUTOUNLOCK_ENABLED_VOLUME	FVE_E_ENH_PIN_INVALID

FVE_E_FIPS_HASH_KDF_NOT_ALLOWED

The failed prerequisite

FVE_E_FIPS_HASH_KDF_NOT_ALLOWED / 0x80310098 marks a rejected BitLocker transition: the smart-card public-key protector requires a key-derivation function that the card cannot perform under active FIPS restrictions.

The same volume can remain strongly encrypted while a recovery-password, passphrase or export operation is rejected. Report the protector operation, not simply “BitLocker failed.”

Diagnostic map

Layer	FIPS-restricted key management
Proof to collect	smart-card model and middleware, certificate key type, advertised KDF support, FIPS policy and the exact protector operation
Different condition	a certificate trust or private-key access error; the certificate may be valid while the KDF capability is incompatible
First safe change	use a FIPS-compatible smart card/provider or an approved alternative protector rather than falling back silently to a disallowed KDF

FIPS-restricted operation changes which protector, export and key-derivation paths BitLocker may use. The volume encryption algorithm and the protector workflow are separate layers, so a FIPS-related HRESULT should be traced to the exact protector or key-management call.

A focused verification sequence

Recommended operational response

Use a FIPS-compatible smart card/provider or an approved alternative protector rather than falling back silently to a disallowed KDF.

manage-bde -protectors -get C:
gpresult /h bitlocker-policy.html

State checks specific to FVE_E_FIPS_HASH_KDF_NOT_ALLOWED

Stage	How to interpret it
Before the call	Record the target identity and the pre-call FIPS-restricted key management state. The smart-card public-key protector requires a key-derivation function that the card cannot perform under active FIPS restrictions.
At failure	Preserve smart-card model and middleware, certificate key type, advertised KDF support, FIPS policy and the exact protector operation.

Official references

Looking for a different code? Search another status or error code.