| 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.
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
Developer guidance
Cleanup should tolerate “already absent” when that matches the desired final state, while still logging unexpected ownership or target mismatches.
Administrator and support guidance
Inspect scripts for unconditional delete commands. This result is usually a state-management issue rather than a disk failure.
Example
An installer rollback removes a JOIN twice. The first succeeds and the second returns this result.
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.
References
Looking for a different code? Search another status or error code.