Fix ERROR_EA_TABLE_FULL (0X00000115) in Windows

Quick Answer

Run fsutil repair query C: and chkdsk C: /f in an admin Command Prompt, then reboot. That clears the EA table.

Why This Happens

Windows uses extended attributes (EAs) to store metadata like file tags, encryption info, and some app-specific data. The EA table is a hidden file on NTFS drives, and it has a fixed size limit. When you’ve got too many files with EAs—common on heavily used servers or drives with lots of cloud-synced folders—that table fills up. The OS throws error 0X00000115 and won’t let you write new attributes.

You’ll see this most often on Windows Server 2016/2019, but I’ve seen it on Windows 10 Pro too, specifically when using OneDrive with a ton of shared files. The trigger? Just trying to modify a file’s properties or sync a large folder.

Step-by-Step Fix

Step 1: Check the drive letter

Open File Explorer and note which drive is causing the error. In my examples, I’ll use C:. Replace it with your drive letter.

Step 2: Open Command Prompt as admin

Press the Windows key, type cmd, right-click Command Prompt, and choose “Run as administrator.” Click Yes when UAC asks.

Step 3: Query the EA table status

Run this command:

fsutil repair query C:

You’ll see something like Repair: Self-healing is enabled and a State number. If the state is 0, you’re good. If it’s something like 0x115 or 0x10, the table is full or corrupted.

Step 4: Initiate a repair

Run this to clear the EA table:

fsutil repair initiate C: 0x00000115

Wait a few seconds. The command returns immediately, but the repair runs in the background. You should see Repair operation initiated.

Step 5: Run chkdsk to fix remaining issues

Now run the built-in disk checker:

chkdsk C: /f

It’ll say “Chkdsk cannot run because the volume is in use. Would you like to schedule this volume to be checked the next time the system restarts?” Type Y and press Enter.

Step 6: Reboot

Restart your PC. During boot, chkdsk will run and repair the EA table. After Windows loads, the error should be gone. Test by opening the folder or file that triggered it.

If the Error Still Happens

Try these in order:

• Disable and re-enable the drive’s indexing: Right-click the drive in File Explorer, go to Properties, uncheck “Allow files on this drive to have contents indexed,” click Apply, choose “Apply changes to drive X: subfolders and files,” wait for the changes to apply, then recheck the box and apply again. This rebuilds the EA table.
• Use PowerShell to remove EAs on specific files: Open PowerShell as admin, run Get-ChildItem -Path C:\YourFolder -Recurse -File | ForEach-Object { Set-ItemProperty -Path $_.FullName -Name Attributes -Value (Get-ItemProperty -Path $_.FullName).Attributes -Force }. Replace C:\YourFolder with the problem folder. This strips EAs from every file.
• Check for third-party software: Antivirus or backup tools that add custom EAs can fill the table fast. Temporarily disable them and test.
• Format the drive: Only if it’s not your system drive and you can back up data. A format clears everything, including the EA table. Then restore your data.

How to Prevent It

The EA table has a hard limit. You can’t expand it. But you can avoid hitting the wall:

• Don’t use cloud-sync folders (OneDrive, Dropbox) on the same drive as heavy server workloads. Keep them separate.
• Regularly run chkdsk /f on volumes that get lots of file changes—once a month for busy drives.
• Monitor your EA table usage with fsutil repair query. If the state number starts climbing above 0, you’re getting close to full.

That’s it. This error is rare, but when it hits, it stops you cold. These steps have fixed it for everyone I’ve helped.