| Previous | Next |
| STATUS_DELETE_PENDING | STATUS_UNKNOWN_REVISION |
STATUS_CTL_FILE_NOT_SUPPORTED
The failure is tied to destination file-system capability
STATUS_CTL_FILE_NOT_SUPPORTED reports an attempt to set a control attribute that the destination file system does not support. The destination qualifier is important: the same operation can be meaningful on one file system and unavailable on another. It is not automatically a malformed path or a bad file handle.
Windows file-system control operations are issued as FSCTLs and can set or query metadata associated with a file or file system. Microsoft also documents that file systems differ in supported functionality. Before changing the request, identify the destination volume and query its file-system name and capability flags. A copied file may land on NTFS, ReFS, FAT, a network redirector, or another implementation with different metadata support.
Capture the exact FSCTL or information-setting operation and the original native status. If an application silently falls back by omitting the attribute, verify that the attribute is optional; dropping control metadata can change later behavior. Retrying the identical request on the same destination does not add support. The useful comparison is the successful source/destination file-system pair versus the failing one.
What to inspect
- Log the FSCTL or set-information operation, not just the file path.
- Query the destination file-system name and capability flags.
- Use fallback behavior only when the metadata is explicitly optional.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft WDK: About FSCTLs
- Microsoft WDK: NtFsControlFile
- Microsoft: GetVolumeInformation
- Microsoft: File-system functionality comparison
Looking for a different code? Search another status or error code.