Restore an OS to an older state, without booting into Windows?

EnFoRcEr!!

Limp Gawd
Joined
Jan 29, 2003
Messages
472
I'll keep this short and sweet guys. I have a system here that refuses to boot, telling me that the SYSTEM file(registry) is corrupt. The problem here is that even when I copy the backup SYSTEM file over I still get the error. I've tried a system repair and that didn't work. I attempted a fix I found, but for some reason I can't get into the Recovery Console because the admin password keeps saying it's wrong(even though I hacked it and cleared all passwords!).

The question I have is, is it possible to restore an OS to an older state, WITHOUT booting into windows?

HELP!!!
 
What is the error message you are getting? Can you get into safe mode?
 
It's tell me that Windows could not start because the following file is missing or corrupt. It's the WINDOWS\SYSTEM32\CONFIG\SYSTEM file. I copied over the original backup, but that didn't do me any good. :( And no, unfortunately I can't get into safe mode either for the same reason.
 
You may just want to save yourself some frustration and try installing a new HD, loading the OS, and slaving the old drive to move any needed files over. Just a suggestion before you get too far into it.
 
I believe that's actually the registry...so I'm not really sure what file you may have copied over. How about a repair install?
 
I've run a repair install, yes. However, what do you mean when you say restore the registry? How do I go about that?
 
http://support.microsoft.com/kb/307545/ has the step-by-step instructions for restoring the registry in XP when it is preventing your PC from booting.

However - it requires access to the recovery console...so assuming that is still a problem...your options narrow.
 
http://support.microsoft.com/kb/307545/ has the step-by-step instructions for restoring the registry in XP when it is preventing your PC from booting.

However - it requires access to the recovery console...so assuming that is still a problem...your options narrow.

That seems to be my main road block. Thanks for the help guys. If I can ever figure out this password issue, I might be in luck.

Have a great weekend everyone.
 
That seems to be my main road block. Thanks for the help guys. If I can ever figure out this password issue, I might be in luck.

Have a great weekend everyone.

Without the password - you might be able to boot off of some other CD (UBCD, a BartPE CD, etc.) and run step 1 from there. That could then allow you to run step 2 in safe mode and skirt the Administrator password roadblock for now.
 
Without the password - you might be able to boot off of some other CD (UBCD, a BartPE CD, etc.) and run step 1 from there. That could then allow you to run step 2 in safe mode and skirt the Administrator password roadblock for now.

Good idea. I had thought of that but didn't think it would allow me to bypass it. I'll give it a shot. Thanks.
 
I would take that HDD out and plug it up into a different computer as a secondary, take the files you need off of it then reinstall the OS back unto that HDD.

Or go into Safemode or CMD Prompt if that works and remove files unto a Jump-drive.
 
HELP!!!!

EnFoRcEr!!, I've changed your thread title, as the above is not very useful to anyone. And please don't SHOUT!!!!! in thread titles.

You might want to review this article on "How To Ask Questions The Smart Way". It has some good advice on how to word things in forum posts to get the best help.
 
A repair would possibly get the system operational again. A wipe and reinstall would almost certainly get the system operational again. But the problem really is that the problem will likely recur.

It's been my experience that errors like this particular one are software problems with hardware causes. Every time I've seen the "WINDOWS\SYSTEM32\CONFIG\SYSTEM missing or corrupt" error it's been just that. and the hardware causes can be obscure.

Check RAM thoroughly for faults, in case RAM modules aren't playing fair with your mobo. Check the hard drive thoroughly for faults, in case it's either on the way out or simply doesn't like the rive controller. Memtest and the diagnostic tools from the drive manufacturer website are suitable for those two jobs.



On one machine I serviced this problem kept cropping up and the cause eventually proved to be a SATA1 drive which simply didn't like the motherboard's SATA2 controller. On another machine I serviced the cause eventually proved to be a household water supply pump which kept causing power fluctuations.
 
Thanks for the help guys. Booting using the UBCD worked like a charm. I was able to restore the backup registry files manually and everything came out great. The first thing I did after it was done is backup the entire hard drive!!
 
Back
Top