Page 1 of 1

problems files recover with testdisk

Posted: 20 Sep 2020, 22:55
by Blixa
hello. i just recovered very important files on a unreadable partition, but many of them have a .hdpvsbm extension and its impossible to read, even if i change it (i.e. pic.jpg.hdpvsbm). any suggestion? thanks

Re: problems files recover with testdisk

Posted: 21 Sep 2020, 01:11
by recuperation
Blixa wrote: 20 Sep 2020, 22:55 hello. i just recovered very important files on a unreadable partition, but many of them have a .hdpvsbm extension and its impossible to read, even if i change it (i.e. pic.jpg.hdpvsbm). any suggestion? thanks
Did you use Testdisk or rather Photorec?

Re: problems files recover with testdisk

Posted: 21 Sep 2020, 07:28
by Blixa
hello, thanks fr the answer. i used testdisk cause with testdisk i found the backup folder i had prepared before the damage happened. so I was able to save the entire content, but many files came with taht extension. using photorec I don't have this possibility, but only search for certain files on the whole disk (i.e. *.jpg). now I am making this attempt but it has been working for about 12 hours and I still haven't been able to verify the result.

Re: problems files recover with testdisk

Posted: 21 Sep 2020, 08:06
by recuperation
I don't know this file extension and can't find information about it.
Testdisk does not change file names. They must have been there before.

For me it appears as the result of a ransomware attack.
When you say "unreadable" partition do you mean that the partition as a whole is not accessible anymore?

Usually the attackers leave a message somewhere or when the drive with the OS is affected you get a notification your screen.

To access your files you probably will have to reverse some kind of encryption. Removing the new part of the extension is not enough.

Re: problems files recover with testdisk

Posted: 21 Sep 2020, 17:08
by Blixa
you were right... when i have read "Testdisk does not change file names" i understood. i had some problems some days ago, and probably the files got corrupted a few days ago and I didn't notice it. testdisk did a good job. thanks so much, you were really helpful