Window cannot start due to system file missing or corrupt message?

[videopho]

Just changed out my new psu and when booting up I encouter this meesage:

Windows can not start because the following file is missing or corrupt: \windows\system32\config\system. Another message gives the following: You can attempt to repair this file by starting Windows Setup using the original Setup CDROM. Select 'r' at the first screen to start repair. Unfortunately, when I access the cdrom with xp on it, it indicates a corrupt file.

Any ideas for repairing this corrupt file will be appreciated.

Note: system was fine prior to swapping out new psu.

 

[Seekermeister]

I'm not sure that I understand...are you booting from the XP CD? There should be no such message if you are. Go into the Recovery Console and run CHKDSK /R...hopefully it will repair the problem.

 

[Smilin]

That corrupt files is actually the system hive of your registry.


Seekermeister has your first step. Drop to recovery console and run a chkdsk (The /P switch should be adequate. If it throws lots of errors you can shift over to the /R switch).

This KB article will hook you up:
307545 How to recover from a corrupted registry that prevents Windows XP from starting
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307545

 

[videopho]

Fixed!
Boot from the original cd window.
Go to Window Set up and ran Recovery mode.
Just manually copied files like this:

create a temp folder:
md tmp
then:
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

Reboot from the hdd, then back to business.

Thanks from everyone's help.

 

[Smilin]

You're only halfway there!!!


The windows\repair version of your hives are leftovers from when you first setup the box. They work but are very old. You'll be missing registry entries from application setup and stuff like that.

I would use those to get booting long enough to grab some hives from a restore point in system volume information. That KB should cover the steps.

 

[greylica]

