Fixing registry problems via system restore when windows won't boot

[+Warwagon MVC]

Fixing registry problems via system restore when windows won't boot.

Everybody knows about system restore, how you can use it to restore your system back to a particular date when all was well. What happens when windows does not boot, because of a problem with the registry? Everybody?s first thought is either performing a repair installation of windows or formatting and reinstalling. Before going that drastic there is one Hail Mary you can attempt before giving up all hope. To do this you need a copy of bartpe (a version of windows that you can boot off a CD.

http://www.nu2.nu/pebuilder (you can use this free software to make your own)

System restore stores all of the restore points in the root of C: in a folder called ?System Volume Information? (You have to tell windows to show Protected Operating system files).

If you open that folder you will see a folder called ?_restore (and then a bunch of numbers)?. All your machines restore points are stored there. The restore points all share a common name, the letters RP and then a number (example RP143). The numbers themselves don?t really tell you when that restore point was created, but the time stamp does. So it?s best to view by details and arrange by date. So you pick a RP folder corresponding by the date you want to go back to and open it up. Every restore point has a ?Snapshot? folder. This folder contains a backup of the system registry the day the restore point was created.

All the registry backups start with the name _Registry_User followed by the name of the registry file. Example _REGISTRY_MACHINE_SYSTEM. (all that file needs is a little rename love?n and it will be as good as new).

Windows stores all of its registry entries in c:\windows(or winnt)\system32\config. So it?s best to backup that folder up before making any changes. After that?s done it?s a good idea to rename the current registry entries to something else, like system to systemold. Now return to your ?Snapshot? directory and copy all backed up registry entries and paste them in c:\windows(or winnt)\system32\config.

All it takes now is just a little renaming. Let?s take system for example. The backup of the system registry file is called _REGISTRY_MACHINE_SYSTEM. Right click it and rename it to what the old file was called. In this case the file was called just system with no file extension. The same goes for the rest of the registry files. The most common registry files to get you back up and running are, System,Software,Security,SAM and Default. I usually just restore all of them.

Once complete reboot your machine. If all goes well the once unbootable windows installation should come back to life, if all that was wrong was the registry. This has worked on more than one occasion, when the fate of a windows install was looking pretty bleak.

Edited June 14, 2012 by warwagon

[APK]

Excellent technique man, haven't had the need to try it, but it sounds QUITE logical & solid...

(Kudos to you!)

:)

* They ought to "sticky thread" this one... imo, @ least!

HOWEVER - wouldn't RECOVERY CONSOLE (free, as in included with your Operating System CD/DVD already) allow for the SAME THING?

(E.G..-> backing up originals, renaming files, & Copy/overwrite of corrupt ones)

I.E.-> It's QUITE POSSIBLE, bart's PE builder is NOT required!

HOWEVER - you may be correct: It's possible that the registry hives are LOCKED, even if only in part, while RC operates too & a 3rd party tool MAY be needed (since it is NOT "Windows itself" running & thus, not locking registry hives).

(Other tools could possibly manage it as well - such as "System Lifeline" by the folks that produce ONTRACK utlities - this is NOT a std. command processor, & it works while windows is booting. prior to the Windows OS Explorer.exe shell taking effect... & probably does NOT "lock" the registry hives against overwrites too).

APK

P.S.=> Since I liked it, even though it's only based on "theoreticals" @ this point (imo & experience because I have NOT had to use it, but it sounds logical enough)? You get a "5 stars" out of me for a rating... apk

Edited March 31, 2008 by APK

[+Warwagon MVC]

Excellent technique man, haven't had the need to try it, but it sounds QUITE logical & solid...

(Kudos to you!)

:)

* They ought to "sticky thread" this one... imo, @ least!

HOWEVER - wouldn't RECOVERY CONSOLE (free, as in included with your Operating System CD/DVD already) allow for the SAME THING?

(E.G..-> backing up originals, renaming files, & Copy/overwrite of corrupt ones)

