HRESULT 0x8031004A (FVE_E_NOT_ON_STACK): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.

Previous	Next
FVE_E_NO_LICENSE	FVE_E_FS_MOUNTED

FVE_E_NOT_ON_STACK

What BitLocker has already established

At HRESULT 0x8031004A, BitLocker has determined that the BitLocker filter or critical boot components are not correctly present in the active storage stack. The FVE_E_NOT_ON_STACK code does not by itself say that the volume master key is lost or that user data is corrupt.

Operational boundary: volume state and geometry.

Note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing this result, remember: Two volumes can both appear “encrypted” in a UI while being in very different states for a management API. Note: Conversion status and protection status answer different questions: sectors can be encrypted while protectors are suspended, and a fully decrypted volume can still contain stale management context in a caller.

Data to preserve before changing state

record loaded storage filters, driver/service state, boot configuration, component integrity results and the first BitLocker event after startup. 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.

Related state to rule out

Do not merge this incident with a volume that is simply decrypted; this condition concerns the driver and boot component path used to manage the volume. 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

Repair Windows components and boot files using supported servicing tools before changing protectors or volume metadata.

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
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"

Diagnosis should be driven by the target object, effective policy and captured state snapshot rather than by a generic remediation applied to every BitLocker error.

Verify the active storage and boot component path

BitLocker relies on its volume filter and boot-time components being present that owns the target volume. Offline image modification, damaged boot files, filter-order problems or incomplete servicing can leave management APIs unable to reach that path even though NTFS still mounts.

Collect loaded filters and component-integrity results, repair the Windows image and boot files through supported servicing, and reboot before touching protectors. Formatting the volume would address the wrong layer.

State checks specific to the result

Checkpoint	How to interpret it for it
Before the call	Record the target identity and the pre-call volume state and geometry state. The decisive boundary is that the BitLocker filter or critical boot components are not correctly present in the active storage stack.
At failure	Preserve loaded storage filters, driver/service state, boot configuration, component integrity results and the first BitLocker event after startup. This proves whether it came from BitLocker itself or from a wrapper translating another result.
After correction	Repair Windows components and boot files using supported servicing tools before changing protectors or volume metadata. 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.

Microsoft references

Reference set for it:

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