| Previous | Next |
| STATUS_REQUEST_PAUSED | STATUS_DISK_RESOURCES_EXHAUSTED |
STATUS_NO_RANGES_PROCESSED
This status has a documented FSCTL_FILE_LEVEL_TRIM contract
STATUS_NO_RANGES_PROCESSED has a concrete file-system control meaning in Microsoft documentation. The FSCTL_FILE_LEVEL_TRIM reply can return this status when the operation completes but none of the ranges in the request were processed. This is different from a partially successful trim where some ranges are reported as processed.
FSCTL_FILE_LEVEL_TRIM accepts one or more byte ranges in FILE_LEVEL_TRIM. The file system translates those ranges to storage trim/unmap behavior so backing storage can reclaim or reorganize physical resources; Microsoft specifically cites fixed-size virtual disk files as a use case. The protocol specification also lists range validation and overflow errors separately.
Capture every requested offset and length, the file attributes, output range count, and the underlying volume/file-system type. Check whether the file is compressed or encrypted and whether the request buffer describes valid ranges. Do not assume the file data was zeroed: trim is a storage-management hint/operation, and “no ranges processed” says the requested reclamation did not affect any range.
What to inspect
- Log all trim offsets and lengths before issuing the FSCTL.
- Inspect the returned processed-range information, not only NTSTATUS.
- Treat trim as storage reclamation metadata, not as a secure data-erasure primitive.
References
- Microsoft WDK: FSCTL_FILE_LEVEL_TRIM
- Microsoft Open Specifications: FSCTL_FILE_LEVEL_TRIM reply
- Microsoft Open Specifications: NTSTATUS values
- Microsoft WDK: About FSCTLs
- Microsoft Open Specifications: File System Control Codes
Looking for a different code? Search another status or error code.