| Previous | Next |
| ERROR_OFFLOAD_READ_FILE_NOT_SUPPORTED | ERROR_ALREADY_HAS_STREAM_ID |
ERROR_OFFLOAD_WRITE_FILE_NOT_SUPPORTED
The destination file or stream is not eligible for an offloaded write
An ODX-capable device does not guarantee that every destination file can consume every token. The destination file-system state, stream type, allocation, transformation features, token compatibility, or storage relationship can make offload-write unavailable. The error is scoped to the destination operation and should not be confused with an invalid source read.
Inspect the destination file attributes and the relationship between source and destination storage. A token can be valid yet unusable on a different subsystem or after its validity interval. Capture bytes written before failure and the returned transfer length so fallback begins at the correct range. Validate final file contents exactly as for a normal copy; offloading changes data movement, not correctness requirements.
What to inspect
- Check destination attributes, stream type, and storage subsystem.
- Validate token lifetime and source-destination compatibility.
- Resume fallback from the confirmed completed byte range.
References
- Microsoft: ODX from the file-system and minifilter perspective
- Microsoft: storage offloaded data transfer
- Microsoft: offloaded copy token workflow
Looking for a different code? Search another status or error code.