The disadvantage with Partition Recovery Wizard is that one can only explore and see the files, cannot access it unless the partition table is rewritten. The point you have brought is a valid one but I would tend to think the last written ones will be in order. In this case we have only selected the partitions known in the last boot state which the OP also concurs. (Right now it is not the boot drive and the OP is not interested in making it bootable again but only recover the data in it- not system files.) It will only be the previous ones that had been overwritten by the later that would appear corrupted if any part of it is still left over and shows up.
The advantage with Test Disk is that if one can see the folders/files in the partitions shown and selected , one can straight away copy those to another drive even without rewriting the partition table. The OP will have a choice to select only the files/folders he wants and copy them. Again if some files are corrupted nothing can be done about it.
So, IMO, the OP should go ahead and rewrite the partition table pertaining to those selected partitions which all add up to the full capacity of the drive and last known state. If still the drive is not accessible, he should get on to Test Disk. Rewritng the partition table is only an operation done in Sector 0, and it in no way affects the data in the partitions.
I don't think one can find a similar case with so many past history where one has dealt with it and succeeded.
So there are only two options.
1.Bite the bullet, let PW write the partition table
with the three selected partitions and see whether the drive becomes accessible.
Check in PW and assign drive letters if those do not have one. If accessible - no guarantee anyway, we can only hope for the best - good. If some files are corrupt, that had already happened and so nothing to cry about.
2. Leave it as it is, get on to TestDisk. I am sure it will also show the same partitions, he can select the desired partitions, see the files and copy the files to another drive. The scanning will take a lot of time. He has to plugin the destination drive before running TestDisk so that it is recognised when it is run and ready to host the files. ( The OP had already tried TestDisk. I don't know what happened. Most probably he aborted it since it was taking a long time.) Again whether the files are good or corrupted we will know only after copying all the desired files.
Either way, the process itself is not going to corrupt the files.
So folks, a decision is upto you. I am going to bed now.
