| 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.
The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. Two volumes can both appear “encrypted” in a UI while being in very different states for a management API. 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
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.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"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 FVE_E_NOT_ON_STACK
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. 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. |
Microsoft references
Looking for a different code? Search another status or error code.