Windows could not start because the following file is missing or corrupt: WINDOWS\SYSTEM32\CONFIG\SYSTEM - fixing this without the OAM disk?

Anonymous

There is microsoft windows XP Professional version 2002 Service pack 3 installed on the computer

I tried to turn on the computer but this came up.

I don't have the original disk to install and fix the problem.

Windows could not start because the following file is missing or corrupt:

WINDOWS\SYSTEM32\CONFIG\SYSTEM

You can attempt to repair this file by starting Windows Setup

Using the original Setup CD-ROM

Select ‘r’ at the first screen to start repair.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I would hold off on a the Repair Install that Elizabeth23 suggested for now.

I think it is time for you to create a bootable Hiren's CD and boot into it Mini XP Mode and choose the Registry repair Wizard.

You already ran chkdsk /r, which is the first thing you should do anyway. Since it didn't work, you may very well need to "go back in time," as it were. Wunders published great instructions for this. Look at his reply in this thread:

http://answers.microsoft.com/en-us/windows/forum/windows_xp-system/error-missing-or-corrupt/a1cf7ecf-e6c8-4546-ab88-f0e5abde7a13?msgId=52ff9278-5721-4b37-8887-700e274493b8

Let us know how you fare.

For simplicity's sake, here are those instructions:

On another machine, create a "Hirens Boot CD": You must burn this with the "Burn Image" feature of a CD Burning program.

Hirens Download: < http://www.hirensbootcd.org/download/ >

[don't get fooled. The actual download link is in light green at bottom next to a disk icon with arrow]

Burning Instructions: <http://www.hirensbootcd.org/burning/>

Once you create the disk, boot your laptop from this disk. At the first screen, select "Mini Windows XP" and let it continue to boot. After it boots, go to the "HBCD Menu" and select:

Programs -> Registry -> Registry Restore Wizard

Follow the prompts in the registry restore wizard, selecting the last restore point before your problem to restore from. When done, shut down your computer, remove the CD, and reboot. If all goes well, you will be back in Windows.

To make sure everything is copacetic, you should perform a "System Restore" using the same restore point you picked using the Restore Wizard:

"How to restore Windows XP to a previous State"

< http://support.microsoft.com/kb/306084 >

0 comments

87 additional answers

Anonymous

2014-11-03T13:20:03+00:00

What was the full content of the system stop message (besides dotdotdot).

I did not give you the full questionnaire about the original message but maybe that will help.

In spite of what the message says about the file being missing or corrupt, that is hardly ever the real problem.

The real problem is usually that XP just can't find the file - usually do to file system corruption.

Your NT File System (NTFS) can get corrupted from a power failure, power interruption, aborted restart, ungraceful shutdown, using the power button/switch, pressing the reset button, plug pulling, battery removal, etc.

Have any of this events occurred prior to this incident?

If the system used to work properly, what do you think happened to the system prior to this incident?

From Hiren's are you able to successfully navigate to the c:\windows\system32\config folder (that is where the registry files are located)? If you can get into the folder, it would seem that XP should be able to get into the folder too.

Another reason for the message is an afflicted c:\boot.ini file that is telling XP to look for the files in the wrong place.

Since we know that in a single partition installation XP doesn't even need a boot.ini file to boot, from your Hiren's navigate to the c:\ folder, locate and rename the boot.ini file to something that you can remember like:

boot.xxx

Then with your c:\boot.ini file "missing" (since it has been renamed) see if the system will boot. XP will complain about the missing file but should still boot just fine (if nothing else is wrong).

If things get worse, just rename the boot.xxx file back to boot.ini
Was this answer helpful?

0 comments No comments
Anonymous

2014-11-02T19:54:26+00:00

After running chkdsk /r a second time it reported NOT finding/fixing any errors. When I rebooted I got the same "Windows could not start..." message. I changed Registry back to most current but then on reboot I got a Blue screen and "system stop..." message. After F8 on boot-up I selected "Last Good Config..." Then system just kept restarting it self over and over. Then went back to next oldest Reg but got System Stop again. So I'm re running chkdsk /r... I've gotten all the data backed up so I'm just about ready to Format C: and reinstall Windows...
Was this answer helpful?

0 comments No comments
Anonymous

2014-11-02T14:45:29+00:00

When troubleshooting, I would not generally make too many changes at the same time... or else you won't know what fixed it.

The chkdsk /r will probably fix your system up, reboot and if things look okay, boot back on Hiren's and Registry Restore Wizard to your latest RP.

It's up to you of course - probably okay no matter what you do :-)
Was this answer helpful?

0 comments No comments
Anonymous

2014-11-02T13:32:53+00:00

Thanks. I guess by my not running chkdsk /r before Registry Restore Wizard was my mistake. I'm running chkdsk now and will rerun until clean. Then should I reset newest Registry before trying a reboot?
Was this answer helpful?

0 comments No comments