Quick Answer
If you're in a hurry: open an elevated Command Prompt and run fsutil ea query <filepath> to see the EA list, then use fsutil ea delete <filepath> <name> to remove the bloated entries. If that's too manual, the real fix is copying the file to a new location without extended attributes – that clears the EA set entirely.
Why This Happens
Extended attributes (EAs) are metadata tags that Windows apps – especially file syncing tools like Dropbox, OneDrive, or older backup software – can attach to files. Each EA has a name and value, and there's a hard cap: the total EA set for a single file can't exceed 64KB. When you hit 0xC0000050, some app has stuffed too many EAs onto the file, or one EA value is just ridiculously large.
I see this most often after migrating files from a Mac or Linux system to Windows, where those OSes use extended attributes heavily (tags, security contexts). Also happens with torrent clients that write metadata, or with old antivirus scanners that wrote EA-based quarantine info. If you can't copy, move, or even open the file, this is probably why.
Step-by-Step Fix
Step 1: Identify the problem file
You'll see the error when you try to copy, move, or open a specific file. Make a note of its full path – for example C:\Users\YourName\Downloads\corrupt.zip.
Step 2: Check the EA set on that file
Open Command Prompt as Administrator. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
In the black window, type:
fsutil ea query "C:\Users\YourName\Downloads\corrupt.zip"Hit Enter. You'll see a list like:
Extended Attributes (EA) information for file: C:\Users\YourName\Downloads\corrupt.zip
EA[0] Name: someapp.tag Value: 1234 binary
EA[1] Name: backup.meta Value: 4096 bytes
...If you see more than a dozen entries, or any entry with a value over 32KB, that's your culprit.
Step 3: Delete the oversized or too-many EAs
You can delete them one by one. For each EA you want to remove, run:
fsutil ea delete "C:\Users\YourName\Downloads\corrupt.zip" "someapp.tag"Replace someapp.tag with the exact name from the query output. Do this for every EA you see, or at least the ones with large values. After each deletion, re-run the query to confirm the count dropped.
Step 4: Test the file
Try copying or opening the file again. If the error's gone, you're done. If not, move to the alternative fix below – it's faster for files with dozens of EAs.
Alternative Fix: Copy Without EAs (Faster for Bulky Files)
If there are too many EAs to delete manually, just copy the file to a new location using robocopy without extended attributes. This essentially strips all EAs in one shot.
Open an elevated Command Prompt and run:
robocopy "C:\Users\YourName\Downloads" "C:\Users\YourName\Desktop\Copy" "corrupt.zip" /COPY:DATWait – the /COPY:DAT flag tells robocopy to copy only Data, Attributes, and Timestamps, not extended attributes. After the copy finishes, delete the original file (if you want) and rename the copy back to its original name. The EA set will be gone.
Prevention Tip
Once you clear the EAs, keep an eye on what software writes them. If you use Dropbox, check its settings – sometimes it writes EA tags for sync metadata. For OneDrive, you can disable extended attributes in the registry (though I don't recommend it unless you really need to). The real fix is avoiding tools that pile on EAs like junk mail. If you're transferring files from a Mac or Linux, use robocopy with /COPY:DAT from the start – that strips the unwanted baggage before it lands on Windows.