It's very simple, use another computer to start up with your HDD atached, browse your HDD and find in your hard drive the proper snapshot this way:
He is in \System Volume information
To Browse ( if you can't have access ) you can go to the folder options, and select to see hidden and system files, after this you have to turn off the " use simple file sharing feature ", and this will make you see correctly the folder, after this you will have to take ownership of the folder to find the snapshot, this is made on the properties of the folder, under security, hidden by the "use simple file sharing feature", take the ownership and you will be able to browse.
You can browse the snapshots and find the file of "user" and "system" under \snapsht folder.
Then go to you hard drive in \windows\system32\config

rename the files :
user _> user2
system _> system2

copy the files of the snapshot folder into this folder with the respective names.
If the last change you made to your windows make the crash you can browse the most new snapshots to find the best that makes your system boot up and do not bother your programs.

simple, fast, clean.

But I choose to do not make any repair nevermore in windows systems when I changed to Linux, despite of knowing how, enjoy... Sometimes I think in do not help windozers too, but will not make any difference, I just found my liberty to know how an entire system really function with Linux.
Linux systems never crashed this way in enterprises here in Brazil. And normally, Linux can be fixed by the prompt that most of the people hate to see and use, blaming this is a thing of the past. Mac suffers too, a complete lack of this simple and powerful tool.
At least, we have a chance to do not disassemble the entire system to put the HDD to another computer to fix it, A simple live CD can help to fix it.

Linux, years ahead.

 

[Smilin]

Originally posted by: greylica
Its very simple, use another computer to start up, browse your HDD and find in your hard drive the proper snapshot, he is in \System Volume information
To Browse ( if you can have access ) you can go to the folder options, and select to see hidden and system files, after this you have to turn off the " use simple file sharing feature ", and this will make you see correctly the folder, after this you will have to take ownership of the folder to find the snapshot, this is made on the properties of the folder, under security, hidden by the "use simple file sharing feature"
You can browse the snapshots and find the file of "user" and "system".
Go to you hard drive in \windows\system32\config

rename the files :
user _> user2
system _> system2

copy the files of the snapshot into this folder with the respective names.
If the last change you made to your windows make the crash you can browse the most new snapchots to find the best that makes your system boot up and do not bother your programs.

simple, fast, clean.
But I choose to do not make any repair nevermore in windows systems when I changed to Linux, despite of knowing how, enjoy...
Linux systems never crashed this way in enterprises here in Brazil. And normally, Linux can be fixed by the prompt that most of the people hate.
At least, we have a chance to do not disassemble the entire system to put the HDD to another to fix it, A simple live CD can help to fix it.

Linux, years ahead.

Grelica, take your linux-monkey-loving-ass of the thread before you give someone some data-damaging advice. There is no User hive in system32\config and the user hive has nothing to do with a corrupt system error.

The KB article listed above is all you need Videopho. If you get stuck lemme know. I sit down the hall from the guy that wrote it.

 

[videopho]

Smilin
It's partially true of what you said, "I'm half-way there".
Well I did have to reinstall some drivers (my HDTV tuner, mouse) and some apps (mostly from M/S itself, ie IE7.0). Otherwise and to my surprise, everything else runs like it'd have ever known of what had happened. 🙂.
Couple things I've noticed missing from the Programs's System Tools, and those are:
System restore/backup and Disk Defragmenter.
One thing I do need to yet recover is the restore/backup tool in which I need to figure out how to do it.
I've always used O&O Defrag so the window disk defrag missing is no big deal.
BTW, the rig at fault is my x64 window system.

 

[Smilin]

use the restore point hives and everything will be perfect.


The reason you've had to reinstall some apps is because that 'software' hive contains all their settings and you're using a copy of the hive that existed before they were installed.

I would highly recommend completing part 2.


There is another option not really discussed in the kb methinks:
take your corrupted system hive and load it with regedit. regedit in XP has some auto-repair functionality built in. Just load the hive and then unload it. Boot to recovery console and move it back in place.

See regedit help for more info. Search on "load hive".

sometimes multiple hives get corrupted but there is a good chance that just system is shot so this may be an option for you.

If you have a recent restore point go with that though. KB article shows how. Do this before you go off reinstalling too much...there are risks in getting things mismatched.

 

[greylica]

Yesterday the link went down, but I will tell you the things you ignored of what told before.

Grelica, take your linux-monkey-loving-ass of the thread before you give someone some data-damaging advice. There is no User hive in system32\config and the user hive has nothing to do with a corrupt system error.

The KB article listed above is all you need Videopho. If you get stuck lemme know. I sit down the hall from the guy that wrote it.

NO!!!

Sometimes you fix the system reg file but the problem can be the user reg file too, and its backed up with the snapshot where I am told,
You don't know what you are talking about. You are not a good technician, in a real live probably you will format and reinstall it all again if things go wrong.
There is no data damaging advice like you blame incorrectly, you don't know nothing about windows, and sometimes even if you press the F8 Key to try to Boot up with the last state your system was ok and it just doesn't function, it's a signal that you reg file ( system ) and their last snapshot are corrupted, probably the backed up too.
You only know Windows in theory of what Microsoft is giving, I know in practice.

Uglier than what your wrong " expert " advice is the fact that if he added users after 3 or four months your KB will cause another problem if he encrypted the data for one or another user doc, cause when the machine was first formatted, the users where not there, you cannot recover the same credential recreating a simple name and password your dumb ass, and if there are no previously restore point created by the user, he will be in an abyss.
My process will give him a chance to recover at least a last state where the user credentials are still functioning well, and if one or more users have encrypted data he can log in normally and make a backup. Your process will lost the data of the credential, idiot.

Your Microsoft-KB will recover the first install, but, who need the first install after six month of installing programs your monkey ?

Some times you said I am BS, but the " expert advices " you offer can lead the users to an abyss, like you did here now .
At least, if he haves the tree or four snapshots of the registry he can save his programs and will not have to reinstall it all again and he will not loose the credentials of the other users, the process I told function very well, and you never tried because of you " Extreme KB of what Microsoft give... "

Smilin, you definetly are only a fan of Bill Gates or fan of Microsoft, and it blind your eyes to technical related things. You are not a good technician, you only know the procedures, do not know how it function and what's best to choose at every moment. Not even only the procedures are the best to choose.

Let him try what I am talking, I swear that it will worth, it will save him. without reinstalling any program...

Windows normally store snapshots of the registry files where I told. find it by yourself and you will notice that I am talking truth.

Before offend others, test . You will learn more every day.

 

[greylica]

Better than this, I will post a mini manual of how to Fix it, making the proof of that you are completely wrong, cause I will never tell things that I can't proove.
I will prove for you and help all of the technicians at anandtech, it will be a pleasure.
We will see who is the real monkey.

 

[InlineFive]

Originally posted by: greylica
Better than this, I will post a mini manual of how to Fix it, making the proof of that you are completely wrong, cause I will never tell things that I can't proove.
I will prove for you and help all of the technicians at anandtech, it will be a pleasure.
We will see who is the real monkey.

I eagerly await your manual...

 

[Smilin]

Originally posted by: greylica
Yesterday the link went down, but I will tell you the things you ignored of what told before.

Grelica, take your linux-monkey-loving-ass of the thread before you give someone some data-damaging advice. There is no User hive in system32\config and the user hive has nothing to do with a corrupt system error.

The KB article listed above is all you need Videopho. If you get stuck lemme know. I sit down the hall from the guy that wrote it.

NO!!!

Sometimes you fix the system reg file but the problem can be the user reg file too, and its backed up with the snapshot where I am told,

The user hive exists in system volume info, yes. However it does not get placed into system32\config. Only the machine hives go there. dummy.

You don't know what you are talking about. You are not a good technician, in a real live probably you will format and reinstall it all again if things go wrong.

heh. riiiiiight. that's usually the advice I give around here: format and reinstall. :roll: That was the first thing I was gonna tell him, didn't you know. 😛

There is no data damaging advice like you blame incorrectly, you don't know nothing about windows, and sometimes even if you press the F8 Key to try to Boot up with the last state your system was ok and it just doesn't function, it's a signal that you reg file ( system ) and their last snapshot are corrupted, probably the backed up too.

If you have a missing or corrupt system32\config\system error last know good buys you nothing. Last known good merely references the select key to decide what control set to use. Since all control sets are stored in the same file the corruption of this file prevents last known good from helping. Please o please, tell me more about what you don't know. You haven't given any damaging advice yet, but you are dangerously stupid.

You only know Windows in theory of what Microsoft is giving, I know in practice.

I spent a year in the team that handles this exact support call. Most admins see major incidents several times a year. I fixed several a day. How many machines have you actually worked on with this problem? Does it take you more than one hand to count or not? I've done more than I can even remember. Don't give me some "theory only" hogwash.

Uglier than what your wrong " expert " advice is the fact that if he added users after 3 or four months your KB will cause another problem if he encrypted the data for one or another user doc, cause when the machine was first formatted, the users where not there, you cannot recover the same credential recreating a simple name and password your dumb ass, and if there are no previously restore point created by the user, he will be in an abyss.
My process will give him a chance to recover at least a last state where the user credentials are still functioning well, and if one or more users have encrypted data he can log in normally and make a backup. Your process will lost the data of the credential, idiot.

Your process will simply take a user hive out of a restore point and drop it somewhere where the system will never look.

Your Microsoft-KB will recover the first install, but, who need the first install after six month of installing programs your monkey ?

Learn to read. The first half of that article discusses the repair hives. The second half discusses how get things back to the most recent point possible. Reading comprehension bub. get some.

Some times you said I am BS, but the " expert advices " you offer can lead the users to an abyss, like you did here now .
At least, if he haves the tree or four snapshots of the registry he can save his programs and will not have to reinstall it all again and he will not loose the credentials of the other users, the process I told function very well, and you never tried because of you " Extreme KB of what Microsoft give... "

Actually the KB is for folks like you, not me. I could have written this particular article from memory and even added some things (the KB doesn't even cover whitespace fragmentation, a common cause of this error). A fundamental understanding of how the registry works is all that is required. Your understanding seems to have some major holes in it.

Smilin, you definetly are only a fan of Bill Gates or fan of Microsoft, and it blind your eyes to technical related things. You are not a good technician, you only know the procedures, do not know how it function and what's best to choose at every moment. Not even only the procedures are the best to choose.

What? English dude. Yes, I'm a huge fan of Bill & MS. I would never work for a company I didn't believe in. Beyond that you don't really know anything about me or my troubleshooting so stop talking out of your ass.

Let him try what I am talking, I swear that it will worth, it will save him. without reinstalling any program...

Windows normally store snapshots of the registry files where I told. find it by yourself and you will notice that I am talking truth.

Before offend others, test . You will learn more every day.

*Sigh* Dude, the KB article I showed earlier already mentions where the snapshots are stored. You aren't telling me anything I don't already know. What you are trulying fvcking up is:
1) The destination. The user hive does NOT go into system32\config. That's for system, software, sam, security.
2) The user hive has jack sh1t to do with this problem. The user hive is not even touched until the computer is booted. How the hell would the computer know what user hive to load before logon??? Idiot.
3) If there are problems with other hives (software is commonly corrupted at the same time as system) the steps in that KB cover what to do. One thing at a time though.



