Game Bar recording won't play — why these files break, and how they're fixed
You recorded gameplay or a meeting with Windows Game Bar
(Win+Alt+R), the app crashed or the PC rebooted — and now
Screen Recording ... .mp4 is gigabytes on disk but shows
0:00 and won't open anywhere. This is a failure family we've studied in
depth from real crashed captures, and in the common case full
audio and video are recoverable — without a reference file.
Why crashed Game Bar files are worse than crashed camera files
Like a camera that loses power mid-recording, a crashed capture never gets its index (moov) written, so players have no map to the frames. But Game Bar — and other recorders built on Windows Media Foundation, including some meeting-recording flows — adds quirks of its own:
- The codec parameters aren't stored in the stream. Most cameras embed the H.264 setup data (SPS/PPS) in-band; these recordings don't. A rebuilt index is useless without it — which is why generic repair tools built for camera files give up on these.
- A pre-allocated zero tail. The recorder reserves space ahead of writing; a crash leaves hundreds of megabytes of zeros after the real footage. Naive repairs choke on the boundary, producing files that play and then die.
- Audio scattered in thousands of chunks. The AAC audio is interleaved in thousands of small runs between video frames. Getting video back but losing audio is the classic partial result — a repair that mishandles even the last chunk of a run silently drops the whole track.
How the recovery works
We catalogued seven distinct defects in this family from real crashed recordings — each one alone is enough to make a repair fail — and built the recovery to handle every one we've encountered: the frames are re-mapped from the raw data, the crash boundary is detected so the zero tail can't poison the result, the scattered audio runs are reassembled, and the missing codec parameters are solved by search — testing candidate parameter sets against your actual frames until one decodes cleanly. That is why no healthy sample recording is needed.
A recent real case from this class: a 2 GB, 21-minute 1080p meeting recording cut off by a crash — delivered back with full video and full audio.
When it honestly can't be fixed
If the crash happened right at the start, the file can be mostly the pre-allocated zeros with only seconds of real data — the analysis will tell you exactly how much real footage exists before you decide anything. And as always: a repair only counts if the output actually plays end to end; our verification refuses anything less.
Free during the beta: there is no payment step today. When paid recovery eventually launches, you will pay only if we hand back a file that actually plays. If it can't be recovered, we say so plainly.
Frequently asked questions
Why does my Game Bar clip show gigabytes on disk but 0:00 duration?
The frames were written continuously, but the index that maps them was never written because the recorder crashed before finishing. Players read the index first, find nothing, and report a zero duration. The large size is good news: the footage itself is usually still there.
Do I need a healthy sample recording as a reference?
No. These recordings don't carry their codec parameters in the stream, but we solve the missing parameters by testing candidates directly against your frames until one decodes cleanly — so recovery works from the broken file alone.
Another tool recovered the video but the audio is missing. Can that be fixed?
Usually yes. In this format the audio is interleaved in thousands of small runs, and a repair that mishandles the edges of those runs ends up dropping the whole track. Rebuilding both streams from the original broken file recovers the audio too — upload the original, not the other tool's output.
Does this apply to Teams or other screen recordings, not just games?
Yes. What matters is the recorder, not the content — Game Bar and other Windows Media Foundation based capture flows produce the same file structure, and meeting recordings are a common case of it.
What does it cost?
Nothing today. RepairMyVideo is free during the beta: there is no payment step, and analysis, repair and download all cost nothing. When paid recovery eventually launches, analysis and diagnosis will stay free, and payment will apply only to a successful repair, meaning a file verified to actually play, not just one that opens.