| Previous | Next |
| STATUS_BAD_FILE_TYPE | STATUS_FORMS_AUTH_REQUIRED |
STATUS_FILE_TOO_LARGE
The active storage path enforces a file-size limit
STATUS_FILE_TOO_LARGE should not be translated into “the disk is full”. The file itself exceeds a limit imposed by some layer of the active path. Windows file systems have different maximum file sizes, and remote providers or redirectors can impose much smaller policy or implementation limits.
This distinction is especially important for WebDAV-style mapped locations. Microsoft documents a FileSizeLimitInBytes setting for the WebClient redirector in troubleshooting guidance, while the Windows file-system comparison shows that local FAT32 has a 4 GiB maximum file size and NTFS/ReFS use different limits. Measure the failing file and identify the provider before changing storage.
Do not split or recompress the file until you know which boundary rejected it. A local file-system limit, a WebDAV client limit and a server upload policy have different remedies and may fail at different phases of the same copy.
What to inspect
- The exact file size at failure and the file system or redirector serving the destination.
- Whether the status occurs on local create/extend, WebDAV transfer, or server commit.
- Documented client and server limits, including configured upload or WebClient caps.
References
- Microsoft: File System Functionality Comparison
- Microsoft: WebDAV folder limits and FileSizeLimitInBytes
- Microsoft: NTFS overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.