Windows error 17 (ERROR_NOT_SAME_DEVICE): meaning and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The source and destination are on different volumes, so a direct rename cannot complete the move.

Could be also:
Constant	Type	OS
KERN_INVALID_RIGHT	Kern return	Mac
ippStsUnderflow	Intel Ipp Status	Any
EEXIST	errno	Any
THREAD_NOT_MUTEX_OWNER	BugCheck Code	Windows

Previous	Next
ERROR_CURRENT_DIRECTORY	ERROR_NO_MORE_FILES

ERROR_NOT_SAME_DEVICE

A cross-volume operation requires a copy instead of a rename

ERROR_NOT_SAME_DEVICE commonly occurs when a rename or move is implemented by a filesystem operation that only works within one volume. The source and destination paths resolve to different devices or mounted filesystems.

Correct handling

Resolve both paths to their actual volumes.
Use copy-then-delete semantics when crossing volumes is allowed.
Preserve metadata and verify the copied content before deleting the source.
Account for partial failure and available destination space.

Important distinction

A same-volume rename is usually atomic; a cross-volume copy is not. Applications should not claim atomic replacement when falling back to copy and delete.

References

Looking for a different code? Search another status or error code.