Encrypted Hard disk and MBR of windows corrupted
Here's what i did.. I had a Windows 7 installed partition on my thinkpad T420 .. on the second hard disk partition i installed Fedora to have a dual boot with windows .. Meanwhile I had installed PGP Desktop 10.1.2 on my windows and began encrypting the hard disk .. This linux partition having fedora won't be available on windows, so i assumed that only the other partitions would get encrypted.. Since PGP allows encryption to be paused and resumed , I paused the encryption at some 25% ..
What happened next was total disaster.. The fedora partition somehow got corrupted because of my experiments and so without a second thought I just reinstalled the fedora .. Since my windows partition was 25% encrypted, Fedora just corrupted the MBR of windows and what i now had on startup was a pure linux GRUB and no windows boot option ...
To fix this i put the windows recovery disk and did bootrec.exe /fixBoot /fixMbr and so on ... So now the GRUB loading was gone as well.. But since the PGP encryption has been done, i couldn't continue into windows ... So to see if there's any way to decrypt this encrypted hard disk I read some posts and technical stuffs that PGP had here .. They asked me to download a recovery image burn on to a disk and try booting... I did so and the PGP screen comes up and says that it failed to load some modules and just says "Cannot continue", Press any key to continue ...
My doubt now is that can this PGP recovery image decrypt a partially excrypted disk (only 25% of the disk is encrypted) .. ??
Have spent more than 6 hours in progressing so far ... Any help regarding how to decrypt the hard disk and fixing the MBR of windows is appreciated ...
That means you have the wrong
That means you have the wrong bit length for your OS. if you have a 64bit OS you need 64bit WinPE, and if you have 32bit you need 32bit WinPE - Then go through normally.
You're nearly there just need the correct bit WinPE disk.
http://www.symantec.com/business/support/index?page=content&id=TECH149478 - ignore the actual solutions on this page but the subsystem error is the same