Error explained
Error 0xc00d36e5 "item is unplayable": causes and fixes
"Item is unplayable, please reacquire the content. 0xc00d36e5." The message sounds like a DRM problem, but on your own recordings it almost always means one thing: the file was cut short during a transfer. The classic case — recorded on a phone, tested fine, copied via USB stick to a PC, now dead.
Quick answer: check the original on the source device first — if it still plays, re-transfer with a cable and you're done. If the original is gone, the truncated copy can usually be repaired locally by rebuilding its index from a short healthy clip recorded on the same device.
What actually happened
MTP transfers (phone → PC), USB sticks, and SD readers all buffer writes. Disconnect early — or hit a flaky cable or a failing stick — and the tail of the file never lands. Since an MP4 stores its index at the end, a truncated copy can show the right file size in Explorer and still be missing the structure players need. Windows reports it as "unplayable."
Fix it, in order
- Check the source device. If the video still plays on the phone/camera, delete the bad copy, re-transfer with a cable, and safely eject before unplugging. Done — no repair needed.
- Re-copy from the USB stick. Sometimes the stick's copy is fine and it's the second hop that broke. Compare file sizes byte-for-byte, not just "56 MB".
- Original gone? Repair the copy. Work on a duplicate, try
ffmpeg -i broken.mp4 -c copy fixed.mp4, and when that fails use the reference-file method: record a 10-second clip on the same phone at the same settings and rebuild the index from it.
Skip the converters. VLC's convert tool on a truncated MP4 produces a near-empty file — it can't read what it's converting. That 1 KB output doesn't mean your footage is gone; it means you need index reconstruction, not conversion.
Repair the truncated copy — locally
StreamSalvage rebuilds the missing index on your own PC from a short reference clip. Free preview of the repaired video, $29 one-time only if it works, nothing uploaded.
Download StreamSalvage for WindowsRelated Windows playback errors
Same family, different codes: 0xc00d36c4 (format not supported), 0xc00d5212 (missing codec), 0xc10100be (file isn't playable). The diagnosis pattern — test in VLC, check the source, then repair — is the same for all.
Frequently asked questions
What does error 0xc00d36e5 "item is unplayable" mean?
Windows opened the file but found its contents unreadable — most often because the file was cut short during a copy or transfer. The size can even look right while the crucial index data at the end is missing or garbled.
Why did my video break when I copied it from my phone?
Phone-to-USB and phone-to-PC transfers over MTP are fragile: unplugging early, a flaky cable, or a drive ejected before the write-cache flushed all truncate the file. The copy triggers 0xc00d36e5 even though the recording was fine on the phone.
Is the original video still on my phone?
Check before anything else — if the original plays on the phone, just re-transfer it with a cable and don't disconnect mid-copy. If the original was deleted after the transfer, the corrupted copy is all you have, and it needs structural repair.
Can a file with error 0xc00d36e5 be repaired?
Often, yes. If most of the stream data survived the truncation, a reference-file repair can rebuild the missing index — using a short healthy clip from the same phone or camera as a template. StreamSalvage does this locally with a free preview.