| Previous | Next |
| FVE_E_NOT_ON_STACK | FVE_E_TOKEN_NOT_IMPERSONATED |
FVE_E_FS_MOUNTED
Why this is not a generic disk error
The practical meaning of FVE_E_FS_MOUNTED is that an operation requiring an offline or dismounted filesystem was attempted while the volume still has open use. The HRESULT is 0x8031004B.
Three decisions before remediation
- Is the result target correct?
- Use the volume or protector GUID and confirm its role; do not rely only on a drive letter or friendly name.
- Is the result request allowed?
- Resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
- Is the result state stable?
- Record conversion, protection, lock and reboot status before modifying anything.
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. Use the volume GUID and current storage topology as the stable identity. Drive letters, mount points and cluster paths are presentation details and can point to the wrong object during recovery.
Why a common workaround is wrong
This should not be diagnosed as a BitLocker-locked volume; a mounted volume is accessible and busy, while a locked volume has no usable clear key. That nearby condition needs a different corrective action and may produce a similar user-facing message.
Confirm the returning layer
- Record mount points, open handles, current working directories, paging or service use, cluster ownership and the exact lock/dismount call.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"State checks specific to FVE_E_FS_MOUNTED
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. An operation requiring an offline or dismounted filesystem was attempted while the volume still has open use. |
| At failure | Preserve mount points, open handles, current working directories, paging or service use, cluster ownership and the exact lock/dismount call. |
| After correction | Close consumers and explicitly dismount or move ownership using supported tools; do not force metadata changes through open handles. |
References
Looking for a different code? Search another status or error code.