HRESULT 0x8031005A (FVE_E_NO_FEATURE

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.

Previous	Next
FVE_E_VOLUME_HANDLE_OPEN	FVE_E_INVALID_STARTUP_OPTIONS

FVE_E_NO_FEATURE_LICENSE

The exact BitLocker boundary

FVE_E_NO_FEATURE_LICENSE (0x8031005A) identifies the point where Windows includes BitLocker but the requested advanced feature is not licensed in the installed edition. For FVE_E_NO_FEATURE_LICENSE, note: BitLocker evaluates the target volume together with effective Group Policy or MDM policy, Windows edition, caller authorization and the requested protector or management method. When diagnosing FVE_E_NO_FEATURE_LICENSE, remember: A policy HRESULT therefore describes a rejected configuration decision, not evidence that encrypted sectors are damaged.

For FVE_E_NO_FEATURE_LICENSE, note: When policy is the boundary, retrying under SYSTEM does not necessarily help: policy can forbid the operation for every caller. When diagnosing FVE_E_NO_FEATURE_LICENSE, remember: Separate authorization from allow/require/disallow settings before changing identities.

Do not confuse it with a nearby failure

Keep this separate from FVE_E_NO_LICENSE, which indicates BitLocker as a whole is unavailable. For FVE_E_NO_FEATURE_LICENSE, 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

For FVE_E_NO_FEATURE_LICENSE, record Windows SKU, requested feature such as hardware encryption or Network Unlock, edition transition history and the API returning the code. For FVE_E_NO_FEATURE_LICENSE, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
For FVE_E_NO_FEATURE_LICENSE, capture manage-bde -status and the protector inventory for the exact volume GUID, not only the drive letter, because letters can change in WinRE, clusters and deployment environments.
Export BitLocker operational events for the FVE_E_NO_FEATURE_LICENSE failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

manage-bde -status
gpresult /h bitlocker-policy.html

Safe corrective sequence

For FVE_E_NO_FEATURE_LICENSE, verify the feature matrix for the installed edition and use a supported edition upgrade if the capability is required.
After correcting the FVE_E_NO_FEATURE_LICENSE prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the FVE_E_NO_FEATURE_LICENSE condition is still active.
Before a FVE_E_NO_FEATURE_LICENSE remediation deletes protectors, changes firmware mode, resizes partitions or decrypts a production drive, verify that an independent recovery method is available and escrowed in the intended directory or account.

For FVE_E_NO_FEATURE_LICENSE, the boundary above identifies which BitLocker state must change before a retry can be meaningful; repeating the call without changing that state only adds noise.

State checks specific to FVE_E_NO_FEATURE_LICENSE

Checkpoint	How to interpret it for FVE_E_NO_FEATURE_LICENSE
Before the call	Record the target identity and the pre-call policy and authorization state. For FVE_E_NO_FEATURE_LICENSE, the decisive boundary is that Windows includes BitLocker but the requested advanced feature is not licensed in the installed edition.
At failure	Preserve Windows SKU, requested feature such as hardware encryption or Network Unlock, edition transition history and the API returning the code. This proves whether FVE_E_NO_FEATURE_LICENSE came from BitLocker itself or from a wrapper translating another result.
After correction	Verify the feature matrix for the installed edition and use a supported edition upgrade if the capability is required. The FVE_E_NO_FEATURE_LICENSE request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for FVE_E_NO_FEATURE_LICENSE; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

For FVE_E_NO_FEATURE_LICENSE, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_NO_FEATURE_LICENSE now matches the intended design, that the protector inventory has not lost an independent recovery route, and that the next reboot or remount can unlock the volume. If the FVE_E_NO_FEATURE_LICENSE request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for FVE_E_NO_FEATURE_LICENSE:

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