ERROR_SECURITY_STREAM_IS_INCONSISTENT - 306 (0x132)
The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume.
Updated: Feb 21, 2026
Technical Meaning
The ERROR_SECURITY_STREAM_IS_INCONSISTENT error indicates that the security stream associated with a given volume is in an inconsistent state. This typically suggests that there may be corruption or issues within the security descriptors of files or directories on the volume.
Error Details
This error code, 306 (0x132), is returned by the Windows operating system when it detects inconsistencies in the security stream of a file system. The security stream contains information about the access control lists (ACLs) and ownership for files and directories on the volume.
Usage Context
This error can occur during various operations that involve accessing or modifying files and directories, particularly those involving security descriptors. It is important to note that this error does not necessarily indicate a critical failure but may require attention to ensure data integrity and system security.
Developer Interpretation
When encountering ERROR_SECURITY_STREAM_IS_INCONSISTENT, developers should interpret it as an indication that the file system's metadata, specifically the security stream, is in an inconsistent state. This could be due to a variety of reasons such as corruption during write operations or issues with the file system itself.
Related Errors
ERROR_FILE_SYSTEM_CORRUPTION(0x52)ERROR_INVALID_PARAMETER(0x57)ERROR_ACCESS_DENIED(0x5)
FAQ
Q: What does ERROR_SECURITY_STREAM_IS_INCONSISTENT mean?
A: It indicates that the security stream for a given volume is in an inconsistent state, suggesting potential corruption or issues with file system metadata.
Q: How can I resolve this error?
A: Running chkdsk on the affected volume may help to identify and correct any inconsistencies. Ensure that the volume is not in use before running chkdsk.
Summary
The ERROR_SECURITY_STREAM_IS_INCONSISTENT (306) error indicates an inconsistency in the security stream of a file system, which can be addressed by running chkdsk. Developers should interpret this as a potential issue with file system metadata and take appropriate action to ensure data integrity.