| Previous | Next |
| STATUS_PROFILING_AT_LIMIT | STATUS_FILE_RENAMED |
STATUS_NOT_SAME_DEVICE
A cross-volume move is not a rename in the Windows file model
STATUS_NOT_SAME_DEVICE is a precise rename constraint. Microsoft documents FILE_RENAME_INFORMATION with the rule that a file or directory can only be renamed within a volume; a rename cannot move the object to a different volume. Minifilter documentation for FltSetInformationFile repeats the same restriction.
Changing permissions does not make a cross-volume rename legal. NtSetInformationFile also documents access requirements for rename operations, but satisfying those requirements only authorizes a rename that is otherwise valid. If source and destination resolve to different volumes, the application needs move semantics implemented as copy to the destination, validation and metadata handling, followed by source deletion when the copy is complete.
Check real volume identity rather than comparing drive-letter text. Mount points, reparse-based layouts, shares, or redirected paths can make two names look related while resolving to different devices. For a network protocol implementation, preserve the server-side volume/device result used by the rename request instead of guessing from the client path string.
What to inspect
- Resolved source and destination volume or device identities at the point of the rename request.
- The information class and rename structure submitted to the file system.
- Whether the application’s “move” code has a separate cross-volume copy-and-delete path with failure-safe cleanup.
References
- Microsoft: FILE_RENAME_INFORMATION
- Microsoft: FltSetInformationFile
- Microsoft: NtSetInformationFile
- Microsoft Open Specifications: FileRenameInformation
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.