I.E.-> It's QUITE POSSIBLE, bart's PE builder is NOT required!

HOWEVER - you may be correct: It's possible that the registry hives are LOCKED, even if only in part, while RC operates too & a 3rd party tool MAY be needed (since it is NOT "Windows itself" running & thus, not locking registry hives).

(Other tools could possibly manage it as well - such as "System Lifeline" by the folks that produce ONTRACK utlities - this is NOT a std. command processor, & it works while windows is booting. prior to the Windows OS Explorer.exe shell taking effect... & probably does NOT "lock" the registry hives against overwrites too).

APK

P.S.=> Since I liked it, even though it's only based on "theoreticals" @ this point (imo & experience because I have NOT had to use it, but it sounds logical enough)? You get a "5 stars" out of me for a rating... apk

True you don't need bartpe. But with the recovery console you have to type out the whole file names. They can be quite long. yes it can be done. BartPE is easier

[APK]

True you don't need bartpe.

Ah, THAT'S what I was wondering & it appears THERE IS NOTHING LOCKING THE REGISTRY @ THAT POINT (while in RC)... that's what I needed to know!

I was unsure here on this note, thanks for seconding me on it & removing my doubts @ this point.

(Heh, I would try to "experiment" here, but... I only have 1 system now, & trying to pull a "radical experiment" on it, after it has been up & running on Windows Server 2003 since 2003 would be a HUGE risk imo... one I would rather NOT gamble on!)

BUT, you have "had the balls" to try it apparently!

(& that earns your 5 star rating from me @ least, on that merit alone (well, that & the fact your technique sounded logical as all get out too!)).

The thing is, over on "my side of the fence", is:

I don't dare "risk" this setup - TOO many years poured into it, very fine-tuned, secured, & much reorganization/personalization into it etc. et al!

(Well, then again, I have an Acronis TrueImage backup I could return to that IS current, but, would take me about 1 hr. to reinstall the OS, install Acronis TrueImage, & then run the restore from it also)

Ah heck, I'll admit it - it's just me being a coward is all, lol!

But with the recovery console you have to type out the whole file names. They can be quite long. yes it can be done. BartPE is easier

Easier = GOOD!

:)

* RC is "primitive" in MANY respects, such as its copy command being a pain too (so, I hear your "pain" when you mention typing things out in it, & more), but, it does do the job well enough, but as you say, sometimes NOT as easily as other things can.

APK

P.S.=> What I am wondering @ this point, & perhaps you can help here? Is IF there is an "SDK" for Windows RECOVERY CONSOLE, because this has given me an idea... that is to write up a small app for RC that will allow .reg file merges. Do you know if MS puts out a SDK for RC? Thanks... apk

[NateB1]

Note that this is unnecessary in Vista - just insert the operating system DVD, choose "repair my computer", and the DVD will automatically restore the registry. I've had it do this when my registry became corrupted (a friend was over, and he accidentally flipped the power supply switch while the computer was booting. Not good)

[+Warwagon MVC]

Note that this is unnecessary in Vista - just insert the operating system DVD, choose "repair my computer", and the DVD will automatically restore the registry. I've had it do this when my registry became corrupted (a friend was over, and he accidentally flipped the power supply switch while the computer was booting. Not good)

Plus in Vista and 7 under the c:\windows\system32\config folder there is a folder in their called regback. So if you wanted to do it yourself, all you have to do is back up your original ones. and just copy and paste the contents of regback, into the system32/config folder and boom! Done!

[Singh400]

Plus in Vista and 7 under the c:windowssystem32config folder there is a folder in their called regback. So if you wanted to do it yourself, all you have to do is back up your original ones. and just copy and paste the contents of regback, into the system32/config folder and boom! Done!

Only took you 3+ years to reply mate. Gotta be a record, right? :D

[dankduke]

okay so if i just use BartPE Live BootCD

this will work?

i also can buy Spotmau Power Suite Golden Edition which i dont mind at all

im willing to do anythign to get this corrected today!!

thanks so much honestly greatly appreciate.