| Previous | Next |
| STATUS_FVE_REBOOT_REQUIRED | STATUS_FVE_RAW_BLOCKED |
STATUS_FVE_RAW_ACCESS
Meaning and context of STATUS_FVE_RAW_ACCESS
This status identifies a BitLocker control mode. It does not mean that the file system is damaged or that a recovery credential was rejected; the requested action was evaluated while the volume was in raw-access mode and no normal action was taken.
Record the exact management operation, caller, target volume, conversion state, and whether the drive is a system, fixed-data, removable-data, or clustered volume. Those facts determine which management path is valid; a drive letter alone does not.
Use manage-bde -status or the BitLocker WMI provider to observe the state before changing configuration. Do not attempt to bypass the condition by writing raw sectors or removing protectors, because those actions do not explain why raw access was selected.
BitLocker status | Win32_EncryptableVolume | BitLocker operations
Native status interpretation
STATUS_FVE_RAW_ACCESS is 0xC0210022, an NTSTATUS error value. AllStat describes it as “No action was taken as BitLocker Drive Encryption is in RAW access mode.”. The first useful question is which native API, IRP, protocol operation, or subsystem in the kernel, native API, or subsystem that returned the status produced that status.
Debugging sequence
- Preserve this result before RtlNtStatusToDosError, HRESULT conversion, exception translation, or provider-specific remapping removes information.
- Compare the exact fve / raw / access operation on a working system and record differences in object lifetime, access token, device state, negotiated protocol, and policy.
- For kernel I/O, keep the device stack, IRP major/minor function, request parameters, completion routine, and the first component that completed the request with this result.
Recovery considerations
A retry is appropriate only after the owner of this result has changed the state described by “No action was taken as BitLocker Drive Encryption is in RAW access mode.”, or when its contract explicitly marks the status as transient. If the value reports corruption, invalid format, access policy, or a lifecycle mismatch, preserve evidence and correct that cause before repeating the request.
Looking for a different code? Search another status or error code.