| Previous | Next |
| ERROR_SEGMENT_NOTIFICATION | ERROR_FT_READ_RECOVERY_FROM_BACKUP |
ERROR_BAD_CURRENT_DIRECTORY
What ERROR_BAD_CURRENT_DIRECTORY means
The process could not switch to its configured startup current directory. In practical terms, this status belongs to process startup and working directories: the recorded current directory is missing, unavailable, disconnected, or inaccessible when the process starts.
Typical causes
- A network drive or removable volume is unavailable
- The directory was deleted or permissions changed
- A shortcut or launcher contains an obsolete Start in path
How to investigate
- Log the requested directory and fallback directory
- Test access under the actual user and service account
- Check mapped-drive visibility across sessions and elevation boundaries
Developer guidance
Prefer absolute paths for resources and do not make correctness depend on the inherited current directory. Services should use stable local paths rather than interactive drive mappings.
Operational interpretation
When ERROR_BAD_CURRENT_DIRECTORY appears, first determine whether the operation actually failed, completed with an informational condition, or transferred work to another component. Record the API name, returned value, affected process or object, and the immediately preceding event. For this code, the most useful boundary is the process startup and working directories boundary; broad machine-wide remediation before that boundary is identified can hide the original evidence.
Example scenario
An incident begins when a network drive or removable volume is unavailable. A responder investigating this result should not begin with a generic reboot that destroys the original context. A better first step is to log the requested directory and fallback directory. That evidence connects it to its producing operation and reveals whether this particular result is repeatable, expected, or merely secondary.
Logging and telemetry
Telemetry for this Win32 error should preserve its numeric value, component version, process and thread identifiers, operation name, affected object or endpoint, elapsed time, and the first earlier failure in the same activity. Keep the result correlation identifier stable across callbacks so the status can be joined to the request that initiated this exact operation.
Recovery and validation
Apply recovery only after the responsible state has demonstrably changed. After changing that state, repeat one controlled this result scenario and verify both the returned status and the resulting system state. Absence of another log line is not sufficient: confirm that the intended process startup and working directories action completed, that no resource remains pending, and that later cleanup does not produce a different secondary error.
References
Looking for a different code? Search another status or error code.