| Previous | Next |
| STATUS_OFFLOAD_READ_FLT_NOT_SUPPORTED | STATUS_OFFLOAD_READ_FILE_NOT_SUPPORTED |
STATUS_OFFLOAD_WRITE_FLT_NOT_SUPPORTED
A destination filter prevents token-based data placement
FSCTL_OFFLOAD_WRITE presents a token to the destination stack and requests that the storage subsystem place the represented data without sending all bytes through the host. This status means a destination file-system filter cannot participate safely in that path. The source token might still be valid, and ordinary copying can remain available.
The destination side has different obligations from token creation: it must preserve destination file semantics, allocation, policy, and any transformation performed by filters. A filter may reject offload when it needs to inspect or rewrite writes, when the file has unsupported metadata, or when its implementation does not advertise offload support.
What to inspect
- Inspect the destination filter stack separately from the source stack.
- Verify destination allocation, valid-data length, alignment, file attributes, and filter policy.
- Record whether the failure occurs before any bytes are reported written and whether fallback follows.
- Avoid reusing the token after its lifetime or source data validity has changed.
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.