WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is corrupted

[Juan I. Cahis]

Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Guest]

Hi Juan,

I don't know the answer to question #1, but the answer to question #2 is
this MSKB article:
How to recover from a corrupted registry that prevents Windows XP from
starting
http://support.microsoft.com/kb/307545
Note that the MS methodology is not to be used for OEM-installed operating
systems....in that case, the user should contact the computer manufacturer's
tech support for assistance.



Regards,

 

[neil]

This is Microsoft's answer
http://support.microsoft.com/kb/307545/en-us

Neil
Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Elmo]

Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?

The file "System" was probably damaged during a write function, probably
as the machine was shutting down.

2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.

MS would have you use the Restore Console, rename the registry files
from a CMD prompt, then replace the files with the backup versions. The
one time I had to do that, I replaced only the damaged file, "System".
After the reboot, I had to remove SP2, which was installed, yet I was
getting warnings that it wasn't. I then reinstalled SP2 and,
surprisingly, it worked!

 

[Juan I. Cahis]

Dear Elmo, do you know where Microsoft store the backup versions?

The file "System" was probably damaged during a write function, probably
as the machine was shutting down.


MS would have you use the Restore Console, rename the registry files
from a CMD prompt, then replace the files with the backup versions. The
one time I had to do that, I replaced only the damaged file, "System".
After the reboot, I had to remove SP2, which was installed, yet I was
getting warnings that it wasn't. I then reinstalled SP2 and,
surprisingly, it worked!

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

Unbelievable!!!!!

ERUNT, or a similar utility, should be in every computer.

This is Microsoft's answer
http://support.microsoft.com/kb/307545/en-us

Neil
Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Kelly]

To fix the "windows\system32\config\system file is mising or corrupt" where
Xp wont boot:

Go to Recovery Console and type:

cd system32\config
ren system system.old
ren system.alt systemalt.old
copy c:\windows\repair\system
copy c:\windows\repair\regback\system
exit

Recover from a Corrupted Registry Preventing Win XP from Starting
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307545

Added info:

Re-extract the files 'NTLDR' and 'ntdetect.com' from the XP CD.

(CD Boot - Recovery Console Prompt)

copy X:\i386\NTLDR C:\
copy X:\i386\NTDETECT.COM C:\

Cannot Start Windows XP if the System or Software Hive Is Missing or Damaged
http://support.microsoft.com/default.aspx?scid=KB;en-us;q303012

SystemRoot\System32\Config\SYSTEM
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q314874

Corrupt Hive
http://www.kellys-korner-xp.com/xp_sys32.htm

How to Recover from a Corrupted Registry
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307545

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm


Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Bruce Chambers]

Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?

How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;822705

2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.

How to Recover from a Corrupted Registry that Prevents Windows XP from
Starting
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545




--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

 

[Patrick Keenan]

Dear Elmo, do you know where Microsoft store the backup versions?

==========

The locations of the backup files are identified in this document:

http://support.microsoft.com/kb/307545/en-us

The restore points are in the System Information folders, and you may need
to do a bit extra to gain access to them.

This happens sometimes, yes. If it happens frequently, consider checking
the condition of the hardware and how you're using it. '

HTH
-pk

==========

The file "System" was probably damaged during a write function, probably
as the machine was shutting down.


MS would have you use the Restore Console, rename the registry files
from a CMD prompt, then replace the files with the backup versions. The
one time I had to do that, I replaced only the damaged file, "System".
After the reboot, I had to remove SP2, which was installed, yet I was
getting warnings that it wasn't. I then reinstalled SP2 and,
surprisingly, it worked!

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[M.I.5¾]

Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

----------------

If English is not your native language, then it is actually quite
impressive - as good as many native English speakers who post here. Even
your grammatical error in the title of you post is used by some English
speakers.

I point it out purely because my experience of people learning English is
that they like to know. We would not say "WinNP do not boot ...", but
rather "WinNP does not boot .." which abbreviates (or contracts if you
prefer the American term) to "WinNP doesn't boot ...".

Good luck with your further English studies.

 

[Juan I. Cahis]

It is the first time that this problem happens to me in years. But I
was shocked about the painful consequences that it would have had for
me, if I didn't had installed previously ERUNT, and used it in a daily
basis.

Dear Elmo, do you know where Microsoft store the backup versions?

==========

The locations of the backup files are identified in this document:

http://support.microsoft.com/kb/307545/en-us

The restore points are in the System Information folders, and you may need
to do a bit extra to gain access to them.

This happens sometimes, yes. If it happens frequently, consider checking
the condition of the hardware and how you're using it. '

HTH
-pk

==========


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

 

[Juan I. Cahis]

Thanks a lot!!!!!

Dear friends:

During a normal boot procedure, I received the following message:
"WinXP don't boot because C:\WINDOWS\SYSTEM32\CONFIG\SYSTEM is
corrupted".

I solved the problem, because I use ERUNT daily, so I booted to the
recovery console and used ERUNT to restore the Registry.

But I have two questions:

1) Why this problem did happen?
2) Which is the methodology recommended by Microsoft to
survive in that event, for the majority of users that they don't use
ERUNT? Please note that selecting the "last good configuration" did
the same error message, which is a logical consequence if you have a
corrupted Registry.


Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!

----------------

If English is not your native language, then it is actually quite
impressive - as good as many native English speakers who post here. Even
your grammatical error in the title of you post is used by some English
speakers.

I point it out purely because my experience of people learning English is
that they like to know. We would not say "WinNP do not boot ...", but
rather "WinNP does not boot .." which abbreviates (or contracts if you
prefer the American term) to "WinNP doesn't boot ...".

Good luck with your further English studies.

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Note: Please forgive me for my bad English, I am trying to improve it!