| Previous | Next |
| STATUS_SECTION_NOT_EXTENDED | STATUS_RESOURCE_DATA_NOT_FOUND |
STATUS_NOT_MAPPED_DATA
The mapping does not represent flushable file data
Image sections, page-file-backed sections, physical mappings, and other specialized section types do not have the same persistence semantics as an ordinary mapped data file. A flush request that assumes file-backed data can therefore be rejected even though the virtual address is mapped.
Determine what created the section before selecting a flush mechanism. FlushViewOfFile initiates writeback for dirty mapped-file pages but does not by itself guarantee that file metadata is durably written; callers requiring durability may also need the documented file-handle flush sequence.
What to inspect
- Use VirtualQuery and section creation records to identify whether the view is image, mapped data, or private.
- Confirm the range belongs to the expected mapped file and is writable under that mapping.
- For durability requirements, follow the documented view and file flush sequence rather than retrying a native section flush.
References
- Microsoft: File mapping
- Microsoft: FlushViewOfFile
- Microsoft: VirtualQuery
- ReactOS source: section objects and mapped views
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.