| Previous | Next |
| FVE_E_DEBUGGER_ENABLED | FVE_E_RAW_BLOCKED |
FVE_E_RAW_ACCESS
Where the operation stops
The value 0x80310050, named FVE_E_RAW_ACCESS, is returned when the volume is currently exposed through BitLocker raw-access mode, so the requested normal management action was intentionally not performed. It belongs to the volume state and geometry part of BitLocker rather than to generic file I/O.
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. 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.
| Question | What to verify |
|---|---|
| Which object failed? | The exact volume GUID, protector GUID, certificate or API target supplied by the caller. |
| Which state matters? | raw-access owner, initiating API, volume lock state, filter stack, outstanding handles and the transition that entered raw mode. |
| What is the nearest false lead? | a raw disk opened by an unrelated storage utility; BitLocker raw-access mode is an explicit internal state of the encrypted volume path. |
Build a minimal diagnostic record
- Record raw-access owner, initiating API, volume lock state, filter stack, outstanding handles and the transition that entered raw mode.
Change only the failed prerequisite
complete or cancel the owning recovery/maintenance operation and allow BitLocker to leave raw mode before retrying normal management.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"State checks specific to FVE_E_RAW_ACCESS
| Stage | How to interpret it |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. The volume is currently exposed through BitLocker raw-access mode, so the requested normal management action was intentionally not performed. |
| At failure | Preserve raw-access owner, initiating API, volume lock state, filter stack, outstanding handles and the transition that entered raw mode. This proves whether this result came from BitLocker itself or from a wrapper translating another result. |
| After correction | Complete or cancel the owning recovery/maintenance operation and allow BitLocker to leave raw mode before retrying normal management. |
Official documentation
Looking for a different code? Search another status or error code.