This content has been marked as final. Show 3 replies
you need to do a manual (force) decryption with SafeTech/WinTech, as you've blown away details of what was, and what was not encrypted.
Thanks for your help. We successfully decrypted the D partition, but the C partition seems to have a hardware fault that precipitated the BSOD mentioned originally. It seems that the decrypt tool can't get past this error. That is second hand information as the decryption was administered by someone other than me (support team in Japan). Does that seem to be reasonable? We may look to do a raw filesystem copy to see if that will allow us to decrypt on a good HDD. Otherwise we'll have to send the disk out for data recovery (Ontrack?) Sound reasonable?
its unlikely that a hardware fault would block the decryption, unless the physical drive itself was dead.
If they started forced decryption on C, and stopped it mid point, I hope they wrote down how far it got, otherwise it's going to be really tough working out where to continue from.