If you're staring at “ERROR_FILE_SYSTEM_LIMITATION (0x00000299)”, I get it — that’s a frustrating wall to hit. Let’s get you past it fast. I’ve seen this on everything from Windows 10 to Server 2019, and it usually boils down to one of three things: a file that’s too big, a path that’s too deep, or a screwed-up NTFS metadata table.
The Quick Fix (works 80% of the time)
First thing — check the file size. NTFS has a theoretical max of 256 TB per file, but real-world limits hit way before that, especially on older drives or drives formatted with small cluster sizes. If you’re copying a file over 4 GB to a FAT32 drive, that’s your problem — NTFS throws this error when it can’t reconcile the allocation table. But most people aren’t on FAT32 anymore.
If the file is under 4 GB and you’re on NTFS, the next culprit is the path length. Windows has a 260-character path limit by default, and some apps (looking at you, Adobe) create nested folders that blast past that. Try this:
- Move the file to the root of the drive (like C:\temp).
- Rename it to something short, like “test.file”.
- Retry the operation.
If that works, you’ve got a path-length problem. Enable long paths in Windows via Group Policy or registry:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /fReboot. Had a client last month whose entire print queue died because of this — the spooler was trying to write to a path that was 290 characters deep. Took me 10 minutes to fix once I stopped chasing ghost drivers.
If That Doesn’t Work: Check NTFS Health
This error also pops up when the Master File Table (MFT) gets corrupted — not full disk corruption, just enough to confuse the file system. Run this from an elevated command prompt:
chkdsk C: /f /rReplace C: with your drive letter. This checks for bad sectors and fixes logical errors. On a modern SSD, /r isn’t as useful, but /f is mandatory. I’ve seen chkdsk clear this error on machines that had a sudden power loss during a big file transfer.
Still stuck? Try fsutil repair. This is a deeper NTFS repair tool that chkdsk doesn’t always trigger:
fsutil repair query C:
fsutil repair state C:
fsutil repair initiate C:
The “initiate” command tells the OS to do a self-heal on the file system. It’s usually fast and doesn’t need a reboot. Ran this on a Server 2016 box that had 0x00000299 every time it tried to sync a 200 MB SQL backup — fixed it instantly.
Less Common Variations
Sometimes this error isn’t about files at all — it’s about volume-level locks. If you’re trying to do a Volume Shadow Copy (VSS) snapshot and the system can’t allocate space for the diff area, you’ll get 0x00000299. Check your VSS storage:
vssadmin list shadowstorageIf the “Used Shadow Copy Storage Space” is maxed out, delete old shadows or resize the storage area. I had a client whose backup software kept failing with this exact error — turned out they had 40 GB of shadows on a 100 GB drive. Freed up space, problem gone.
Another edge case: USB drives formatted with exFAT. exFAT has a 16 EB file size limit, but some older controllers report back to Windows with a bogus limit. If you get this error on a USB drive, reformat it as NTFS (if you don’t need cross-platform compatibility) or update the drive’s firmware.
Prevention
Stop this from coming back by keeping your file system clean:
- Use short folder names — no more than 3 levels deep for files you access often.
- Enable long paths globally (the reg key above) if you work with deep project structures.
- Run chkdsk once a month on drives that see heavy write activity.
- Monitor VSS storage — set a cap so it doesn’t eat your whole drive.
That’s it. Skip the forums that tell you to reinstall Windows or replace your drive — 99% of the time, it’s just the file system being stupid, not broken. You’re welcome.