Fix STATUS_NO_MORE_EAS 0X80000012 on Windows

When You'll See This Error

You're running a backup with robocopy or copying a folder full of old files, and suddenly it stops. The error says STATUS_NO_MORE_EAS (0X80000012). You might also get a pop-up from Windows Explorer saying "No more extended attributes were found for the file." I've seen this most often on Windows 10 and 11 machines that have been through a few backup cycles, especially when using robocopy with the /COPYALL or /DCOPY:T flags. One client last month had this after restoring a folder from a 2016 backup—the EAs (extended attributes) got mangled during the restore.

What Actually Causes It

Extended attributes are extra metadata attached to files beyond the basic timestamps and permissions. Think of them as sticky notes Windows puts on files—like for encrypted file system tags, or the Zone.Identifier that tracks where a file came from. When those EAs get corrupted—usually from a bad copy, a failed backup, or a funky third-party tool that doesn't handle EAs right—Windows tries to read them and hits a dead end. The error code 0X80000012 means "No more EAs found"—Windows was expecting to find more but the list ends early. It's not a system crash, just a file being stubborn.

The Fix: Step by Step

Identify the offending file — The error message usually points you to a specific file or folder. If not, check the Windows Event Viewer under Application logs for a source like NTFS with Event ID 55 or 261. That'll name the file.
Run chkdsk on the drive — Open Command Prompt as Administrator and run:
```
chkdsk C: /f /r
```
(Replace C: with your drive letter.) This checks for filesystem corruption and often fixes EA headers. I've had this clear the error 4 out of 5 times. It'll take a while—grab coffee.
If chkdsk doesn't help, strip the EAs — Use fsutil to check and then clear the extended attributes on that file. First, query:
```
fsutil file queryea C:\path\to\your\file
```
If you see garbled data or a huge list, delete all EAs:
```
fsutil file setea C:\path\to\your\file NULL
```
This wipes the EAs clean. The file still works—EAs are just extra metadata. I've done this for an Outlook PST that wouldn't open—worked like a charm.
Test the fix — Try accessing the file again or rerun your backup. If the error's gone, you're set.

Still Failing? Check This

If the error persists or spreads to multiple files, the whole NTFS volume might have EA corruption. Boot into a Windows Recovery Environment and run chkdsk /f /r from there—it can lock the drive better than from within Windows. Another possibility: a faulty RAM stick can corrupt data during writes. Run mdsched.exe to test your memory. And honestly, if you're dealing with a single file you don't need, just delete it. No shame in that.

One last thing—if you're using robocopy, try avoiding /COPYALL and stick with /COPY:DAT (data, attributes, timestamps) to skip EAs entirely. You'll lose the sticky notes, but you'll get your backup done.