 |  |  |  |  |  |  |  |
New: What causes corrupt Windows\System32\Config\system file?
 |
Newbie here- couldn't read any replies on archived thread about this. Desktop crashed on boot with no warning, showing Windows unable to load due to this missing or corrupt file.
System was well maintained, clean:
Dell Dimension 4400
Pen 4 1600 megahertz
Installed RAM: 512MB
HD: 40GB 77% free
Windows XP Home w/SP2
No major problem, no hardware problems, no 'noises'-whirring or beeps.
Installation CD will not boot
Possible Dell 4400 motherboard problem?
Keep trying, or remove hard drive, try to recover?
Thanks,
anges35
System was well maintained, clean:
Dell Dimension 4400
Pen 4 1600 megahertz
Installed RAM: 512MB
HD: 40GB 77% free
Windows XP Home w/SP2
No major problem, no hardware problems, no 'noises'-whirring or beeps.
Installation CD will not boot
Possible Dell 4400 motherboard problem?
Keep trying, or remove hard drive, try to recover?
Thanks,
anges35
Hello,
I just had this happen to me and I was able to fix it in 10 minutes. Mine was caused by a power bump right at boot-time and it caused the "%systemroot%\system32\config\system " file to become corrupted. This file is re-written at each boot-up.
What I did was access the drive from another operating system (Win XP) and went to %systemroot%\system32\config\ and renamed the old file from system to system.CRP(for crap
). I them renamed the existing file "SYSTEM.ALT" to "system" (without the quotes) and rebooted my computer. Everything was fine. It's safe to delete the crap file. I'm always in the habit of never deleting, always renaming when I troubleshoot.
In my case it was that fast because my PC dual boots. In your case you can either put the hard drive in another machine that uses NTFS (Win2000 or XP) or find one of those boot disk out there that will boot the machine from a CD and allow read/write access to your hard drive. BartPE or a Linux boot disk are options. Also look at bootdisk.com. He has a real nice ISO file that can be used to burn a boot disk that will allow read/write access to an NTFS partition.
BTW, %systemroot% is a Windows variable for the root (starting) folder of the operating system. I've seen Windows installed in C:\Windows and C:\WINNT.
Good luck!
-Dennis
I just had this happen to me and I was able to fix it in 10 minutes. Mine was caused by a power bump right at boot-time and it caused the "%systemroot%\system32\config\system " file to become corrupted. This file is re-written at each boot-up.
What I did was access the drive from another operating system (Win XP) and went to %systemroot%\system32\config\ and renamed the old file from system to system.CRP(for crap
). I them renamed the existing file "SYSTEM.ALT" to "system" (without the quotes) and rebooted my computer. Everything was fine. It's safe to delete the crap file. I'm always in the habit of never deleting, always renaming when I troubleshoot.In my case it was that fast because my PC dual boots. In your case you can either put the hard drive in another machine that uses NTFS (Win2000 or XP) or find one of those boot disk out there that will boot the machine from a CD and allow read/write access to your hard drive. BartPE or a Linux boot disk are options. Also look at bootdisk.com. He has a real nice ISO file that can be used to burn a boot disk that will allow read/write access to an NTFS partition.
BTW, %systemroot% is a Windows variable for the root (starting) folder of the operating system. I've seen Windows installed in C:\Windows and C:\WINNT.
Good luck!
-Dennis
•
•
•
•
Originally Posted by anges35 
Newbie here- couldn't read any replies on archived thread about this. Desktop crashed on boot with no warning, showing Windows unable to load due to this missing or corrupt file.
System was well maintained, clean:
Dell Dimension 4400
Pen 4 1600 megahertz
Installed RAM: 512MB
HD: 40GB 77% free
Windows XP Home w/SP2
No major problem, no hardware problems, no 'noises'-whirring or beeps.
Installation CD will not boot
Possible Dell 4400 motherboard problem?
Keep trying, or remove hard drive, try to recover?
Thanks,
anges35
Thanks Dennis. I'm going to get the hard drive out and hook it up to my laptop which also has Win XP Home, SP2. I don't have the dual boot option, nor boot disc at this point.
While still looking for a cause, I came across this in a troubleshooting reference: Windows XP doesn't use the Config.Sys which is a DOS start-up file, so it's a bogus message on XP- something else is trying to access it.
I don't know what it was, but had tech out day before putting in new wireless router- this was my first reboot since then!
anges35
While still looking for a cause, I came across this in a troubleshooting reference: Windows XP doesn't use the Config.Sys which is a DOS start-up file, so it's a bogus message on XP- something else is trying to access it.
I don't know what it was, but had tech out day before putting in new wireless router- this was my first reboot since then!
anges35
Hello,
The 'system' file is the root of this problem. (BTW, that file is just called system and does not have any file extension). It is a component of the registry and way too fragile for my liking. It is about 3-4 MB in size and is constantly being written to during a computing session. Since it only takes a couple of messed up bytes to corrupt it, it should have a better level of fallback protection.
There is a Microsoft bulletin on how to fix this with the RECOVERY CONSOLE:
http://support.microsoft.com/kb/307545/en-us
Instructions are straight forward and you wouldn't have to remove your drive, so that is another option.
Config.sys is on the root of your hard drive to allow some older applications to run and need provides a method to tweak DOS settings. It is not a component used for the XP boot cycle.
-Dennis
The 'system' file is the root of this problem. (BTW, that file is just called system and does not have any file extension). It is a component of the registry and way too fragile for my liking. It is about 3-4 MB in size and is constantly being written to during a computing session. Since it only takes a couple of messed up bytes to corrupt it, it should have a better level of fallback protection.
There is a Microsoft bulletin on how to fix this with the RECOVERY CONSOLE:
http://support.microsoft.com/kb/307545/en-us
Instructions are straight forward and you wouldn't have to remove your drive, so that is another option.
Config.sys is on the root of your hard drive to allow some older applications to run and need provides a method to tweak DOS settings. It is not a component used for the XP boot cycle.
-Dennis
•
•
Join Date: May 2005
Posts: 3,204
Reputation: 
Solved Threads: 188
config.sys is NOT config\system, and the msg was about the latter.. config has system, sam, software, security and default -they are all used for startup in XP.
Safety?: well yes, there are excellent levels of protection - just once in a while do a system state backup [like no-one ever does....] to update the files in %systemroot%\repair, [or put the backups into another folder eg repairnew ] in which case the restoration of your sys' health is straightforward; but those five files are also backed up in every system restore point......
The trick is to get at them - recovery console cannot access them inside the System Volume Information folder, and if you restart your sys using an earlier-created set of files then System Restore will not know they exist! .... so you restart your sys using any old set from \repair, then access SVI and copy out the five files from a restore point just previous to the crash to a C: root temp folder, and finally use recovery console to copy em in to where they belong, in system32\config. And restart - your sys is now at the state it was in just before the crash.
Which pretty much goes to prove - do not ever let your sys crash. Ok, it sounds involved, but it's just one step after another on a logical pathway.
Safety?: well yes, there are excellent levels of protection - just once in a while do a system state backup [like no-one ever does....] to update the files in %systemroot%\repair, [or put the backups into another folder eg repairnew ] in which case the restoration of your sys' health is straightforward; but those five files are also backed up in every system restore point......
The trick is to get at them - recovery console cannot access them inside the System Volume Information folder, and if you restart your sys using an earlier-created set of files then System Restore will not know they exist! .... so you restart your sys using any old set from \repair, then access SVI and copy out the five files from a restore point just previous to the crash to a C: root temp folder, and finally use recovery console to copy em in to where they belong, in system32\config. And restart - your sys is now at the state it was in just before the crash.
Which pretty much goes to prove - do not ever let your sys crash. Ok, it sounds involved, but it's just one step after another on a logical pathway.
Last edited by gerbil; Apr 25th, 2007 at 11:19 am.
Deep, deep in the woods, but walking about.
Moral of the story is to always shut down your machine properley
If i am helpful, please give me reputation points.
Hi pls help me:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM
I dont know how... please help
\WINDOWS\SYSTEM32\CONFIG\SYSTEM
I dont know how... please help
•
•
•
•
Originally Posted by gerbil
config.sys is NOT config\system, and the msg was about the latter.. config has system, sam, software, security and default -they are all used for startup in XP.
Safety?: well yes, there are excellent levels of protection - just once in a while do a system state backup [like no-one ever does....] to update the files in %systemroot%\repair, [or put the backups into another folder eg repairnew ] in which case the restoration of your sys' health is straightforward; but those five files are also backed up in every system restore point......
The trick is to get at them - recovery console cannot access them inside the System Volume Information folder, and if you restart your sys using an earlier-created set of files then System Restore will not know they exist! .... so you restart your sys using any old set from \repair, then access SVI and copy out the five files from a restore point just previous to the crash to a C: root temp folder, and finally use recovery console to copy em in to where they belong, in system32\config. And restart - your sys is now at the state it was in just before the crash.
Which pretty much goes to prove - do not ever let your sys crash. Ok, it sounds involved, but it's just one step after another on a logical pathway.
|
Similar Threads
- missing or corrupt \windows\system32\config\system fixes not working (Windows NT / 2000 / XP)
- XP Boot error windows\system32\config\system (Windows NT / 2000 / XP)
- \windows\system32\config\system ?!?! (Windows NT / 2000 / XP)
- windows\system32\config\system (Windows NT / 2000 / XP)
- missing or corrupt : /WINDOWS/SYSTEM32/CONFIG/SYSTEM (Troubleshooting Dead Machines)
- Corrupt: \Windows\System32\ Config\System !!!! Please help! (Windows NT / 2000 / XP)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: Bad Image MOM.exe
- Next Thread: Re-Booting deleted my files
Views: 20858 | Replies: 7
| Thread Tools | Search this Thread |
Latest Windows NT / 2000 / XP Posts
- Today's Posts
- Unanswered Threads
Related Forum Features
Tag cloud for Windows NT / 2000 / XP
.net 3.5 3daccelertion 64bit 2007 2010 a.exe activedirectory address android apache application appstore arm automatically black blue bluescreen boot bsod canonical chinese codeplex combofix computerfreezes cursor deployment desktop desktops dns domain downloads drive eartlink error explorer fax firefox fontmanagers fonts format framework freeze gadgets home install intel laptop latitude linux login mac markshuttleworth microsoft minimalizes monitor netbooks nvidia open opensource operatingsystems options osinstallationproblem osx outlook palm partition patch port printer program proxy raid rds reformat remotedesktop repair replacingraiddrive screen server. sharepoint simplifiedchinese sitetositevpn studios ubuntu unreadable update upgrade videodrivers virus visual volume vpn vulnerability window windows windows7 windowsxp windowsxpnotstartingup. xp
