cgsecurity.org

I double checked it good sir.
https://youtu.be/dgn8bsvVz7g

First I found 2 lost partitions, but from one of them nothing was recovering.

Then after deep analyse, I find this unable to copy from partition again.
Now I am able to copy from directories I was unnable before, but when I navigate those with arrow keys it make beep sounds. Constantly. What it mean?

Or whole other data will be overwritten with recovered partition?

This is progress after few days. Will I be able to somehow save the results when it 100%, or after I reboot pc all will be lost and I need to scan again?

cgrenier wrote: 11 Jan 2020, 15:41 Windows chkdsk wrongly repairing a filesystem is the most dangerous possible thing.

How can I make sure that this is not gonna happen? What are countermeasures to prevent this when using testdisk?

That you very much for reply, because Im kinda stuck here horrified to do next move.

"Windows chkdsk wrongly repairing a filesystem is the most dangerous possible thing."
It can be initialised by testdisk, or you talking about this disk checking blue screen that sometimes pop on the loading on ...

No real risk to data right? It just create new partition table, while data stay intact, so even if something will go wrong and this new partition table turn out to be me faulty or something, I still can do it all over again with new settings right, because data stay unaffected only partition table ...

Have hdd with lst partition table. Partitions successfully found with testdisk.
The I successfully copied few big files from one of the partitions.
And then I decide to copy files from another partition(I think somewhere at following steps roots of the problem).
I comeback to partitions list ...