| Previous | Next |
| ERROR_SUBST_TO_JOIN | ERROR_SAME_DRIVE |
ERROR_BUSY_DRIVE
What ERROR_BUSY_DRIVE means
ERROR_BUSY_DRIVE is a Win32 system result whose documented message is: “The system cannot perform a JOIN or SUBST at this time.” In practical troubleshooting, it belongs to legacy JOIN or SUBST operations attempted while the selected drive is active or cannot safely change namespace mapping.
Typical causes
- a process has its current directory on the drive
- open files or searches are using paths through the mapping
- another mapping change is in progress
How to investigate the result
- find processes whose current directory or open handles reference the drive
- stop directory watchers and shells using the path
- serialize mapping changes and retry once the drive becomes idle
Developer guidance
Coordinate namespace changes with users of the path and reject new work before removing or replacing a mapping.
Administrator and support guidance
Close command prompts, Explorer windows, and applications rooted on the drive. Avoid changing shared mappings during active jobs.
Example
A script tries to remove a SUBST drive while a command prompt has that drive as its current directory, producing this result.
How it differs from related results
ERROR_DRIVE_LOCKED generally concerns exclusive access to a physical volume; this result is tied to legacy JOIN/SUBST state changes.
References
Looking for a different code? Search another status or error code.