Can't play a recovered avi file.

Recuva Recuva Bug Reporting
1

I have "perfect" recovered an avi file. I use recuva witch is placed on my "D partition" (SSD). I have recovered the file to an external disk. The avi file is about 1.10 GB. But... I can't play it.

I see it in VLC player. When I start the file in VLC I see under beneath a yellow line is running, but the file never start to play.

It's very frustrated that I see a "perfect" recovered file that not works.

When I read in, the recovered file, in other conversion programs, it is not recognized.

I'v tried to fix the avi file with DivFix+++ but no use.

Can someone help me?

2

Some users have reported that using Irfanview can succeed with recovered filed where other players can't.

It seems to be more tolerant of damaged files.

If Irfanview can play the file then re-saving it in Irfanview 'fixes' it so that other players can then read it.

3

Was the deleted file also on the D drive? If so there is virtually no chance of recovering the original data, as recovering deleted files from an SSD returns zeroes.

In Recuva Advanced Mode look at the header information. If it's all zeroes then the data has gone.

A 'perfect' file - I assume you mean in Excellent State - means that the deleted file's clusters have not been overwritten by another live file. Recuva will recover (i.e. copy) what's in those clusters, it cannot tell whether the contents are valid or not.

4

Thks for the quick reply.

Yes, the deleted file was on the D drive. The D drive is a partition of my C drive. So, it is a SSD drive and as far I can understand: it is no possible to recover files from a SSD drive.

Correct?

5

That's correct. Data clusters are zeroed almost immediately under Windows NTFS.

6

Thks Augeas. It's a pity I can no longer use recuva to recover, and so I suppose, no other programs can do.

7

That's right, it's beyond any recovery software's reach. It's a feature of Windows, NTFS, TRIM, DZAT and the SSD controller, where a file deletion triggers a TRIM command for each page, and following that the SSD controller executes a DZAT (Deterministic Zero After TRIM) response to any read request for that page. Recovery, if possible at all, is generally out of reach of any of the run of the mill authorities.