STATUS_EAS_NOT_SUPPORTED (0XC000004F) Fix Guide

This error pops up when a program tries to write extended attributes to a drive that doesn't support them—usually a FAT32 or exFAT external drive, or a USB stick.

You're copying a folder from one drive to another—maybe a backup or a transfer to a USB stick—and halfway through, Windows throws up an error: STATUS_EAS_NOT_SUPPORTED (0XC000004F). The copy stops cold. You might see it with Robocopy, File Explorer, or even a backup tool like Macrium Reflect. The specific trigger is almost always a target drive formatted as FAT32 or exFAT—common on USB flash drives, SD cards, and external hard drives bought pre-formatted for Mac and PC compatibility. These file systems simply don't have the ability to store extended attributes (EAs).

What's really going on?

Extended attributes are extra metadata that NTFS tacks onto files—stuff like security descriptors, encryption flags, or custom tags used by some apps (like DESKTOP.INI file settings). When you try to copy a file that has these attributes to a FAT32 or exFAT drive, the file system says, "I can't store that extra data, so I'm refusing the whole operation." Windows doesn't gracefully skip the EA part—it just kills the transfer.

The fix depends on whether you absolutely need those attributes preserved. Most home users don't. But if you're a system admin moving files with security settings, you've got to keep them.

Fix 1: Reformat the target drive to NTFS (best for most users)

This is the real fix. NTFS supports extended attributes natively. But reformatting wipes the drive, so back up anything you need on it first.

Plug in the USB drive or external hard drive that's giving you the error.
Open File Explorer, right-click the drive in the left pane, and select Format.
In the Format dialog box, set the File system to NTFS. Leave Allocation unit size at Default unless you know what you're doing.
Check Quick Format (unless the drive has bad sectors—then uncheck it for a full format, but that takes hours).
Click Start. Windows warns you this erases everything—click OK.
Wait for it to finish. You should see a "Format complete" box.
Try your copy operation again. The error should be gone.

After formatting: The drive will no longer work on Macs without third-party NTFS support, but it'll work fine on all Windows PCs.

Fix 2: Copy without extended attributes using Robocopy (no reformatting)

If you can't reformat the drive—say it's a large external drive with data you can't relocate—you can tell Windows to skip the EA data during the copy.

Open an elevated Command Prompt (right-click Start, choose Command Prompt (Admin) or Terminal (Admin)).

Run this command, replacing source and destination with your real paths:

robocopy C:\Users\YourName\SourceFolder D:\BackupFolder /E /R:3 /W:10 /NP /A-:SH

The key switches: /E copies all subfolders, /R:3 retries 3 times, /W:10 waits 10 seconds between retries, /NP hides progress to keep output clean, /A-:SH removes the System and Hidden attributes if they're causing issues (they often are with DESKTOP.INI).
Press Enter. Robocopy will copy files and ignore any EA-related errors. It might report a few skipped attributes in the log, but the files land on the target drive.

What to expect: The copy finishes, but files may lose thumbnails or custom icons on the target drive—that's the EA data missing. No big deal for backups.

Fix 3: Use 7-Zip to compress files without EAs (advanced workaround)

This is a quirky but effective trick if Robocopy feels too technical. 7-Zip can compress a folder into an archive, and the archive doesn't carry EAs by default. Then you copy the archive to the FAT32/exFAT drive.

Download and install 7-Zip from 7-zip.org.
Right-click the source folder and choose 7-Zip > Add to archive.
Leave the archive format as 7z (or ZIP if you need compatibility). Under Parameters, add: -snl (that tells 7-Zip to not store NTFS security and EA data).
Click OK to create the archive on your local NTFS drive.
Now copy the archive file to the external drive. The copy should work because the archive itself has no EAs.

Downside: You'll need to extract the archive on the other end, which takes extra time.

What if it still fails after these fixes?

Three things to check:

Drive health: Run chkdsk D: /f on the target drive (replace D: with your drive letter). Bad sectors can mimic EA errors by corrupting metadata writes.
Windows version: Some older builds of Windows 10 (pre-1903) had buggy EA handling with exFAT, especially with large files. Update to at least Windows 10 22H2 or Windows 11.
File names too long: FAT32 has a 260-character path limit, same as old NTFS. If your source folder has deep paths, the copy might fail with a different error that looks like this one. Shorten the path or map a drive letter closer to the target.

If nothing else works, the drive might be physically failing. Back up what you can and replace it. I've seen a dying USB stick throw random STATUS_EAS errors because its controller couldn't handle metadata writes anymore.