| Previous | Next |
| STATUS_OFFLOAD_READ_FILE_NOT_SUPPORTED | STATUS_WOF_WIM_HEADER_CORRUPT |
STATUS_OFFLOAD_WRITE_FILE_NOT_SUPPORTED
The destination file cannot accept an offload token
This status is returned when the destination file does not satisfy the file-system requirements for FSCTL_OFFLOAD_WRITE. The storage array might support ODX and the token might be well formed, yet the target stream, allocation state, attributes, or range can still make an offloaded write invalid.
Offload write is an optimization, not a requirement for data correctness. A robust caller falls back to an ordinary copy and handles any partial LengthWritten result before continuing. Recreating the destination file can change semantics such as security descriptors, alternate streams, sparse layout, or application-visible identity, so it should not be an automatic workaround.
What to inspect
- Record destination file system, file type, allocation size, EOF, VDL, offset, length, and relevant attributes.
- Verify required alignment and that the destination was prepared according to the ODX contract.
- Check whether any portion was written before fallback and resume at the correct byte offset.
- Preserve destination metadata and sharing semantics when switching to the normal copy path.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Offloaded Data Transfers
- Microsoft Open Specifications: FSCTL_OFFLOAD_WRITE
- Microsoft: ODX compatibility guidance
Looking for a different code? Search another status or error code.