ERROR_WAS_UNLOCKED - 715 (0x2CB)
{Page Unlocked} The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process.
Updated: Feb 21, 2026
Technical Meaning
The error code ERROR_WAS_UNLOCKED indicates that a previously locked memory page has been unlocked and its protection settings have been changed to 'No Access'. This operation involves the removal of the page from both physical memory and the process's virtual address space.
Error Details
- Error Name: ERROR_WAS_UNLOCKED
- Numeric Code: 715 (0x2CB)
- Short Description: {Page Unlocked} The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process.
Usage Context
This error code is typically encountered in scenarios where memory management operations are performed, such as when pages are allocated or deallocated within a process. It may also be relevant during debugging sessions where memory state changes need to be monitored.
Developer Interpretation
Developers should interpret this error code as an indication that a specific memory page has been unlocked and its protection settings have been altered. This can occur due to various operations, such as freeing the page or changing its access permissions. The exact context in which this error is generated depends on the underlying system calls or APIs being used.
Related Errors
- ERROR_PAGEFILE_QUOTA_EXCEEDED (704): Occurs when a process attempts to allocate more memory than allowed by the pagefile quota.
- ERROR_COMMITMENT_LIMIT: Indicates that the system is unable to commit enough virtual address space for the requested operation due to resource constraints.
- ERROR_INVALID_PARAMETER: May be encountered if an invalid parameter was passed during a memory management operation, leading to unexpected behavior or state changes.
FAQ
Q: What does ERROR_WAS_UNLOCKED mean?
A: It indicates that a locked page of memory has been unlocked and its protection settings have been changed to 'No Access'.
Q: When would this error be generated?
A: This error is typically generated during memory management operations, such as freeing or reconfiguring pages.
Summary
ERROR_WAS_UNLOCKED (715) is a specific error code indicating that a locked page of memory has been unlocked and its protection settings have been changed. Developers should be aware of this error when dealing with memory management operations to ensure proper handling of memory states.