| Previous | Next |
| ERROR_NOT_SUBSTED | ERROR_SUBST_TO_SUBST |
ERROR_JOIN_TO_JOIN
What ERROR_JOIN_TO_JOIN means
ERROR_JOIN_TO_JOIN is a Win32 system result whose documented message is: “The system tried to join a drive to a directory on a joined drive.” In practical troubleshooting, it belongs to invalid legacy mapping topology where a drive is being joined to a directory located on another joined drive. The numeric result identifies the failed contract, while the operation and target object explain why this particular result appeared.
Typical causes
- mapping scripts chain JOIN relationships
- a destination path was resolved through an existing JOIN unknowingly
- configuration was copied from a different drive layout
How to investigate the result
- expand both source and target to their underlying volumes
- draw the current JOIN topology and detect chains or cycles
- remove intermediate mappings in a controlled test
When investigating this result, start with the first failing call rather than a later cleanup error. Preserve the raw it before any wrapper converts it. Record whether it is reproducible in a clean process, a new user session, or after the relevant object is recreated.
Developer guidance
Keep JOIN relationships flat. Resolve destinations to ordinary directories on non-joined drives before creating a mapping. Logs should include the operation name, canonical target, process architecture, operating-system build, and the state that was validated immediately before the call. Avoid blind retries while the same precondition remains unchanged.
Administrator and support guidance
Simplify legacy mappings one at a time and preserve the original configuration for rollback. Modernize to volume mount points where practical. Before restarting after this result, collect evidence because a restart may clear the state responsible for it. When a it workaround succeeds, record exactly which process, mapping, media, driver, or configuration value changed.
Example incident
Drive D: is already joined elsewhere, and a script tries to JOIN E: to a directory reached through D:, resulting in this result. A useful incident timeline shows the successful setup steps, the first operation returning it, and any secondary errors produced during its rollback.
How it differs from related results
This code rejects JOIN-to-JOIN chaining specifically; ERROR_IS_JOINED only says one drive already has a JOIN relation. That distinction determines whether the remedy belongs in application input, resource release, mapping topology, driver compatibility, or underlying storage.
Evidence worth collecting
Capture evidence around the condition “mapping scripts chain JOIN relationships.” The result 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 it check should be to expand both source and target to their underlying volumes.
Recovery and verification
Recovery from it is complete only when the original operation succeeds under the same relevant conditions. After fixing it, 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 it are idempotent. If it disappears only after reboot, continue investigating the owner or leaked state rather than treating reboot as the permanent correction.
When to escalate
Escalate it with a minimal reproduction, the exact it value, application and component versions, target path or device class, and the collected state before and after this failure. For a legacy the 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.