Now the linux wont mount and of the HD's but i dont know much about linux anyway, ill try once again what you said to do because im running out of options. anyway i can call someone on the phone (free) and get some help? I can call using skype if need be, thanks in advance!
This is the error im getting now. I finally got it so it shows a bootloader but only shows the Windows Legacy Longhorn something Pre Vista beta 1 version and when i select it, the next screen says :
Windows Boot manager Error
Status: 0Xc000000f
Info: The selected entry could not be loaded because the application is missing, or corrupt.
File: \NTLDR
Ok, just to catch you guys up.. i dont know what all i did really but now i got it fixed so when it comes up it gives me these three boot choices :
Windows XP Home
0
Microsoft Windows XP Home
And I tried the first 2 and they just hang up on a black screen. The third girls me an al.dll or hal.dll missing or something, says to reinstall windows. HELP!!!
To start, this problem began after running adaware se checking for sypware. I left the comupter while the scan was in progress to return to the blue screen of death. The screen stated windows was shut down to prevent damage to the computer. I tryed to re-boot the machine to another blue screen stating /windows/system32/config/system file was either missing or corrupted. I tryed this solution and found at the BOOTCFG /REBUILD step I received an error message "Failed to successfully scan disks for windows installations. This error may be caused by a corrupt file system, which would prevent Bootcfg from successfully scanning. Use chkdsk to detect an disk errors." I then ran chkdsk /r/f and repaired one or more errors on the disk. I re-ran BOOTCFG /REBUILD and it came back with the same error message! I've also run CHKDSK /P/F and the volume checks out with no errors reported. I'm at a loss to which step to take now as I do not want to re-install the operating system and lose all my saved data. Please help if anyone can. Thanks
I read the thread last night and to no avail. I gues I am going to have to use the recovery disks that were made when the laptop was bought and install the newer drivers and applications again. I think that once I do that I will make a more current Recovery disk.
I am wondering if this problem might be due to our installation of Quickbooks 2007? The problem start two weeks after installation.
Great guide Thrax, many thanks, it will come in handy.
Does anyone know if anything can be done to prevent or reduce the occurences of this type of error? It seems to happen on one of our computers about once every month or two. chkdsk and memtest don't reveal any problems with hd or ram, but I don't know what else to look at. I'm not overclocking or running anything exotic. Would low voltage on the RAM or HD cause this to happen? Any thoughts would be appreciated.
Thanks again, Thrax, for the great guide. It helped me once and certainly saved me a great deal of time. Now, I'm facing something very strange to say the least. The problem began with Adware Ad-Watch running on my system not connected to the internet and suddenly the program told me that something is trying to alter a protected value in the registry. When it asked me for my action I denied the change, and then same thing occurred over and over in the same session the program kept telling me that different registry values are being altered. I kept cancelling the change and then just punched a reboot button on the computer. The Windows reloaded but much to my bewilderment most icons on the desktop as well as all quick launch icons instead of their usual individual signs had the same kind of system icon and Windows cannot recognize how to open any of the programs that usually load at start up, so I have to do it manually i.e. “open with”. Neither could windows recognize how to open any of the system tools programs in start menu. So finally I opened system restore manually and much to my surprise discovered that “no restore points are available”! I have System Mechanic 6 installed which didn’t help either when I tried to restore the registry. So I finally decided to attempt Thrax’s 8 step recovery and though certain that I enter things correctly (since I’ve done it once before), in the first step of ATTRIB –H C:BOOT.INI it tells me that C:BOOT.INI is not found!
So I’m at a loss. If anybody could help figure out what to do, I’d greatly appreciate it. I haven’t lost any data, but sure you know it’s a hustle to have to completely reinstall the system.
I came across your article a bit on the late side I'm hoping I'm not totally hosed.
I have the boot error with a corrupt /config/system file every 6 months or so. Normally what I've done is let the XP SP2 cd work it's way to the install screen where it gives me a choice as to what to do with the detected volumes. I select the "do not format" option, and let the CD scan the install and repair. Upon reboot everything has been honky-dory, until now.
This time it rebooted and gave me the same corrupt error. I let the CD boot and it proceeded to install XP again. However, instead of checking the disk for errors it went straight to copying files. I figured I lost everything.
However, when I rebooted I got a bootloader screen with two XP installs. The 1st in the list was a new installation of XP, the second was the corrupted version. All files from the previous installation appear to be in tact on the drive.
Anyway I can copy files from one folder to the other to get the old install up and running?
Thanks for a great tutorial - I've printed it out for my next bout with this error.
as a follow-up, I checked the drive thoroughly. I lost everything in My Documents, but all else was essentially intact. I tried copying SYSTEM from /system32/repair to no avail. I also tried going into the recovery console from a different win xp cd. Turns out the system is hosed b/c the password file was screwed up in teh process.
I'm investing in a big hard drive to go into my linux server, will schedule periodic backups from various spots, and won't worry about this again.
What's really sad is that, until about 3 months ago, I had assigned My Documents to a folder on my server. If I had done that I would have saved myself a lot of grief.
Great article! I had spent days trying to recover data on an HP laptop with a hive start up issue. Thrax's Repairing Windows in Eight Commands worked great! After working thru the procedure the computer now boots up to windows XP!! Thank you Thrax!!!!!!!!!!!!!!!!!!!!!!
Mike
Minneapolis
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited December 2006
Works!
About a week ago had a big power outage. For some reason - improper settings I guess - the uniterrubtable power supply shut down one of my computers abruptly. After the outage, there were some system problems, which I attributed to operating system files corruption. I performed a checkdisk/repair operation that improved the system operation, but did not repair all the problems.
I just ran through the 8-step Windows repair process outlined in the article. Fixed!
Great Job...I have found it very useful here at work as well.....Also added it to my website for helpful resources. I would love to give you credit for it but im not sure what to use for info.
Travis
0
LeonardoWake up and smell the glaciersEagle River, AlaskaIcrontian
edited December 2006
I would love to give you credit for it but im not sure what to use for info.
Why not a link to the original article at Short-Media?
It's a nicely written, thoughtful approach to trying to find a "magic bullet" for XP boot problems, and while it may fix BOOT.INI and some related issues, it won't fix the problem with a corrupt or damaged registry or hive. Specifically, it won't fix the error "Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
If someone gets an error message on boot up that states, "Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" follow these instructions to fix it:
A. Use "Last Known Good Configuration"
Note: If you've rebooted several times, this probably won't work. Even if you haven't rebooted, it is unlikely to work, but it's worth trying simply because if it does work you'll be back to where you were in a few minutes.
Press any key to restart the computer and hold down the F8 key when the system starts to load to get the Startup screen (Windows Advanced Options Menu). Select "Last known Good Configuration" and press <Enter>
If it doesn't work (you get the same error message), go to B., below. If it works, you'll see the usual splash screen, login, etc. You might have to reload some drivers and/or reinstalled some software. It all depends on what has been added since the configuration the system is using was created.
B. Use The Windows Recovery Console
If you have a Windows XP Startup Floppy Disk, insert it into your Floppy drive and press any key to restart your system. If you don't have a Windows XP Startup Floppy disk, use the Windows XP Install CD. Place it in the CD or DVD drive (or the one with the lowest letter if you have more than one). Press any key to restart your system.
When the system restarts, press the key(s) (usually "Del") needed to go to your system's Setup (may also be called System Settings or something similar). Your computer manufacturer's screen or you computer's initial screen will usually tell you what key(s) to press. If they don't, try "Del". If that doesn't work, check with your manual or manufacturer's website or help line.
At the CMOS Setup/BIOS Settings page, find an entry (usually under Advanced BIOS Features) that tells the system the drive boot sequence and make sure that the first boot device corresponds to the Floppy or CD Drive chosen above. Make a note of any changes so you can change it back later. Exit and Save Settings. The system will restart. If you are booting from a CD, you may have to make that choice or confirm that choice when the system restarts.
After a few minutes, you will see the "Welcome to Setup" screen appear. Press R to start the Recovery Console. Do NOT choose any Windows Install options.
Select the installation that you want to access from the Recovery Console. Usually this is "1". On multi-boot or multi-system configurations, it will vary. Choose the Windows XP configuration you want to work on.
If you are prompted to do so, type the Administrator password and press <Enter>. If you don't have one or are sure there never was one, try pressing <Enter> (= blank). If this doesn't work, you will have to find the Adminstrator password to continue. Note: you can use a variety of tools to discover or delete the Administrator password. However, this process is beyond the scope of this solution.
At the Recovery Console Command Prompt (typically "C:\WINDOWS>"), type the following sequence of commands followed by <Enter>. Always be sure you are in the right directory and always double check your typing before proceeding. If you aren't familiar with DOS or Windows command prompt or commands consider getting someone who is to do this for you.
cd system32\config <Enter> (prompt changes to "c:\windows\system32\config>")
ren system system.old <Enter> (renames the corrupt system file to system.old)
copy ..\..\repair\system <Enter> (copies system in \repair to \config)
dir <Enter> (review files and check that system was copied and system.old exists)
Note: Microsoft recommends replacing all the Registry files, but I always replace only the corrupt one. I do this because the replacement files are usually quite old and replacing all of them means a lot of updating and reinstalling. If the only file reported as damaged, missing, or corrupt is the SYSTEM file, replacing only the SYSTEM file has always worked, it's fast and Windows most often performs all the needed updates when it reboots, bringng you up-to-date quickly.
Type EXIT to restart the system, and eject any Floppies or CDs.
Follow the sequence in 2. and 3., above to change the boot device sequence back to the way it was before.
Window should now boot up as it used to before this error occurred. You will have to reload some drivers. Windows should do this automatically. You will see it finding and loading devices and drivers, usually followed by a prompt to restart. Just follow the prompts and all should be well. You may also have to reinstall some software.
If you have any suggestions, corrections, or comments feel free to e-mail me.
I have had this article fix that error several times. That is why the article was written. I'm sorry, but I have the real-world experience to disagree in this case.
I have had this article fix that error several times. That is why the article was written. I'm sorry, but I have the real-world experience to disagree in this case.
It's not possilbe for your solution to fix a corrupt or missing SYSTEM registry. "Real world experience" or not, it's simply not possible.
-- What does "real world experience" mean anyway? Wanna bet your eight months with Best Buy against my 25 years of fixing computer problems, including 10 years as a Windows beta tester, and seven years with NT and XP? I mean, if you doubt my "real world experience"... :-)
You can easily test it by using the Windows XP Cd to boot, run the Recovery Console, delete the SYSTEM (and SOFTWARE if you think your solution will fix a misisng or corrupt SOFTWARE file) file in the \windows\system32\config folder, and reboot the system. You will get the error I'm referring to. Do your fix and you will still get it. It's as simple as that to test it. Go ahead and try it.
Look, we all fall into the trap of assuming that our "Eureka" will work for everyone else, and find it doesn't. It's no biggie.
Arguing from credentials will do you no good with me because I simply don't care. Twenty-five years vs. my fifteen (Best Buy is a drop in the bucket, and nothing more than an early-life money job -- not a career), none of us are masters at everything. My real world experience simply indicates that I have used this command to solve this error on numerous occasions, as have several people in this thread.
Your error is in the assumption that the SYSTEM error <i>always</i> means a corrupt hive, when that is simply not the case. Many times the registry hive is <b>just fine</b>, and it's as if Windows forgets it's even there. For whatever reason, this command sequence often resolves the issue and is one of many available fixes for the different causes that all exhibit the same symptom.
If you really have a corrupt registry hive, nothing but a backup drop from the WRC or patching in a brand new registry hive will save you, but it's not always the case, nor is that always the required solution.
I appreciate your comments in the thread, criticism is always a good thing, <i>especially</i> from someone who is clearly knowledgeable about the subject matter, but as I initially said, you are only partially correct.
Arguing from credentials will do you no good with me because I simply don't care.
Hey, you brought up the "real world experience" implying you had it and I didn't.
Anyway, I'm not going to get into a pissing contest with you. your claim that your solution fixes the problem I proovided a fix for is false. I'm fine with that. Others can try your fix -- for that specific error -- and then mine if yours doesn't work. I really don't care as long as people get the problem fixed.
Comments
This is the error im getting now. I finally got it so it shows a bootloader but only shows the Windows Legacy Longhorn something Pre Vista beta 1 version and when i select it, the next screen says :
Windows Boot manager Error
Status: 0Xc000000f
Info: The selected entry could not be loaded because the application is missing, or corrupt.
File: \NTLDR
Any help?
Windows XP Home
0
Microsoft Windows XP Home
And I tried the first 2 and they just hang up on a black screen. The third girls me an al.dll or hal.dll missing or something, says to reinstall windows. HELP!!!
Please help.
ps. Is my hard drive shot?
Thanks in advance.
How do I determine if my processor type uses the XD buffer overflow protection? I have a Intel Pentium IIIEB 1000MHz (Coppermine, CuMine, A80526).
Thanks in advance
Have used it successfully twice. Simple and quick. I like that
N
Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM
Please help
I am wondering if this problem might be due to our installation of Quickbooks 2007? The problem start two weeks after installation.
Does anyone know if anything can be done to prevent or reduce the occurences of this type of error? It seems to happen on one of our computers about once every month or two. chkdsk and memtest don't reveal any problems with hd or ram, but I don't know what else to look at. I'm not overclocking or running anything exotic. Would low voltage on the RAM or HD cause this to happen? Any thoughts would be appreciated.
John
So I’m at a loss. If anybody could help figure out what to do, I’d greatly appreciate it. I haven’t lost any data, but sure you know it’s a hustle to have to completely reinstall the system.
Thanks
It looks like you have a serious virus and/or spyware problem, for which you should read my article HERE and follow it very closely.
I came across your article a bit on the late side
I have the boot error with a corrupt /config/system file every 6 months or so. Normally what I've done is let the XP SP2 cd work it's way to the install screen where it gives me a choice as to what to do with the detected volumes. I select the "do not format" option, and let the CD scan the install and repair. Upon reboot everything has been honky-dory, until now.
This time it rebooted and gave me the same corrupt error. I let the CD boot and it proceeded to install XP again. However, instead of checking the disk for errors it went straight to copying files. I figured I lost everything.
However, when I rebooted I got a bootloader screen with two XP installs. The 1st in the list was a new installation of XP, the second was the corrupted version. All files from the previous installation appear to be in tact on the drive.
Anyway I can copy files from one folder to the other to get the old install up and running?
Thanks for a great tutorial - I've printed it out for my next bout with this error.
I'm investing in a big hard drive to go into my linux server, will schedule periodic backups from various spots, and won't worry about this again.
What's really sad is that, until about 3 months ago, I had assigned My Documents to a folder on my server. If I had done that I would have saved myself a lot of grief.
Mike
Minneapolis
About a week ago had a big power outage. For some reason - improper settings I guess - the uniterrubtable power supply shut down one of my computers abruptly. After the outage, there were some system problems, which I attributed to operating system files corruption. I performed a checkdisk/repair operation that improved the system operation, but did not repair all the problems.
I just ran through the 8-step Windows repair process outlined in the article. Fixed!
Thanks, Thrax. Good stuff.
Travis
Eric
If someone gets an error message on boot up that states, "Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" follow these instructions to fix it:
A. Use "Last Known Good Configuration"
Note: If you've rebooted several times, this probably won't work. Even if you haven't rebooted, it is unlikely to work, but it's worth trying simply because if it does work you'll be back to where you were in a few minutes.
B. Use The Windows Recovery Console
Note: Microsoft recommends replacing all the Registry files, but I always replace only the corrupt one. I do this because the replacement files are usually quite old and replacing all of them means a lot of updating and reinstalling. If the only file reported as damaged, missing, or corrupt is the SYSTEM file, replacing only the SYSTEM file has always worked, it's fast and Windows most often performs all the needed updates when it reboots, bringng you up-to-date quickly.
Window should now boot up as it used to before this error occurred. You will have to reload some drivers. Windows should do this automatically. You will see it finding and loading devices and drivers, usually followed by a prompt to restart. Just follow the prompts and all should be well. You may also have to reinstall some software.
If you have any suggestions, corrections, or comments feel free to e-mail me.
It's not possilbe for your solution to fix a corrupt or missing SYSTEM registry. "Real world experience" or not, it's simply not possible.
-- What does "real world experience" mean anyway? Wanna bet your eight months with Best Buy against my 25 years of fixing computer problems, including 10 years as a Windows beta tester, and seven years with NT and XP? I mean, if you doubt my "real world experience"... :-)
You can easily test it by using the Windows XP Cd to boot, run the Recovery Console, delete the SYSTEM (and SOFTWARE if you think your solution will fix a misisng or corrupt SOFTWARE file) file in the \windows\system32\config folder, and reboot the system. You will get the error I'm referring to. Do your fix and you will still get it. It's as simple as that to test it. Go ahead and try it.
Look, we all fall into the trap of assuming that our "Eureka" will work for everyone else, and find it doesn't. It's no biggie.
HTH
Your error is in the assumption that the SYSTEM error <i>always</i> means a corrupt hive, when that is simply not the case. Many times the registry hive is <b>just fine</b>, and it's as if Windows forgets it's even there. For whatever reason, this command sequence often resolves the issue and is one of many available fixes for the different causes that all exhibit the same symptom.
If you really have a corrupt registry hive, nothing but a backup drop from the WRC or patching in a brand new registry hive will save you, but it's not always the case, nor is that always the required solution.
I appreciate your comments in the thread, criticism is always a good thing, <i>especially</i> from someone who is clearly knowledgeable about the subject matter, but as I initially said, you are only partially correct.
Hey, you brought up the "real world experience" implying you had it and I didn't.
Anyway, I'm not going to get into a pissing contest with you. your claim that your solution fixes the problem I proovided a fix for is false. I'm fine with that. Others can try your fix -- for that specific error -- and then mine if yours doesn't work. I really don't care as long as people get the problem fixed.
Please, feel free to have the last word. :-)