System will not load Windows XP
Wednesday, June 24, 2009 5:48The other day my mother-in-law dropped off her laptop and said, “it doesn’t work” and left. It took me a day to get to it but when I powered up the system it came up with this message, “windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM”
My heart sank as I had a few other FUN things planned for the evening. This laptop is a Dell Inspiron with the Medial Edition of XP with SP3 installed. I still do not understand why OEM’s or the Best Buys, Office Depot stores, etc. do not install the XP Recovery Console on ALL systems but let’s move on!!!
I had planned on spending a few hours reinstalling the OS (as a last result) and going from there. However, the first thing I usually try is the XP repair option (in the event of corruption or a bad spot on the hard drive), before going further so I put in a Dell OEM XP CD and restarted the laptop. I had already made sure that the BIOS was set to look to the CD drive to boot first, then if none found move to hard drive. The XP setup started and when all of the files loaded it came up and asked me to install or repair and of course I wanted the repair / recovery console option. This brought me to a command prompt, or black dos-like screen.
The system then asked which partition, or which Windows install I wanted to repair (or recover). I chose (1) Windows since it was the only OS on the one partition hard drive and then I was given a command prompt. Here’s is where I was pleasantly surprised!
The first thing I wanted to check was the health of the hard drive so I typed, “chkdsk /R” at the command prompt. After (40) minutes the system was finished with the check disk utility and informed me it had found some “bad data” and moved it. Since the system was now back at the command prompt, I crossed my fingers and restarted. The laptop came up fine, back to the XP Media Center desktop and my work was done. Well, almost. I immediately installed the recovery console option and change the “timeout” to (3) seconds.
My night was salvaged after all and everyone is happy!
I got lucky with this laptop, since the chkdsk issue resolved the problem. This is not always the case and a fresh OS install is all too common. You can search the MS site for articles on restoring the registry, making batch files to save time, etc. Again, I got lucky and expected the worse but it turned out OK.
