Data Recovery Case File · Formatted & Logical Faults · What Repair Tools Actually Fix
Those Services Mend Containers, Not Missing Content
His enquiry describes a specific dead end. A folder of videos corrupted after a drive failure: "the files are there and so are the titles, sizes and formats, however when trying to play them they all fail, and basic steps to repair such as online video repair services haven't worked. These files are in various formats." Those services are a real technique with a real limitation, and their failure tells him something useful — because what they fix is the wrapper around a video, and his problem is not the wrapper.
| Media | Video files recovered following a drive failure — filenames, sizes and formats intact; playback failing across multiple container formats; third-party repair services attempted |
| Reported situation | Video files affected following a hard drive failure · filenames, sizes and formats present · playback failing on all affected files · multiple container formats involved · online video repair services attempted without success |
| Fault class | Content-level damage rather than container damage — repair tooling inapplicable; source medium to be re-read rather than output repaired |
| Equipment used | Repair attempts on recovered output discontinued · original source drive re-read rather than output repaired · imaged write-blocked under per-sector timeouts with weak regions revisited · files reassembled from the image · playback validated and losses reported by affected duration |
The decode: what a video repair tool is for
How those services work: a video file has two parts — a container holding structural information about the recording, and the encoded stream that is the picture and sound. The container includes an index written when the file is closed, describing frame positions and timing. If a recording was interrupted, the stream exists and the index never got written, so nothing will play a file it cannot navigate. Repair services rebuild that index, frequently by taking a known-good file from the same device as a reference for what the structure should look like.
Why that is genuinely effective: for interrupted recordings it works well, and it is the correct tool. A camera that lost power mid-take produces exactly the file those services were written for.
Why it did nothing here, and this is the informative part: his files came from a drive failure, not an interrupted recording. A failing drive damages content — regions that could not be read, or that returned incorrect data, distributed through the stream itself. Rebuilding an index over a stream with holes in it produces a file that navigates perfectly and still will not play, because the problem was never navigation. There is nothing for the tool to repair.
Why every format failed identically: he lists several container formats, and the same result across all of them points away from any format-specific issue and toward the common factor — the medium they were read from.
So what the failure of those services establishes: that the damage is in the content, which means the useful work is not on the recovered output at all. It is on the drive. Files that came back incomplete were assembled from a source that could not be fully read, and the answer is to read the source properly rather than to repair the result.
Why re-reading can produce a different outcome: a region that fails on one attempt often succeeds on a later one, because the outcome sits close to a threshold. Capturing under strict per-sector timeouts, with weak areas revisited across multiple passes, frequently returns material that a single pass missed entirely — and files reassembled from that image can be complete where the earlier output was not.
What to stop: running further repair tools on the recovered files. Each attempt works on a copy that is missing content, and no amount of processing puts back what was never read.
On the bench
Repair attempts on the recovered output were discontinued — those services rebuilding a container's index, which addresses an interrupted recording and does nothing where content is missing from the stream itself. The original source drive was re-read rather than the output repaired, imaged write-blocked under per-sector timeouts with weak regions revisited across multiple passes, since a region failing one attempt frequently succeeds on a later one. Files were reassembled from the image, and playback validated with losses reported by affected duration.
The outcome
The output repairs abandoned, the source re-read under timeout control across multiple passes and files reassembled from the image. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: a video file is a container and a stream, and repair services rebuild the container's index — which fixes an interrupted recording and does nothing for content that is missing. Your files came from a drive failure, so the damage is in the stream. The work belongs on the drive, not the output.
Recovered videos that repair tools can't fix
Stop running repair services on the recovered files and go back to the drive instead. A video is a container plus an encoded stream, and the container holds an index written when the file closes, describing where each frame sits. Repair tools rebuild that index — which genuinely works for a recording interrupted mid-take, because the picture exists and only the map was missing. Your files came from a drive failure, so the damage is inside the stream itself: regions that couldn't be read or came back wrong. Rebuilding an index over a stream with holes gives you a file that navigates perfectly and still won't play. Every format failing identically points at the medium. Re-reading the source properly is what changes the outcome.
The work belongs on the drive — call Guildford Data Recovery on 01483 901310; source re-read under per-sector timeouts with weak regions revisited across passes, files reassembled from the image.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.