I swear I will flame the living snot out of you if you cock off at the mouth again. I'll take a vacation to do it if I have to. The situation here is handled. I'll make sure he gets fixed. Now get off the thread, you are only crapping on it.

 

[Akt]

Hello, I am having a similar problem, however when I try to use boot from the windows CD to repair i get a stop error. I was gonna start a new thread but I luckily saw this one first so ill just copy and paste my problem here.

"Hi, after exhausting all of my resources trying to fix my computer i keep running into dead ends.

Initially while playing a game, my system froze up, restarted, and I started to get the following error:

BIOS ROM checksum error

before even having the option to enter my bios.
So I reflashed my motherboard, and now when windows tries to boot I get the following error:

Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

It instructs me to use my windows setup disk and press 'r' to repair , however when i try to do this, I get the following message before I have the option to repair.

STOP error : 0x0000007E (0xc0000005, 0x80807EE0, 0xF78D1F1C, 0xF78D1C18)

And now im stumped. Even when I put a different hard drive in I get the same errors. I've tried to remove sticks of RAM one at a time thinking it may be bad ram but to no avail. I am not able to boot in safe mode."

Please help

 

[Smilin]

Originally posted by: Akt
Hello, I am having a similar problem, however when I try to use boot from the windows CD to repair i get a stop error. I was gonna start a new thread but I luckily saw this one first so ill just copy and paste my problem here.

