| Previous | Next |
| ERROR_BUSY_DRIVE | ERROR_DIR_NOT_ROOT |
ERROR_SAME_DRIVE
What ERROR_SAME_DRIVE means
ERROR_SAME_DRIVE is a Win32 system result whose documented message is: “The system cannot join or substitute a drive to or for a directory on the same drive.” In practical troubleshooting, it belongs to legacy JOIN or SUBST validation that rejects mapping a drive to a directory located on that same drive. For ERROR_SAME_DRIVE, the numeric result identifies the failed contract, while the operation and target object explain why this particular result appeared.
Typical causes
- the target path resolves back to the source drive
- an environment variable changed and created a self-reference
- path normalization exposed a same-volume mapping that string comparison missed
How to investigate ERROR_SAME_DRIVE
- resolve source and target to volume identifiers, not only drive letters
- expand environment variables and symbolic components
- check for self-referential or circular configuration
When investigating ERROR_SAME_DRIVE, start with the first failing call rather than a later cleanup error. Preserve the raw ERROR_SAME_DRIVE result before any wrapper converts it. Record whether ERROR_SAME_DRIVE is reproducible in a clean process, a new user session, or after the relevant object is recreated.
Developer guidance
Validate mappings after canonical resolution and prohibit self-reference before issuing the operating-system command. For ERROR_SAME_DRIVE, logs should include the operation name, canonical target, process architecture, operating-system build, and the state that was validated immediately before the call. For ERROR_SAME_DRIVE, avoid blind retries while the same precondition remains unchanged.
Administrator and support guidance
Correct the target to a directory on a different drive or remove the unnecessary mapping. Do not try to bypass this guard. Before restarting after ERROR_SAME_DRIVE, collect evidence because a restart may clear the state responsible for this result. When a ERROR_SAME_DRIVE workaround succeeds, record exactly which process, mapping, media, driver, or configuration value changed.
Example incident
A configuration expands the target for drive D: to D:\LegacyRoot, so the attempted mapping fails with ERROR_SAME_DRIVE. A useful ERROR_SAME_DRIVE incident timeline shows the successful setup steps, the first operation returning ERROR_SAME_DRIVE, and any secondary errors produced during its rollback.
How it differs from related results
ERROR_SAME_DRIVE prevents a direct self-mapping, while JOIN_TO_JOIN and related codes reject more complex chained topologies. For ERROR_SAME_DRIVE, that distinction determines whether the remedy belongs in application input, resource release, mapping topology, driver compatibility, or underlying storage.
Evidence worth collecting
For this result, capture evidence around the condition “the target path resolves back to the source drive.” The ERROR_SAME_DRIVE evidence package should include the exact API or command, all non-secret input fields, normalized paths or device names, object ownership, and a timestamp correlatable with Windows Event Log and application tracing. The first concrete ERROR_SAME_DRIVE check should be to resolve source and target to volume identifiers, not only drive letters.
Recovery and verification
Recovery from ERROR_SAME_DRIVE is complete only when the original operation succeeds under the same relevant conditions. After fixing ERROR_SAME_DRIVE, repeat the action and verify that no stale mapping or handle remains. Run the operation a second time to confirm that the setup and cleanup associated with ERROR_SAME_DRIVE are idempotent. If ERROR_SAME_DRIVE disappears only after reboot, continue investigating the owner or leaked state rather than treating reboot as the permanent correction.
When to escalate
Escalate ERROR_SAME_DRIVE with a minimal reproduction, the exact ERROR_SAME_DRIVE value, application and component versions, target path or device class, and the collected state before and after this failure. For a legacy ERROR_SAME_DRIVE case, also state whether the executable is 16-bit, DOS-derived, virtualized, redirected, or running under a compatibility subsystem.
References
Looking for a different code? Search another status or error code.