1. Malformed or Incorrectly Formatted ISRC Code
The culprit here is almost always a typo or formatting issue in the ISRC code itself. Windows Media Player expects the exact ISO 3901 standard: country code (2 alphanumeric), registrant code (3 alphanumeric), year (2 digits), and designation code (5 digits). Total: 12 characters. No spaces, dashes, or underscores.
I've seen this a hundred times — someone copies an ISRC from a spreadsheet that has a leading space, or they mix up letters and numbers. The error 0xC00D11FB literally means "invalid code." Windows Media Player won't even try to write it.
How to fix it
- Open Windows Media Player (or WMP-based tool) and right-click the track.
- Go to Advanced Editor or Properties (depends on version).
- Find the ISRC field (sometimes labeled "Recording Code").
- Delete the entire entry. Then type it manually:
USABC1234567— exactly 12 characters, all uppercase, no spaces. - Click OK or Apply. Test again.
If you're not sure of the exact code, look it up on a database like ISRC Search or your distributor's dashboard. Don't guess.
Pro tip: If the field won't let you enter exactly 12 characters, you're probably in a different field. ISRC is always 12. No exceptions.
2. File Format or Metadata Locking
Some file formats — especially older MP3s encoded with certain encoders — have metadata that Windows Media Player just can't write to. The file is "locked" in practice, even if the read-only attribute is off. This is common with FLAC files from legacy ripping software, or MP4s from iTunes.
I see this most with Windows Media Player 12 on Windows 10. The player tries to write the ISRC, hits a permissions or format barrier, and throws 0xC00D11FB even if the code itself is fine.
How to fix it
- Right-click the file and choose Properties.
- Uncheck Read-only. Click Apply then OK.
- Try adding the ISRC again in WMP.
- If it still fails, convert the file to a WMP-friendly format. Use Audacity or Foobar2000 to re-encode as WAV (lossless) or MP3 320kbps. Then re-add the ISRC.
Skip the MP4 container — WMP hates writing ISRC into it. Stick with MP3 or WMA if you want WMP to manage the metadata.
3. Corrupted Media Library Database
Less common but real: the Windows Media Player library database (CurrentDatabase_372.wmdb) gets corrupted. This happens when the player crashes while saving metadata, or after a failed Windows update. The database holds cached info, and a corrupt entry can block writing ISRC even when the file is fine.
You'll know it's this if you have no trouble writing ISRC to a fresh file but get 0xC00D11FB on an existing library entry.
How to fix it
- Close Windows Media Player completely.
- Open Task Manager (Ctrl+Shift+Esc) and kill any
wmplayer.exeprocesses. - Press Win+R, type
%LOCALAPPDATA%\Microsoft\Media Player, hit Enter. - Delete everything in that folder. Yes, all files. Windows Media Player will rebuild the database on next launch. This is safe — you'll lose star ratings and play counts, but not the actual media files.
- Restart Windows Media Player. It'll rescan your libraries. Try adding the ISRC again.
Heads up: This can take a while if you have a huge library. Don't panic if it hangs for a minute. Let it finish.
Quick-Reference Summary Table
| Cause | Fix | Time |
|---|---|---|
| Malformed ISRC code (wrong length, spaces) | Re-enter code manually — 12 chars, uppercase, no spaces | 2 min |
| File format or metadata locked | Remove read-only attribute or re-encode to MP3/WMA | 10 min |
| Corrupted WMP library database | Delete database files in %LOCALAPPDATA%\Microsoft\Media Player | 15 min |
Start with the first fix. Nine times out of ten it's a bad ISRC code. If not, move down the list. You'll have it sorted in under 20 minutes.