| 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. For FVE_E_RAW_ACCESS, it belongs to the volume state and geometry part of BitLocker rather than to generic file I/O.
For FVE_E_RAW_ACCESS, note: Use the volume GUID and current storage topology as the stable identity. When diagnosing FVE_E_RAW_ACCESS, remember: Drive letters, mount points and cluster paths are presentation details and can point to the wrong object during recovery. For FVE_E_RAW_ACCESS, note: The BitLocker provider tracks encryption conversion, protection, lock state, metadata version, filesystem geometry and outstanding volume use independently. When diagnosing FVE_E_RAW_ACCESS, remember: 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? | For FVE_E_RAW_ACCESS, 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
- For
FVE_E_RAW_ACCESS, record raw-access owner, initiating API, volume lock state, filter stack, outstanding handles and the transition that entered raw mode. ForFVE_E_RAW_ACCESS, keep the full HRESULT and the first method that returned it because later cleanup calls can report a different state. - For
FVE_E_RAW_ACCESS, capturemanage-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
FVE_E_RAW_ACCESSfailure and note the boot session, caller identity and management source; that evidence separates this BitLocker condition from a generic access or storage error.
Change only the failed prerequisite
complete or cancel the owning recovery/maintenance operation and allow BitLocker to leave raw mode before retrying normal management. For FVE_E_RAW_ACCESS, collect a fresh state snapshot and issue a single retry from the same management layer.
manage-bde -status
powershell -NoProfile -Command "Get-BitLockerVolume | Format-List *"Do not delete all key protectors, clear a TPM, reformat a partition or decrypt the volume as a generic response to FVE_E_RAW_ACCESS; those actions affect different trust layers and can destroy the easiest recovery route.
State checks specific to FVE_E_RAW_ACCESS
| Checkpoint | How to interpret it for FVE_E_RAW_ACCESS |
|---|---|
| Before the call | Record the target identity and the pre-call volume state and geometry state. For FVE_E_RAW_ACCESS, the decisive boundary is that 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 FVE_E_RAW_ACCESS 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. The FVE_E_RAW_ACCESS request should then advance without removing an unrelated recovery route. |
| After reboot or remount | Recheck protection, conversion and lock state for FVE_E_RAW_ACCESS; a successful management call is incomplete if the next boot cannot unlock the volume. |
Verification after the change
For FVE_E_RAW_ACCESS, success means more than the absence of a dialog. Confirm that the condition represented by FVE_E_RAW_ACCESS 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 FVE_E_RAW_ACCESS request advances to another HRESULT, record both values in order because that transition reveals the next unmet prerequisite.
Official documentation
Reference set for FVE_E_RAW_ACCESS:
- Microsoft: GetLockStatus method
- Microsoft: BitLocker operations guide
- Microsoft: manage-bde status
- Microsoft: GetConversionStatus method
Looking for a different code? Search another status or error code.