ERROR_ATOMIC_LOCKS_NOT_SUPPORTED - 174 (0xAE)
The file system does not support atomic changes to the lock type.
Updated: Feb 21, 2026
Technical Meaning
The ERROR_ATOMIC_LOCKS_NOT_SUPPORTED error indicates that the file system in use does not support atomic changes to lock types. This means that operations attempting to change a lock from one type to another cannot be performed atomically, leading to potential race conditions or inconsistent states.
Error Details
This error is typically encountered when an application attempts to perform an operation that requires changing the type of a file system lock in a manner that is not supported by the underlying file system. For example, attempting to convert a shared lock into an exclusive lock atomically might fail if the file system does not support such operations.
Usage Context
This error can occur in various scenarios where file locking mechanisms are used, such as when applications need to ensure data integrity during concurrent access or when implementing complex file synchronization logic. It is important for developers to understand that this error indicates a limitation of the file system and may require alternative approaches to achieve desired functionality.
Developer Interpretation
When encountering ERROR_ATOMIC_LOCKS_NOT_SUPPORTED, it is crucial to review the specific operation being performed and ensure compatibility with the file system in use. Developers should consider using alternative locking mechanisms or rearchitecting their code to avoid operations that are not supported by the underlying file system.
Related Errors
FAQ
Q: What does ERROR_ATOMIC_LOCKS_NOT_SUPPORTED mean?
A: This error indicates that the file system in use does not support atomic changes to lock types.
Q: How can I handle this error in my application?
A: Review your locking operations and ensure they are compatible with the file system. Consider using alternative mechanisms or rearchitecting code to avoid unsupported operations.
Summary
ERROR_ATOMIC_LOCKS_NOT_SUPPORTED is a specific error indicating that atomic changes to lock types are not supported by the current file system. Developers should be aware of this limitation and adjust their application logic accordingly to ensure proper operation.