File Missing or corrupted

  • Thread starter Thread starter Dean Black
  • Start date Start date
D

Dean Black

A friend has a computer with XP on it.
She got this error message on boot

File missing or corrupted windows\system32\config\system

She tried a repair install without success. She had another blank HD and she
did a complete install on it thinking that she could run her programs that
were on the first disk. What she ended up was a system with dual boot and 2
copies of XP. The new install boots ok but not the original one.

Two questions
How to repair the first install with the error message.
How to get rid of the dual boot afterwards.

TIA
Dean
 
Dean Black said:

A friend has a computer with XP on it.
She got this error message on boot

File missing or corrupted windows\system32\config\system

She tried a repair install without success. She had another blank HD and she
did a complete install on it thinking that she could run her programs that
were on the first disk. What she ended up was a system with dual boot and 2
copies of XP. The new install boots ok but not the original one.

Two questions
How to repair the first install with the error message.
How to get rid of the dual boot afterwards.

Try a boot into Safe Mode, by hitting F8 just before the "Starting
Windows" screen would appear (takes a bit of practice).
Choose LAST GOOD.

If that isn't applicable, use a working PC to read these sites...

How to Recover from a Corrupted Registry
http://support.microsoft.com/default.aspx?scid=kb;en-us;q307545
describes a three-step process to extract a copy of the registry
from the System Restore SVI folder.

http://WWW.WEBTREE.CA/windowsxp/ (repair console/restore tutorial)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314874
http://www.kellys-korner-xp.com/xp_sys32.htm

After your system is restored, the ERUNT utility available here may
make it easier to fix the problem if it recurs...
http://HOME.T-ONLINE.DE/home/lars.hederer/erunt

If the problem persists, try swapping current RAM (even if it checks
good) for a single, high-quality 512Mb chip. XP reportedly is sensitive
to memory timing.
 
Ok, we all know how to fix this problem by now BUT what is causing the
problem.??? So we don't have to keep doing this. Thanks, Mike
 
Back
Top