ERROR_BUSY - 170 (0xAA)
The requested resource is in use.
Updated: Feb 21, 2026
Technical Meaning
The ERROR_BUSY error code indicates that a requested resource or operation is currently in use by another process or component. This can occur when attempting to access, modify, or delete a file, directory, or other system resource.
Error Details
- Error Name: ERROR_BUSY
- Numeric Code: 170 (0xAA)
- Short Description: The requested resource is currently in use.
Usage Context
This error can be encountered in various scenarios where a process attempts to access or modify a resource that is already occupied by another process. Common contexts include file operations, directory management, and system resource manipulation.
Developer Interpretation
When the ERROR_BUSY code is returned, it signifies that the operation cannot proceed because the target resource is currently in use. Developers should handle this error gracefully, typically by retrying the operation after a brief delay or informing the user of the current state of the resource.
Related Errors
- ERROR_SHARING_VIOLATION (32): Similar to
ERROR_BUSY, but may indicate that the file is in use and cannot be opened for read/write operations. - ERROR_FILE_NOT_FOUND (2): Indicates that the requested resource does not exist, which might lead developers to mistakenly attempt an operation on a non-existent resource.
FAQ
Q: Can this error occur with files or directories?
A: Yes, ERROR_BUSY can be returned when attempting to access or modify a file or directory that is currently in use by another process.
Q: Is there any way to determine which process is using the resource?
A: No, the operating system does not provide specific information about which processes are using the resource. Developers must handle this error based on the context and retry logic.
Summary
The ERROR_BUSY code indicates that a requested operation cannot proceed because the target resource is currently in use by another process or component. This error is generic and can occur in various scenarios, such as file operations or directory management. Developers should handle this error gracefully to ensure robust application behavior.