Recover an unbootable windows vista product key, from a corrupt/missing registry hive

[JosephLeo]

Hello TN I have a bit of a problem on my hands here today that I just can't figure out.

In my shop is a clients laptop that fell two storeys out a window during a New Years Eve party. Apparently it was on top of their stereo system by the window being used as an MP3 player and someone knocked over the stereo, which in turn dropped the laptop out the window.

The client has a broken screen and a failing (but still not broken) hard drive so time is of the essence here. I've already ordered a new screen and hard drive however, the thing is I need to perform some data recovery.

Okay, so I've loaded up my boot disks and started recovering personal files from two user profiles, no problem at all. Videos, Music, Pictures, Documents, Emails and Bookmarks all backed up successfully. However, when it came to backup product keys (most important of all the Windows license key) I ran into some trouble.

It turns out that not only is the registry hive not loading, it's not even there at all! I just simply can not find it and I can't run a full data recovery scan on a drive that's ready to fail (it's featuring pre-click'o'death noises) but I need at least the windows key! I also can't check the sticker because THE INK RUBBED OFF! (why doesn't Microsoft laminate their stickers...)

The client already payed $450 ($200 for the screen and $250 for the data recovery) and I would feel awful telling him that he needs to buy a copy of windows as well, especially because he's my first data recovery of the year. So then guys, is there anything I can do here to recover the registry hive or at least the windows key? I only have so much more time to go before this drive completely fails.

 

[ATTech]

Worst case scenario, you have to order the recovery disks from the manufacturer. Shouldn't cost as much as a whole new Windows installation.

 

[JosephLeo]

Worst case scenario, you have to order the recovery disks from the manufacturer. Shouldn't cost as much as a whole new Windows installation.

D'oh, thanks a lot for that reminder. Geez, you think I would remember something like that. That would be a last resort however, and I'd be willing to front the cost of it.

By any chance do you (or anyone else) know of any software dedicated to this type of problem?

 

[MobileTechie]

First thing to do with a failing drive is to image it with something that can deal with errors.

Then you CAN do data recovery on the image.

 

[JosephLeo]

First thing to do with a failing drive is to image it with something that can deal with errors.

Then you CAN do data recovery on the image.

Thing is I don't think it can live that long. It sounds like it's almost "grinding". In otherwords, I'm lucky I got the data I already have off the disk. I have permission to check the files for stability (contract aside, I also ask verbally) and they're seemingly okay from the samples I've tested.

All I really need to get is that damned registry hive and I'm set.

 

[MobileTechie]

Taking an image is the first thing DR pros will do rather than using the file system to find files. It's less stressful on a drive than taking files off because the head is moving sequentially over the disk rather than thrashing about looking items up in the MFT, reading fragmented files etc.

You've already risked the data more than you needed to by getting it off at the file level. Poking around the file system looking for a hive is just more risk. If you can't take any more risk then you might as well stop now. If you can then taking an image is the best and safest method.

 

[othersteve]

If the product key is the last thing you need, this is maybe not so bad.

Try copying the BACKUP registry hives from the system32\RegBack folder and loading those remotely with a utility such as ProduKey (I think it will remotely load hives for this purpose). Then you should have your product key!

 

[JosephLeo]

If the product key is the last thing you need, this is maybe not so bad.

Try copying the BACKUP registry hives from the system32\RegBack folder and loading those remotely with a utility such as ProduKey (I think it will remotely load hives for this purpose). Then you should have your product key!

There are no registry files to backup, they're missing- that's the problem. However, I've managed to solve the problem.

I've just remembered that various data recovery programs allow you to recover specific folders on a hard drive (although, most of the time it doesn't work) and as luck would have it, I was indeed successful in the recovery of the registry files. I've got them right here and now I've got all the CD keys I need.

My method was obviously a little unorthodox, but it worked- although I did create a risk that wasn't needed. My lesson has been learned and I will use better methods next time. So thanks again everyone for your help- I'll be sure to repay the favor somehow.

 

[othersteve]

Oh, I didn't realize that both the main registry keys and the backups were missing. Regardless, glad you solved the problem!

 

[Knightsman]

Taking an image is the first thing DR pros will do rather than using the file system to find files. It's less stressful on a drive than taking files off because the head is moving sequentially over the disk rather than thrashing about looking items up in the MFT, reading fragmented files etc.

You've already risked the data more than you needed to by getting it off at the file level. Poking around the file system looking for a hive is just more risk. If you can't take any more risk then you might as well stop now. If you can then taking an image is the best and safest method.

This is good info. I use Disk Copy for cloning a drive, and can ignore errors, would this be the same lines of what your talking about?