"Hi, after exhausting all of my resources trying to fix my computer i keep running into dead ends.

Initially while playing a game, my system froze up, restarted, and I started to get the following error:

BIOS ROM checksum error

before even having the option to enter my bios.
So I reflashed my motherboard, and now when windows tries to boot I get the following error:

Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

It instructs me to use my windows setup disk and press 'r' to repair , however when i try to do this, I get the following message before I have the option to repair.

STOP error : 0x0000007E (0xc0000005, 0x80807EE0, 0xF78D1F1C, 0xF78D1C18)

And now im stumped. Even when I put a different hard drive in I get the same errors. I've tried to remove sticks of RAM one at a time thinking it may be bad ram but to no avail. I am not able to boot in safe mode."

Please help

Is that checksum error still occuring? If so you'll want to get that sorted out. It's not uncommon to see that *once* after flashing.

Things to try:
reset bios to defaults.
Clear via jumper
Re-flash with latest version.
If you still have trouble you may need to ping your mobo manufacturer.

With that out of the way the 'missing or corrupt' message is covered by that KB. The core of what you are trying to do to repair it involves shuffling some files around that exist on your disk. You just need some way to do this while the computer isn't booting. Methods:
1. Recovery console
2. WinPE or other boot disk.
3. Parallel install
4. Mount drive in different box.

If recovery console is giving you fits you can use one of the other methods.

Now about that bugcheck getting into RC..
A bugcheck at that point in setup is going to be caused by one of two things:
1. An inbox driver being loaded that is not compatible with your hardware (the inbox drivers are older and sometimes a firmware update to a device will make it incompatible..perc controllers are notorious for this).
2. The other cause is simply hardware failure. It's pretty tough to bugcheck during setup. There aren't many components running at all.

For #1: What controller are you using? If it's pATA then #2 is more likely. If it's SATA/SCSI then don't count on the inbox driver. Boot with your CD, do the F6 and provide a driver like you are performing a normal setup. Hit R and jump to recovery console once a driver is provided.

For #2: Strip the box down to the essentials to boot. Disable any unnecessary onboard devices. That checksum error may be related but I hope not...it points towards mobo replacement if the earlier steps didn't make the error go away. Memtest. Underclock. Cross fingers.

The ray of hope:
If you got the checksum error out of the way there is a good chance the dirty shutdown is what got you. A chkdsk /p at recovery console might do the trick. (experience says it will do the trick about 1/4 of the time). If you are truly unable to reach RC then look into WinPE or mounting the drive elsewhere to run the chkdsk and KB steps.

 

[Akt]

Smilin,

I stopped getting the checksum error after I reflashed my motherboard.

I simply cannot get to the recovery console, I always get a stop error. Even stripping the rig down to the bare essential hardware, and using a hard drive from an older computer im still getting the same errors. I am using a pATA btw.

 

[Smilin]

ouch. With mass storage out of the picture, hardware failure is about the only thing left. You simply aren't supposed to bugcheck during setup.

A Stop 7E with a 0xC0000005 is a memory access violation. If a particular driver is mentioned it *may* give some indication of what hardware is giving you trouble.

Things to try:
compatibility settings in BIOS
Underclock the cpu+mobo a little.
memtest
RMA 🙁

There is a good chance your OS+files are ok and you'll be able to get the corrupt system message out of the way, BUT.. you likely need to get a hardware issue resolved first.

 

[wiin]

Originally posted by: videopho
Just changed out my new psu and when booting up I encouter this meesage:

Windows can not start because the following file is missing or corrupt: \windows\system32\config\system. Another message gives the following: You can attempt to repair this file by starting Windows Setup using the original Setup CDROM. Select 'r' at the first screen to start repair. Unfortunately, when I access the cdrom with xp on it, it indicates a corrupt file.

Any ideas for repairing this corrupt file will be appreciated.

Note: system was fine prior to swapping out new psu.

Are you still unable to boot?

Have you tried Last Known Good Configuration(I think)? Start your computer and press F8 to get to it.
Failing the above, go to Safe Mode and do a System Restore.