HRESULT 0x80310049 (FVE_E_NO_LICENSE): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system.

Previous	Next
FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED	FVE_E_NOT_ON_STACK

FVE_E_NO_LICENSE

Read this as a state-machine result

FVE_E_NO_LICENSE is a BitLocker facility HRESULT, not a Win32 filesystem error wrapped by an application. In this case the installed Windows product edition does not license BitLocker Drive Encryption as a product capability.

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 this result, remember: A policy HRESULT therefore describes a rejected configuration decision, not evidence that encrypted sectors are damaged.

What the code does not prove

The closest misleading interpretation is a feature-specific policy setting or a missing optional component; edition entitlement is the first boundary. Verify the returning method and state transition before assigning the incident to disk corruption, TPM failure or bad credentials.

Inspect the target, not just the message

record Windows edition and activation state, servicing image, SKU changes, exact BitLocker entry point and whether only a particular feature or all BitLocker management is unavailable. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
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 result failure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.

Note: A managed restriction is part of the security design. When diagnosing this result, remember: Record which authority delivered it and whether the requested operation is mandatory for compliance or merely a convenience feature.

A low-risk recovery path

confirm the supported edition and upgrade through a licensed path rather than copying binaries or changing undocumented registry values.
After correcting the result prerequisite, refresh protection, conversion and lock state before one controlled retry; a cached UI message is not proof that the condition is still active.
Before a this result 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.

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

Result Interpretation

After correction, compare the new conversion, protection and lock state with the original snapshot. A different HRESULT after this result is useful because it means the request crossed this boundary and reached the next prerequisite.

Edition entitlement precedes every volume check

It is established from the installed Windows SKU before BitLocker evaluates a disk, TPM or protector. A healthy volume and ready TPM cannot supply a product capability that the edition does not license. Capture the exact edition, servicing image and any incomplete edition-upgrade state.

Use a supported edition transition and confirm activation afterward. Copying executables, enabling services manually or editing feature registry keys cannot create a valid BitLocker entitlement.

State checks specific to it

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call policy and authorization state. The decisive boundary is that the installed Windows product edition does not license BitLocker Drive Encryption as a product capability.
At failure	Preserve Windows edition and activation state, servicing image, SKU changes, exact BitLocker entry point and whether only a particular feature or all BitLocker management is unavailable. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Confirm the supported edition and upgrade through a licensed path rather than copying binaries or changing undocumented registry values. The request should then advance without removing an unrelated recovery route.
After reboot or remount	Recheck protection, conversion and lock state for it; a successful management call is incomplete if the next boot cannot unlock the volume.

Verification after the change

Success means more than the absence of a dialog. Confirm that the condition represented by it 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 request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.

References

Reference set for it:

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