| Previous | Next |
| STATUS_RWRAW_ENCRYPTED_FILE_NOT_ENCRYPTED | STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILERANGE |
STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILEOFFSET
The raw encrypted stream contains invalid offset metadata
STATUS_RWRAW_ENCRYPTED_INVALID_EDATAINFO_FILEOFFSET is narrower than a normal read or write offset error. It refers to the encrypted-data information carried by the raw EFS I/O path. Public Win32 backup APIs intentionally expose the raw encrypted file as callback data: ReadEncryptedFileRaw supplies blocks to an export callback, and WriteEncryptedFileRaw obtains blocks from an import callback.
The public API documentation does not define an application structure named EDATAINFO that callers should patch field by field. For code using the supported raw API, the safe rule is to preserve the exported byte stream exactly and feed it back through the documented import sequence. Repacking, interpreting, or seeking within opaque raw data can corrupt internal offset metadata.
Do not “fix” the failure by rounding the offset as though it were a sector-alignment problem. Compare the exported stream, callback byte counts, resume storage, and any transformation layer between export and import. If a private or file-system-level producer builds this information directly, validate it against the implementation that consumes it rather than inferring the layout from the NTSTATUS name.
What to inspect
- The exact raw stream bytes and total byte count produced by the export callback sequence.
- Any buffering, framing, deduplication, compression, encryption, or resume layer that can alter callback boundaries or bytes.
- Whether import starts with
CREATE_FOR_IMPORTand supplies the same raw stream in the documented lifecycle.
References
- Microsoft: Backup and Restore of Encrypted Files
- Microsoft: ReadEncryptedFileRaw
- Microsoft: WriteEncryptedFileRaw
- Microsoft: OpenEncryptedFileRaw
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.