| Previous | Next |
| STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILEOFFSET | STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_PARAMETER |
STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILERANGE
The encrypted-data range is internally inconsistent
STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILERANGE identifies the combination of offset and length in raw encrypted-file metadata. It is not merely “offset bad” or “buffer too short”: the range as a pair is invalid for the encrypted data being read or written.
The supported raw EFS backup interfaces pass opaque encrypted data through callbacks. An export implementation should preserve every block supplied by ReadEncryptedFileRaw, and an import implementation should return the saved stream through the WriteEncryptedFileRaw callback sequence. Rechunking for transport is acceptable only if the original byte stream is reconstructed exactly before it reaches the EFS import path.
Inspect integer-width conversions and resume logic carefully. Truncating a length, losing bytes between chunks, duplicating a resumed block, or associating raw data with the wrong destination file can turn individually plausible values into an impossible range. Do not synthesize a new range from the visible file size because raw encrypted backup data includes EFS-specific information beyond ordinary plaintext I/O semantics.
What to inspect
- Offset and length values observed by the failing lower layer and the total raw stream length preserved by the backup.
- Chunk assembly and resume checkpoints, especially 32-bit to 64-bit conversions and partial callback handling.
- The identity of the source export and destination import contexts to rule out cross-file stream reuse.
References
- Microsoft: Backup and Restore of Encrypted Files
- Microsoft: ReadEncryptedFileRaw
- Microsoft: WriteEncryptedFileRaw
- Microsoft Open Specifications: Encrypting File System overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.