[File unrecoverable because overwritten by itself]

I understood that there is no other way to handle such cases. And I learned, that although a file is reported as 'unrecoverable', that nevertheless it is possible to try to recover it (and then check the content for rubbish). Thanks for that information.

[File unrecoverable because overwritten by itself]

Please look at the screenshot: Recuva reports, that a file is 'unrecoverable', because it is overwritten by another file. But this is not true.

 

What I did:

 - I saved a file as e:\Inst\rcsetup150.exe

 - then I moved this file to e:\Inst\_SystemTools\Recuva\rcsetup150.exe

 - then I deleted this file to the recycle bin

 - then I deleted this file within the recycle bin

 - immediately after this I started Recuva

 

So Recuva reports a wrong state ('unrecoverable'), although the file should be recoverable.

The reason is, that Recuva does not check, that a file has been moved, before it was deleted. But this can happen often.

 

This seems to me a bad error, because a file is reported to be lost, although it is recoverable.

 

Only if the user:

 - remembers, that he had moved the deleted file (this could be long ago) and

 - realizes, that the mentioned file in column 'Comment' was the source of the move and

 - searches this file (e:\Inst\rcsetup150.exe) in the list

then he will see, that this file is reported to be recoverable. But this disadvantages should not be necessary.