| Previous | Next |
| STATUS_BAD_WORKING_SET_LIMIT | STATUS_SECTION_PROTECTION |
STATUS_INCOMPATIBLE_FILE_MAP
The file already has a section with conflicting mapping attributes
Windows can maintain shared section state for a file, but image, data, protection, size, and caching expectations must be compatible. Creating another section with conflicting attributes can be rejected even when the file handle itself is valid. This protects coherence between views of the same underlying file.
Identify every component mapping the file, including image loader and cache paths. Closing only the new handle does not change an existing section still referenced by another process or kernel component. Avoid changing file size or mapping mode while incompatible views remain active.
What to inspect
- Record file identity, section type, maximum size, protection, and cache attributes.
- Find existing image or data-section mappings in all participating processes.
- Coordinate truncation, replacement, and remapping only after old views and section handles are closed.
References
- Microsoft: File mapping
- Microsoft: MapViewOfFile
- ReactOS source: section objects and mapped views
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.