STATUS_EA_CORRUPT_ERROR (0xC0000053) Fix – EA Is Corrupt

Cause #1: File system corruption on the drive

This is the most common reason you see STATUS_EA_CORRUPT_ERROR (0xC0000053). Extended Attributes (EA) are hidden metadata attached to files on NTFS drives—things like security descriptors, file tags, or custom app data. When the file system gets a bad sector, an unexpected shutdown, or a failing disk, that EA data can become unreadable.

In my experience, this error pops up most often when you’re copying a large batch of files from one drive to another, or right after a system crash. The error message itself says “The EA is corrupt and cannot be read,” which is Windows’ way of telling you the metadata on that file is scrambled.

Here’s the fix: Run chkdsk to check and repair the file system. This is the first thing every tech I’ve trained does, and it fixes about 70% of these cases.

1. Open Command Prompt as Administrator. Click Start, type cmd, right-click “Command Prompt” and select “Run as administrator.”
2. Type chkdsk C: /f /r and press Enter. Replace C: with the drive letter showing the error. The /f flag tells it to fix errors, /r locates bad sectors and recovers readable info.
3. If the drive is your system drive (usually C:), you’ll see a message like “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. Then restart your computer.
4. If it’s a non-system drive (like D: or E:), chkdsk will run immediately. Wait for it to finish—this can take 10–60 minutes depending on drive size and corruption level. You’ll see a summary at the end: “Windows has made corrections to the file system.”
5. After chkdsk finishes, try accessing the file or folder that triggered the error. If it still fails, move on to Cause #2.

What you should see: After typing chkdsk C: /f /r, you’ll get a prompt about scheduling the check (if it’s the system drive) or the scan starting immediately. During the scan, you’ll see stages like “Stage 1: Examining basic file system structure...” and then “Stage 2: Examining file name links...” and so on. If it finds corrupted EA data, it will attempt to repair it. After reboot, you might see a command window flash briefly—that’s chkdsk running before Windows loads.

Cause #2: Corrupted system files or drivers

If chkdsk didn’t find anything wrong, the next suspect is system file corruption or a bad driver. The error can also show up if a system file that uses EAs (like some registry hives or security templates) got damaged. I’ve seen this on Windows 10 machines after a botched update or power failure.

First step: Run System File Checker (SFC). This scans and replaces corrupted Windows system files.

1. Open Command Prompt as Administrator again (same method as above).
2. Type sfc /scannow and press Enter. Let it run completely—don’t close the window. It usually takes 10–20 minutes.
3. After it finishes, you’ll see one of three messages: “Windows Resource Protection did not find any integrity violations,” “Windows Resource Protection found corrupt files and successfully repaired them,” or “Windows Resource Protection found corrupt files but was unable to fix some of them.”
4. If it says it couldn’t fix some files, run the Deployment Image Servicing and Management tool next. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This takes longer—15–30 minutes—and requires a stable internet connection because it downloads fresh copies from Windows Update.
5. After DISM completes (it will say “The restore operation completed successfully”), run sfc /scannow one more time. This second pass often fixes what DISM uncovered.

Second step: Update or roll back drivers. A bad driver, especially for storage devices, can cause EA corruption errors. Open Device Manager (right-click Start > Device Manager). Expand “Disk drives” and “Storage controllers.” Look for any device with a yellow exclamation mark. Right-click it and select “Update driver” > “Search automatically for drivers.” If you recently updated a driver and the error started, roll it back: right-click the driver > Properties > Driver tab > Roll Back Driver.

What you should see: SFC will print progress as percentages (like “Verification 100% complete”). DISM shows a progress bar. After each tool finishes, read the message carefully. If SFC says it repaired files, your error might be gone after a reboot. Test by accessing the file again.

Cause #3: Faulty hardware (bad drive, loose cable, or failing memory)

If both chkdsk and SFC come back clean—or chkdsk keeps finding errors on the same drive—the hardware itself is failing. I’ve seen this a dozen times: a user gets 0xC0000053 every time they copy a specific file, and it’s because the drive has physical bad sectors that keep corrupting data.

Step 1: Check drive health. Download a free tool like CrystalDiskInfo (standard edition, no adware). Install it and look at the “Health Status” for each drive. If it says “Caution” or “Bad,” replace the drive. If it says “Good,” still check the raw values: look at “Reallocated Sector Count” and “Current Pending Sector Count.” Non-zero numbers mean the drive is failing.

Step 2: Reseat cables (for desktop PCs). Turn off the computer, unplug it, and open the case. For SATA drives, disconnect and reconnect both the data cable (thin, usually red or black) and the power cable (wider, with four pins). Make sure they click into place. Then boot back up and test.

Step 3: Test RAM. Bad memory can corrupt file operations too. Run Windows Memory Diagnostic: press Windows Key + R, type mdsched.exe, press Enter. Choose “Restart now and check for problems.” The PC will reboot and run tests for about 20 minutes. If it finds errors, you have a faulty RAM stick—replace it.

What you should see: CrystalDiskInfo shows a green circle with “Good” or a yellow/red warning. Reallocated Sector Count will be under “Raw Values” – any number above 0 means the drive has replaced bad sectors. The memory test will show progress as a percentage and report errors at the end (or show “No errors”).

Quick-reference summary table

Start with cause #1. It’s quick, safe, and fixes the majority of cases. If you’re still stuck after trying all three, you might need to recover data from a backup and replace the drive. Don’t keep hammering on a failing disk—it’ll only get worse.