Fix NS_E_METADATA_NO_EDITING_CAPABILITY (0XC00D32D6)

You hit this metadata error, and it's annoying.

You right-click a music file, go to Properties > Details, try to change the artist or title, and Windows slaps you with NS_E_METADATA_NO_EDITING_CAPABILITY (0XC00D32D6). The edit fields are greyed out or throw the error when you click OK. I've seen this on Windows 10 22H2 and Windows 11 23H2, especially after moving files from a different drive or downloading from certain services.

The fix, in order of likelihood

1. Unlock the file

Windows Explorer locks the metadata of files it thinks are in use or have restricted permissions. The first step is always to check if the file is actually read-only or blocked.

Right-click the file, choose Properties.
At the bottom of the General tab, uncheck Read-only if it's ticked.
Then click Unblock if that button appears (it shows when the file came from another computer or the internet).
Apply, OK.

Now try editing metadata again. If it works, you're done. If not, the problem isn't file permissions — it's that Windows' built-in metadata editor simply refuses to handle certain file formats or encoding quirks.

2. Use a proper tag editor (the real fix for 90% of cases)

What's actually happening here: Windows Explorer uses the Windows Property System to read and write metadata, but that system has limited support. It works fine for simple MP3 ID3v2 tags or standard JPEG EXIF, but it chokes on:

FLAC files with Vorbis comments
OGG containers
MP4/M4A files with iTunes-style metadata
Any file where the tag format is non-standard or corrupted

The error NS_E_METADATA_NO_EDITING_CAPABILITY literally means "the codec or the metadata handler can't edit this." It's not a bug — it's a limitation. Microsoft never prioritized writing support for every tag format.

Skip Explorer's editor entirely. Download Mp3tag or MusicBrainz Picard. Both are free, well-maintained, and handle dozens of file types. Open your file in Mp3tag, edit the fields, save. It bypasses Windows' broken handler and writes tags directly.

3. If Mp3tag also fails: check file encoding or corruption

Rarely, the file itself has a corrupt header. Mp3tag will show an error like "Invalid data" or the save just doesn't stick. In that case:

Copy the file to a new location (sometimes path length or special characters confuse the metadata system).
Use a tool like ffprobe to check if the file is valid:
```
ffprobe -v error "yourfile.mp3" 2>&1
```
If it reports errors, the file is damaged.
Re-encode the file using ffmpeg or a media converter:
```
ffmpeg -i input.mp3 -c copy -map_metadata -1 output.mp3
```
The -map_metadata -1 strips all existing tags, letting you start fresh.

Why step 2 works and step 1 sometimes doesn't

Windows Explorer's metadata editor is a thin wrapper over the Windows Media Foundation metadata handler. That handler only supports editing for formats that have a registered IPropertyStore implementation with write capability. Most third-party codec packs don't register a write handler — they only register read. So when you right-click and try to edit, Windows says "nope, no editing capability." Mp3tag doesn't use that API at all — it writes the raw binary tag data directly. That's why it works when Explorer won't.

Less common variations

Video files (MP4, MKV, AVI): Same error, same root cause. Use MKVToolNix or MP4Remuxer to edit metadata.
Image files (JPEG, PNG): If the error shows for images, it's almost always a permissions issue. Check the file is not on a network share that blocks write access. Right-click the folder > Properties > Security and verify your user has Modify permission.
Files on OneDrive or SharePoint: Synced files sometimes inherit read-only attributes from the cloud. Right-click the OneDrive icon in the system tray > Settings > Unlink this PC, then re-link. This resets the file attributes.
Files with names over 260 characters: Windows Explorer chokes. Shorten the filename or move the file to a shorter path, then edit.

Prevention: stop using Explorer for metadata

Honestly? Don't rely on Windows Explorer's properties panel for anything beyond basic inspection. It's not designed for bulk or format-agnostic editing. For music, use Mp3tag. For video, use MKVToolNix. For photos, use Adobe Bridge or FastStone Image Viewer. These tools write metadata correctly and won't give you the 0XC00D32D6 error. If you must use Explorer, keep files on local NTFS drives (not FAT32 or exFAT, which lack file-level permissions) and never set files as read-only.

One last thing: if you're a developer and you see this error in your own app, you're probably calling IPropertyStore::SetValue on a file whose media source doesn't support writing. Check the format handler's GetCapabilities before attempting to write. It's a common mistake.