| Previous | Next |
| ERROR_NO_RANGES_PROCESSED | ERROR_DISK_RESOURCES_EXHAUSTED |
ERROR_NOT_ALLOWED_ON_SYSTEM_FILE
The target is a file-system internal file
ERROR_NOT_ALLOWED_ON_SYSTEM_FILE means the file system rejected an operation because the target is one of its internal files. This is not the same as the ordinary DOS/Win32 FILE_ATTRIBUTE_SYSTEM flag and is not repaired by making protected files visible in File Explorer.
What to verify
- Record the exact volume, file identifier/path if one is exposed, API or FSCTL, and operation that returned the error.
- Determine whether the request came from backup, defragmentation, volume-management, filter-driver, or other low-level code that can encounter file-system metadata objects.
- Keep the file-system type and volume state with the trace; internal-file rules are part of the file system's consistency contract.
Correct handling
Skip or handle the internal object according to the documented API contract. Do not change hidden/system attributes, take ownership, or force ordinary file operations against metadata that the file system intentionally protects.
If an application unexpectedly selected an internal file, fix its enumeration or filtering logic and repeat the original operation on supported user data. If a storage tool is expected to work at this level, diagnose the specific documented interface it should use instead.
Official references
Looking for a different code? Search another status or error code.