Question Locked

Windows XP couldn't start because the following file is missing or Corrupt:

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Improper shutdown probably casued this, but Windows will not start...getting "Windows XP couldn't start because the following file is missing or Corrupt: \windows\system32\config\system" I know I need to use recovery console to fix, but here's the issue..it won't get to that point. Win XP Cd, boots to it and I get the normal Windows startup blue screen with "Windows setup" at the top left but it just hangs there for hours. I have data on this drive that is needed. I've created a boot disk and the PC boots to it but it doesn't recognise the C: or D: drives as being there. I'm Stuck. Any ideas to try next without data loss would be GREATLY appreciated!

6 replies

by churdoo

Also, is the drive SATA or PATA? If SATA, I've seen some systems where you have to go into CMOS setup and put the SATA controller(s) into a compatibility or legacy mode in order for Windows setup to access them and see attached drives. On these, once XP is setup, updated, and/or repaired, you can switch the CMOS back to the normal setting.

by thechas

First, you likely cannot see your drives from the boot disk as you are booting to DOS and DOS cannot read NTFS format drives. You can get NTFS reader software. Or, install the drive as a slave or external drive on another XP system.

As to recovering your system, you do not want the recovery console. You want to follow the normal install process, select the existing folder for the installation, and when prompted, choose repair rather than a new installation.

Even if you end up performing a clean install of XP, your data files will be intact. The clean new registry however will not know that any of your application software exists.

Chas

by stingray1527

OK, I've removed the drive (ATA), not SATA and slaved it into another system and I can get at everything. My question now is can I rename or copy new system files onto that slaved drive to make it bootable again? If not, at least I can copy off any imprtant folders/files needed onto an external usb HD.

by churdoo

... but I think this is what you're looking for,

http://support.microsoft.com/kb/307545

except that instead of booting to recovery console, this is with the drive slaved in your second machine; substitute the drive letter assigned to the slaved drive in the manual directions of this article. Also, do this from a CMD prompt rather than being tempted to use winders explorer.

by sleepin'dawg

I would suggest trying that first and then hopfully you could use a previous "Restore" point.

The slave idea is a good one but trying safe mode first is simpler and less likely to corrupt anything else. BTW you may be missing or have corrupted more than the above mentioned file so restoring to a a known restore point is a lot easier than searching for corrupted files.

If you can't boot in safe mode then go the slave route.

I would also suggest purchasing a UPS if the "improper shutdown" was the result of a power failure. They're not all that expensive anymore.

[b]Dawg[/b] ]:)

This discussion is closed to new replies.