Video error 0x80004005 "Can't play": how to fix it on Windows

By the FixMP4 engineering team · · 7 min read

Error 0x80004005 is Windows' least helpful message: "unspecified error". When it appears as "Can't play" in the Photos app, Media Player or Movies & TV, it means the playback pipeline failed and nobody along the way reported why. The good news is that the possible causes are a short list, and two quick tests tell you which one you are dealing with. This guide is about 0x80004005 during video playback; the same code also appears for file copying and network shares, which we touch on where it overlaps.

Two tests that narrow it down

  1. Play the file in VLC. VLC uses its own decoders and its own rendering path.
  2. Copy the file to a plain local folder (for example C:\Temp) and play the copy in the Windows app.
VLCLocal copy in Windows appMost likely cause
PlaysPlaysFile access: sync folder, network share, permissions
PlaysStill failsThe Windows app, its decoders or the graphics driver
FailsFailsThe file is damaged

Cause 1: file access (sync folders, shares, locked files)

0x80004005 is the same code Windows uses for many file access failures, and media apps surface it unchanged. Typical situations:

  • The file is a OneDrive, Dropbox or Google Drive placeholder that is not downloaded yet, or the sync client is still writing it.
  • The file sits on a network share or NAS that went to sleep or uses an old SMB version.
  • Another program has the file open and locked: a video editor, a backup tool, the camera's import app, or a half-finished copy.
  • The file was copied from another PC and your account lacks read permission.

Fixes: right-click the file and pick "Always keep on this device", wait for sync to finish, close editors and import tools, or copy the file into your own Videos folder. If the local copy plays, you are done.

Cause 2: the Windows app is in a bad state

The modern Media Player, Photos and Movies & TV apps keep caches and settings that can break after an update.

  1. Open Settings, Apps, Installed apps, find the app, choose Advanced options.
  2. Click Repair first; it keeps your settings. If that fails, click Reset.
  3. Check the Microsoft Store Library for app and extension updates, especially HEVC Video Extensions, AV1 and VP9.
  4. Sign out and back in, or restart. Store apps often hold old components until a restart.

The Photos app has a specific quirk: its built-in video editor and its viewer use different paths. If a clip fails in the viewer, try opening it from Media Player instead, and vice versa.

Cause 3: graphics driver and hardware decoding

The Windows media apps decode video on the GPU. A broken or outdated graphics driver, a laptop switching between integrated and dedicated graphics, or a remote desktop session can make decoding fail with 0x80004005, especially for 4K, 10-bit or HEVC footage.

  • Update the graphics driver from Intel, AMD or NVIDIA directly, not only through Windows Update.
  • On laptops with two GPUs, assign the app to one GPU under Settings, System, Display, Graphics.
  • Test the file without remote desktop or screen-sharing software running.
  • If only high-end footage fails (drone 4K, iPhone HDR), the decoder is likely the bottleneck; VLC or a lighter copy will work. Our guide to playing MOV files on Windows covers the HEVC and HDR side in more detail.

Cause 4: unusual but healthy files

Some files are valid but use features the built-in apps handle poorly: variable frame rate from screen recorders, very high frame rates, PCM audio inside MP4, rotation metadata, or several audio tracks. These usually play in VLC. If you need them to open everywhere, make a standard copy (H.264 video, AAC audio, constant frame rate) with HandBrake. Keep the original.

Cause 5: the file is damaged

If VLC cannot play the file either, the problem is inside it. For camera, phone, drone, dashcam and screen recordings, the most frequent damage is a recording that stopped without being finalized:

  • The camera or phone switched off because the battery died.
  • The recording app or the system crashed.
  • The card was removed or filled up mid-recording.

MP4 and MOV write their index (the moov atom) last, so in all three cases the frames exist but the map to them does not. Windows cannot interpret the file and falls back to the generic 0x80004005. Other damage includes a truncated download, or holes left by a failing card; our post on video corrupted after transfer explains how to spot those.

How to recover it

  • Look for a second copy first: the original card, the phone's cloud backup, a messaging app that still has the full file.
  • Check the size: if it matches the length of the recording, the data is there and the index can be rebuilt.
  • Run the copy through the FixMP4 repair tool. It works in the browser without uploading the file, reads the H.264 or HEVC frames and AAC audio directly, and builds a new index. For many cameras it needs a short reference clip recorded with the same device and settings. The preview is free, so you can confirm the footage is there before paying to export it.

After repair, the new MP4 opens in the Windows apps like any other file. If it still fails there but plays in VLC, go back to causes 2 and 3; the file is now fine.

What does not help

  • Generic "PC repair" tools that promise to fix 0x80004005 system-wide. The code is generic; the fix is specific.
  • Registry edits found for the file-sharing variant of this code. They address network authentication, not playback.
  • Renaming .mov to .mp4. Both use the same structure, and renaming changes nothing inside.

Summary

  1. Test in VLC and from a local copy.
  2. Access problem: download, unlock or copy the file locally.
  3. App problem: repair or reset the app and update extensions.
  4. Driver problem: update the GPU driver, pick a GPU, try without remote sessions.
  5. Damaged file: work on a copy and rebuild it; see the full guide to repairing a corrupted video. For related Windows codes, compare 0xc00d36c4 and 0xc1010103.

If the Media Player app shows "This file isn't playable" with 0xc10100be instead, follow the 0xc10100be guide; when the message mentions your speakers or headphones, the 0xc00d36fa audio device fix applies.

Frequently asked questions

What does 0x80004005 mean when playing a video?

It is the generic Windows code E_FAIL, "unspecified error". The playback component failed without a more specific reason, so the code alone does not say whether the file, the app, the driver or file access is to blame.

Why does a video play in VLC but show 0x80004005 in Photos or Media Player?

VLC uses its own decoders and does not depend on the Windows graphics pipeline. If VLC plays the file, the file is fine and the problem is in the Windows app, its decoders or the graphics driver.

Can a file in OneDrive cause 0x80004005?

Yes. A cloud-only placeholder, a file still syncing or a file locked by the sync client can make the Windows media apps fail with this unspecified error. Making the file available offline usually fixes it.

Will converting the video fix error 0x80004005?

Converting helps when a healthy file uses a codec or profile the Windows app handles badly. It does not help a recording that lost its index; that file has to be repaired first, then converted if needed.

Have a broken recording right now?

Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.

Open the repair tool
  • 0x80004005
  • unspecified error
  • Windows
  • Photos app
  • Movies & TV