Fix STATUS_FILE_TOO_LARGE 0XC0000904 on Windows (5 Steps)

You tried to save a file and Windows threw STATUS_FILE_TOO_LARGE (0XC0000904). This usually happens when you're copying a movie, a virtual machine disk, or a large database backup. The error text says "The file size exceeds the limit allowed and cannot be saved."

Here's the thing: that limit is often not from the app you're using – it's from the file system on your drive. Let me explain the typical culprit.

If your drive is formatted as FAT32, the maximum file size is 4 GB minus one byte. Any file larger than that gets rejected instantly. This error also pops up when the destination is an old exFAT volume with a weird cluster size, or when you're saving to a network share with a file size cap set by the admin.

We'll fix this step by step. Start with the quick checks – you might be done in under a minute. If not, we'll move to converting the file system, which takes a bit longer.

Step 1: Check the Drive Format (30 seconds)

Right-click the drive where you're saving the file. Choose Properties. Look at the File system line.
If it says FAT32 – that's your problem. If it says NTFS or exFAT, then the issue is elsewhere (like an app-specific limit or a network policy).

Expected outcome: You'll see either FAT32, NTFS, or exFAT. If it's FAT32, proceed to Step 2. If it's NTFS or exFAT, jump to Step 4.

Step 2: Quick Workaround – Save to a Different Drive (1 minute)

This isn't a permanent fix, but it confirms the diagnosis. Try saving the file to your C: drive or any drive that's NTFS (usually your system drive).

• Open the app you're using.
• In the Save dialog, pick a folder on C: (like Documents).
• Give the file a name and click Save.

Expected outcome: The file saves without an error. That proves the issue is with the FAT32 drive, not the file itself.

Now you have two paths: convert the FAT32 drive to NTFS (Step 3) or split the file into smaller parts (skip to Step 5). Converting is cleaner if you want to keep using that drive for large files.

Step 3: Convert FAT32 to NTFS (5 minutes)

You can convert a FAT32 drive to NTFS without losing data. Windows has a built-in command for this. But first, back up any important files – this is risky, and I've seen it fail on drives with bad sectors.

Here's how:

1. Close all programs and make sure nothing is using the drive.
2. Open Command Prompt as Administrator. Press Win, type cmd, right-click Command Prompt, and select Run as administrator.
3. Type the following command, but replace E: with your drive letter:

convert E: /fs:ntfs

Press Enter. Windows might ask to dismount the drive. Type Y and hit Enter.

Expected outcome: You'll see a message like "Conversion complete" and the drive's format becomes NTFS. Now try saving your large file again.

What if it fails? If you get an error saying the drive is in use, close everything and try again. If it complains about insufficient space, you need to free up some room – NTFS needs a bit of space for the conversion.

Step 4: Check for App-Specific or Network Limits (10 minutes)

If the drive is already NTFS or exFAT, then the file system isn't the issue. Let's look at other places.

• App limit: Some apps have their own max file size. For example, older FAT32-formatted SD cards in cameras still cause this even when the card is exFAT. Check your app's settings for any file size limits.
• Network share: If you're saving to a network location, the server might have a quota or a file size cap. Contact your network admin, or try saving locally to test.
• Registry policy: On Windows Server, there's a policy that sets a max file size for certain services. But on a normal PC, this is rare. Still, you can check:

1. Press Win + R, type regedit, and hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters.
3. Look for FileSizeLimitInBytes. If it exists, double-click it and change the value to 4294967295 (about 4 GB) or higher.

Expected outcome: If the registry value was set to a low number, changing it and restarting the WebClient service might fix the error. But honestly, only do this if you know what you're doing.

Step 5: Split the File into Smaller Parts (15+ minutes, but worth it)

This is the practical workaround if you can't convert the drive (for example, it's an SD card that you need to keep as FAT32 for a camera or console).

Use a file splitter tool like 7-Zip (free) to split the large file into chunks under 4 GB.

1. Download and install 7-Zip from 7-zip.org.
2. Right-click your large file, select 7-Zip > Add to archive.
3. In the Split to volumes, bytes field, enter 4000M (that's about 3.9 GB).
4. Click OK. It will create multiple files like file.7z.001, file.7z.002, etc.
5. Copy those to the FAT32 drive. To get the original file back, right-click the first part and choose Extract here on any NTFS drive.

Expected outcome: The split parts copy without errors. You lose the convenience of a single file, but you gain the ability to use that drive.

When to Skip the Fixes and Just Reformat

If the drive is a USB stick or SD card you only use on Windows, and converting fails repeatedly, just back up everything and reformat to NTFS.

1. Copy all files off the drive.
2. Right-click the drive in File Explorer, choose Format.
3. Set File system to NTFS (or exFAT if you need compatibility with Macs, but exFAT has its own quirks).
4. Click Start.

That wipes the drive, so only do this if you're prepared to lose the data or have it backed up.

The Real Takeaway

Most of the time, 0XC0000904 comes down to a FAT32 drive. Convert it to NTFS, and you're done. If you can't convert, split the file. The error is annoying, but it's not a sign of a dying drive – it's just Windows doing its job by saying "I can't write that here."

If none of these steps work, then the problem is likely inside the application you're using. Check the app's forums or try a different version of the app. But I'd bet my left arm that the drive format is the culprit.