| Previous | Next |
| STATUS_INVALID_VIEW_SIZE | STATUS_ALREADY_COMMITTED |
STATUS_INVALID_FILE_FOR_SECTION
The backing file cannot support the requested section
Creating a file-backed section requires a valid file object whose type, access, size, and file-system behavior are compatible with the requested mapping. This status indicates that the memory manager could not read or use the necessary attributes. The failure can precede any actual view being mapped.
The important distinction is between an invalid or unsupported backing object and a bad virtual address. Reopening the same path with the same share mode will not help when the handle refers to a directory, special object, inaccessible file, truncated image, or file system that cannot provide the required mapping semantics.
What to inspect
- Record the file handle type, granted access, share mode, file size, attributes, and underlying file system.
- Confirm that the handle refers to a regular file and remains valid for the entire section-creation call.
- For SEC_IMAGE mappings, inspect the PE headers and ensure the complete image is readable.
- Check filter-driver and remote-file-system logs when attribute queries succeed outside the mapping path but fail here.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: CreateFileMapping
- Microsoft: ZwCreateSection
- Microsoft: PE and COFF format
Looking for a different code? Search another status or error code.