| Previous | Next |
| ERROR_OFFLOAD_READ_FLT_NOT_SUPPORTED | ERROR_OFFLOAD_READ_FILE_NOT_SUPPORTED |
ERROR_OFFLOAD_WRITE_FLT_NOT_SUPPORTED
A filter in the destination path cannot process the offloaded write
The write half of ODX presents a token obtained from the source and asks the destination storage stack to materialize the represented data range. A destination minifilter must preserve the semantics of a normal write, including any transformation or policy it applies. This error means a filter cannot guarantee those semantics for the offloaded operation.
Inspect filters attached to the destination volume separately from the source. A product may support offload-read but reject offload-write because destination writes trigger scanning, encryption, journaling, replication, or classification. Do not assume that a successful token creation guarantees token use. Record the fallback path and ensure partial offload progress does not lead to duplicate or skipped ranges.
What to inspect
- Identify destination filters and write-time transformations.
- Track token creation separately from token application.
- Verify fallback resumes at the correct destination offset.
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.