| Previous | Next |
| ERROR_IS_SUBSTED | ERROR_NOT_SUBSTED |
ERROR_NOT_JOINED
What ERROR_NOT_JOINED means
ERROR_NOT_JOINED is a Win32 system result whose documented message is: “The system tried to delete the JOIN of a drive that is not joined.” In practical troubleshooting, it belongs to removal of a legacy JOIN mapping when the specified drive is not currently joined. The numeric result identifies the failed contract, while the operation and target object explain why this particular result appeared.
Typical causes
- cleanup runs after another component already removed the mapping
- the delete command targets the wrong drive letter
- the create step failed but unconditional rollback still attempted deletion
How to investigate the result
- enumerate mapping state immediately before cleanup
- correlate the delete with the earlier create result
- verify drive-letter normalization and session context
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
Cleanup should tolerate “already absent” when that matches the desired final state, while still logging unexpected ownership or target mismatches. 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
Inspect scripts for unconditional delete commands. This result is usually a state-management issue rather than a disk failure. Before restarting after it, 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
An installer rollback removes a JOIN twice. The first succeeds and the second returns 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
It is the inverse state check for JOIN; it should not be confused with network join or domain membership errors. 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 “cleanup runs after another component already removed the mapping.” 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 enumerate mapping state immediately before cleanup.
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.