Fix ERROR_INVALID_EA_NAME (0X000000FE) on Windows

You're in the middle of a big file copy — maybe using Robocopy, maybe dragging a folder to an external drive — and bam: ERROR_INVALID_EA_NAME (0X000000FE). The copy stops, you get a Windows error dialog that says something like "The specified extended attribute name was invalid." It's cryptic, and it usually hits when dealing with files that have custom metadata or tags, like old Office documents with custom properties, or files from a Linux server with extended attributes that Windows doesn't grok. I saw this last month with a client who had a bunch of PDFs tagged with Adobe Bridge keywords — the copy would fail on exactly those files.

What the Heck Is an Extended Attribute?

Extended attributes (EAs) are extra data attached to a file beyond the basic stuff like name, size, and timestamps. Windows NTFS uses them for things like FILE_ATTRIBUTE_ARCHIVE, custom metadata, or encryption info. The error 0X000000FE means Windows hit an EA name that's either null, empty, or contains characters Windows can't handle — like a null byte or a weird Unicode character. Usually happens after a file was modified by a third-party app that didn't clean up after itself, or during a cross-platform copy where Linux or macOS slapped on attributes Windows barfs at.

Root Cause in Plain English

Think of a file as a folder with a label on it. The label is the EA. If the label has garbage scribbled on it — like a stray invisible character — Windows can't read it, so it throws up its hands and says "nope." The copy fails, and you're stuck. The fix is to strip or fix that bad label. Don't bother with chkdsk — that's for disk corruption, not EA corruption. The real fix is surgical.

How to Fix It (Numbered Steps)

Identify the offending file. The error usually names the file. If not, run Robocopy with logging to catch it. Open a Command Prompt as admin and run:
```
robocopy C:\source D:\dest /E /LOG:copy.log
```
Then search the log for 0X000000FE. That's your bad file.
Backup the file first. Right-click the file, copy it to a temp folder using basic Windows copy (Ctrl+C, Ctrl+V). If that fails, skip it for now — we'll fix it in place.
Strip the extended attributes. Use the command-line tool fsutil to check the EAs. In an admin Command Prompt, run:
```
fsutil file queryea "C:\path\to\file.ext"
```
If it lists EAs, you'll see them. If it says "Error: The specified extended attribute name was invalid." — that's the problem. Then run this to wipe all EAs:
```
fsutil file setea "C:\path\to\file.ext" /clear
```
Note: This removes ALL extended attributes. That might strip custom icons, tags, or encryption metadata. But it beats the error.
Or just copy with robocopy and skip EAs. If you don't care about preserving metadata, run:
```
robocopy C:\source D:\dest /E /COPY:DAT /NOOFFLOAD /R:2 /W:5
```
The /COPY:DAT flag copies only Data, Attributes, and Timestamps — not EAs. The /NOOFFLOAD forces a pure file-level copy. This bypasses the bad EA entirely.
If it's a folder with hundreds of files, don't run fsutil on each one. Instead, use PowerShell to bulk-strip EAs. Open PowerShell as admin and run:
```
Get-ChildItem -Path "C:\source" -Recurse | ForEach-Object { fsutil file setea $_.FullName /clear }
```
This clears EAs on every file in that folder. Test on a small subfolder first.
After stripping, try the copy again. Use standard Windows copy or Robocopy. If it fails, the file might have corruption beyond EAs — try copying with /COPY:DAT alone.

What to Check If It Still Fails

If the error persists after stripping EAs, here's what to look at:

Antivirus interference. Some AV suites (looking at you, McAfee) lock file metadata during scans. Temporarily disable real-time protection and retry.
File system damage. Run chkdsk /f C: on the source drive. If the file's MFT entry is hosed, that'll flag it. But don't expect this to fix EA issues — it's a long shot.
Third-party tools. Apps like Dropbox, Google Drive, or backup software can add their own EAs. If the file is in a synced folder, pause sync and try copying outside that folder.
NTFS permissions. If you don't have rights to read the EAs, you'll get this error. Right-click the file, go to Properties > Security, and make sure your account has Full Control.
Last resort: Use icacls to reset ACLs on the file: icacls "file.ext" /reset. This or a full reformat of the destination drive if it's toast.

In my experience, step 3 or 4 fixes 9 out of 10 cases. If you're still stuck, the file itself might be partially corrupted — try opening it in its parent app (like Word for a .docx) and resaving. That often rebuilds the EA structure clean. Good luck.