Encrypted files but os died

I have a pc with 3 os's on 3 partitions, I was repairing an installation of windows 2000 server when for some reason, both my xp partitions got hacked up.

now when i select an xp os, i get the windows 2000 splash screen, then error.

i verified by boot.ini points to the proper place, i even unplugged the drive with the windows 2000 partition.

I'm not too worried about the os but I had some files that were encrypted.

is it possible to somehow retrieve those files and encryption key?
i was thinking copying the user directory to a working xp box?

OR

if i do a soft install (upgrade) of the OS, will the key remain intact?

 

Gasolene, it seems that you are in big trouble. If you have backed up the key pair (as suggested by Arie), then you can get the data back otherwise its bye bye. Sorry.

 

Hi Gasolene, if you tell me everything about your setup I may be able to see what the problem is. What hard drives do you have and how they are configured – primary/secondary, master/slave. The partition layout primary/logical, and all the partitions you have. What OS is on what partition. Which OS has the boot.ini file and ntloader in it. Also what order you installed the three OSes and what exactly did you do while trying to repair 2K.

If the ntloader is in the 2K install and you installed this first and then XP afterwards. Then you done a repair install of 2K from the Windows CD, then it’s likely the ntloader files have been replaced with the original 2K ones, which can’t boot XP (XP would have substituted its own for the 2K ones).

You need to replace 2 files in the root of 2K, you’ll find them next to the boot.ini file.
Ntdetect.com and ntldr.

You can get them from the i386 folder on your XP CD
Or download them here http://1gighost.net/jerseyboy/xpquick.zip

 

Definitely worth a try. May be a last ditch effort.

 

thnx, and lesson learned

basically I had 3 working OS's
2HD's

HD 1 had 2 partitions, each partition had XP (primary/logical)
HD 2 had 1 partition with 2000 (primary)

HD1 is the master, and has the boot.ini
both are ntfs

win2000 wasn't working so I did a "repair "

after that I could no longer get into the XP machines

when I select an XP option from the boot menu, I get a win2000 splash screen, then an error.

I don't think theres anything wrong with either OS, just can't boot them
I'll give ur sugestion a try tomorow.

 

Go ahead and replace those two files in the XP install on the primary partition on the master hard drive. It can’t do any harm and may just be your cure. If it was a repair install from the 2K CD that you tried then it sounds good.

Not sure why you are seeing the 2K splash screen. If the above does not work can you post a copy of your boot.ini file. So how did you get 2000 on the second hard drive in the first place? Did you install when it was the master hard drive and then move it to secondary/slave and edit the boot.ini file to include 2K? Can you be more specific on the “repair” you tried on 2k – and did it work?

Another option is to try an XP boot floppy. Download this little app and it will build the floppy for you. Download link It is already set for two XP’s on two partitions on the master hard drive. It will give you a dual boot menu and should boot both of your installs. Just boot the computer with the floppy in the drive.

 

And backup your data ASAP.

 

thnx guys

it worked, i replaced the ntloader on the primary driver an all is good

and I'm now backing up my key!

as for the "repair" i did, no it was not successfull, see this post for details
http://www.windowsbbs.com/showthread.php?t=50984

 

my .02 here only - i'd remove the encryption - or ask why u need it basically. u should be able to setup standard win perms to make them private - default to basic users anyway - and just avoid the encryption all together for future.

 

Now from what I can remember about windows encryption is that it uses the system ID hash number as part of the key generation. So unless your computer generated the same ID for your repair install, I believe that your data is pretty much gone.

I'm probably wrong but I'm sure I read it in some Windows administration guide.

 

yes Dcrypter you are correct - Windows indeed uses User ID [SID's] as part of the key generation but here only boot record was repaired. Windows installation was as it is.