| 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?
- For this result, 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?
- For this result, resolve effective policy, Windows edition, caller token and management source for the volume state and geometry operation.
- Is the result state stable?
- For this result, record conversion, protection, lock and reboot status before modifying anything.
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: Use the volume GUID and current storage topology as the stable identity. When diagnosing it, remember: 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. Keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state.
- capture
manage-bde -statusand 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.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"Correct the configuration deliberately
- close consumers and explicitly dismount or move ownership using supported tools; do not force metadata changes through open handles.
- 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 it 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.
Treat it as a state label rather than a complete recovery plan. Confirm a successful retry with an updated BitLocker state query and a verified recovery path.
State checks specific to it
| 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 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. This proves whether it came from BitLocker itself or from a wrapper translating another result. |
| After correction | Close consumers and explicitly dismount or move ownership using supported tools; do not force metadata changes through open handles. 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:
- Microsoft: BitLocker operations guide
- Microsoft: manage-bde status
- Microsoft: GetConversionStatus method
- Microsoft: GetLockStatus method
Looking for a different code? Search another status or error code.