Missing or corrupt Windows\System32\Config\System

[AP81]

Hi,

My Dad's PC is booting up to the dreaded "Missing or corrupt c:\windows\system32\config\SYSTEM".

I know from past experience that there is no way to reliably fix this without a relatively recent backup of the registry, which unfortunately I don't have.

Because I have to instruct my Dad on how to fix this over the phone, the easiest thing would be to do a Windows install over the top (without formatting).

Does anyone know if doing this will preserve all his existing information (i.e. MS Outlook profiles, Bookmarks, MyDocs)? Otherwise it will be easier to stick another new HDD in and do a fresh install.

Thanks.

 

[wahnula]

Your dad's files, settings and installed programs should remain intact, but Microsoft does not promise that in their instructions:

http://support.microsoft.com/kb/315341

Every time I've done it it's been fine, but sometimes the corruption carries over to the new installation. It's worth a shot though.

Tony

Users helping Users...

 

[LilBob]

Has your Dad tried using System Restore? Also, has he tried booting up in Safe mode & selecting last good configuration?

http://support.microsoft.com/kb/315222

If that doesn't work, have him do a Repair Install.

http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx

As Tony said, it's not foolproof but I too have never had any problems. He'll lose all service pack updates so have him run Windows Update.

Also, have him run regedit & backup the registry after doing a repair install & updating windows, if all goes well.

http://windowsxp.mvps.org/registry.htm

Hope this helps! Bob

 

[AP81]

Will give the repair install a try. System restore is disabled for performance reasons...maybe worth enabling for him.

Last known configuration doesn't work- I've had this issue before with other computers & the only way I could get this working was with restoring the registry.

Thanks for the help.

 

[wolluf]

This is usually easy to fix if system restore is enabled - you just need to manually 'restore' a recent registry hive set from 'system volume information' - using something like a bartpe disk is good idea (so I always have system restore enabled! - though usually restrict its space usage to 3% max).

There is another 'fix' that sometimes works - boot into recovery console and run chkdsk c: /p (sometimes repairs the errant registry hive file - but not often)