| Previous | Next |
| STATUS_CHECKOUT_REQUIRED | STATUS_FILE_TOO_LARGE |
STATUS_BAD_FILE_TYPE
The storage service rejected the file type by policy
STATUS_BAD_FILE_TYPE is not a PE loader-format error. This status belongs to a content-policy decision rather than executable image loading or PE validation. Document and remote-authoring systems can reject selected extensions or classes of content even when the caller otherwise has permission to create or read objects in the target location.
Record the complete filename, extension after normalization, and the server or redirector involved. Policy checks can occur on upload, synchronization or retrieval, and a renamed extension is not a safe or valid workaround: the service may inspect the real object type, and bypassing a security policy can create a larger incident.
SharePoint documentation, for example, exposes blocked file-type controls for synchronization and earlier server versions expose blocked extension lists. Treat those as examples of provider policy; the NTSTATUS by itself does not name SharePoint. The correct remediation is to identify the rejecting provider and its configured rule.
What to inspect
- The exact extension and content type of the file after client-side normalization.
- The service that returned the status and its blocked-file or upload policy.
- Whether the block occurred during save, sync or retrieval, which identifies the enforcement layer.
References
- Microsoft: Block syncing of specific file types in SharePoint
- Microsoft: Add blocked file types in SharePoint
- Microsoft: Using the WebDAV Redirector
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.