I had a similar experience with my first use of this tool. I performed an initial basic scan and it didn't find anything recoverable. Then I clicked on deep scan and after it ran for several hours with a few hours left to go I stopped the scan and saw a large number of files I was missed were recoverable. I recovered a file to analternate location - being careful not to write anything to the disk with the missing files, as a test and it came back perfect so I closed the list display window and started another deep scan, all the while I had removed anyone from accessing this portion of the system and no data was being written to the drives with the missing data - none at all - no reboots performed on the server and no activity on the folders where the data was missing - I allowed the deep scan to run to completion and then from the listing I see most of the missing files are unrecoverable and are indicating that they have been overwritten with files of the same name?? Is there something destructive about running the deep scan that makes it not return the same results the 2nd time you run it on the same disk that previously seemed to yield very favorable possibilities for recovery?
Bth, I've put your post into a new topic as you posted directly following a mod's request not to respond to that topic.
There are a huge amount of variables in what you're doing that would have to be quantified, the main one being that you're comparing a cancelled deep scan with a completed deep scan. The different stages of the scan evaluate the state of the files more thoroughly.