Dell Dimension 2400 desktop

[bigstraw]

I have this system running winXp but it won't boot up! Instead I get an error screen saying : "Windows could not start because the following file is missing or corrupt: \Windows\System32\Config\System". Is there any way for me to resolve this issue without reinstalling windows? I have alot of files on this system that I can't afford to lose. Thanks.

[smilingjack]

Are you sure it do not say
ntldr (system file)
They always lose that, prevents them for starting

ntldr

delete the (.txt)
put it in your (ROOT) C:/ drive or where ever you XP is
if that is it it will start

[smilingjack]

it it CONFIG.SYS IT IS A ZERO BUT FILE

Tank may file, change .txt to .zip

uz-zip it

rename is CONFIG.SYS

put it and the (ROOT) C:/

it doen't useuly this file

[Bandit5906]

I have this system running winXp but it won't boot up! Instead I get an error screen saying : "Windows could not start because the following file is missing or corrupt: \Windows\System32\Config\System". Is there any way for me to resolve this issue without reinstalling windows? I have alot of files on this system that I can't afford to lose. Thanks.

You could always take your hard drive and hook it up to another system and repair or save.

[Budreaux]

I have this system running winXp but it won't boot up! Instead I get an error screen saying : "Windows could not start because the following file is missing or corrupt: \Windows\System32\Config\System". Is there any way for me to resolve this issue without reinstalling windows? I have alot of files on this system that I can't afford to lose. Thanks.
You're in for a ride mate. It's more than likely a damaged registry hive.

Use the Recovery Console Tool

To do that, use your Revovery cd for your system to boot into the Recovery Console..You'll need to set your CD drive to the 1st boot device in your Bios settings.

Once you get to the Recovery Console, then chose "R" to repair:

Select the OS you are running.. it;s usually (1)

If you have password protection on your windows, then you will be prompted to enter it now, if you don't then you should get a c:\windows

Type cd system32, and then press ENTER.

Type cd config, and then press ENTER.

Type dir system , and then press ENTER.

You should now get a list of the dir, in which you should see an entry for "system"

Type ren system systemold

This will rename your corrupted system file to systemold..

Type copy c:\windows\repair\system , and then press ENTER.

You should get a "1 file copied" message

Type exit and rebnoot and you should be good to go, once you are back in, you may need to restore to a previous restore point because this procedure repaired your system file back to when Windows was first Installed and succesfully booted.

I hope this helped ya. But, as always, there is possibility it will not work or create further issues, BUT, this issue has been running rampid lately, just doa google search for it and you;ll see. Many folks are claiming various reasons and fixes, but I just outlined what I had to do to fix mine a week or two back.....

REMEMBER.. You renamed your system file to system old, so if you get back in and things don't seem right, you can go back and delte the system file you just copied over and rename the systemold to system and be back to where you started.
Good Luck.

Budreaux

[mruk69]

Here is your solution and it has worked for me numerous times

hxxp://support.microsoft.com/?kbid=307545

Try it, and keep us posted in this thread.

Good Luck

Also install the attatched file this is for everyone, it will backup your registry and will also do it every time you reboot. Change from .txt to exe.

[Budreaux]

I'll be a SOB.....

That is the same procedure I used except I didn;t realize I needed to go in and set my restore points as it showed how to do.

In the end, I decided to reformat and reinstall anyways.. not because I didn;t have access to all my files, but because I wasn;t ahppy with the overall performance afterwards and it was about time to do a clean install.

Had I known that, it would have saved me alot of time.

However, he did say this was a Dell and MS warned not to do this procedure on a system with an OEM installation of Windows...... so, that may put a twist in the works.

Budreaux

[Bandit5906]

Here is your solution and it has worked for me numerous times

hxxp://support.microsoft.com/?kbid=307545

Try it, and keep us posted in this thread.

Good Luck

Also install the attatched file this is for everyone, it will backup your registry and will also do it every time you reboot. Change from .txt to exe.

What happened to the attachment?

[bigstraw]

You're in for a ride mate. It's more than likely a damaged registry hive.
Use the Recovery Console Tool
To do that, use your Revovery cd for your system to boot into the Recovery Console..You'll need to set your CD drive to the 1st boot device in your Bios settings.
Once you get to the Recovery Console, then chose "R" to repair:
Select the OS you are running.. it;s usually (1)
If you have password protection on your windows, then you will be prompted to enter it now, if you don't then you should get a c:\windows
Type cd system32, and then press ENTER.
Type cd config, and then press ENTER.
Type dir system , and then press ENTER.
You should now get a list of the dir, in which you should see an entry for "system"
Type ren system systemold
This will rename your corrupted system file to systemold..
Type copy c:\windows\repair\system , and then press ENTER.
You should get a "1 file copied" message
Type exit and rebnoot and you should be good to go, once you are back in, you may need to restore to a previous restore point because this procedure repaired your system file back to when Windows was first Installed and succesfully booted.
I hope this helped ya. But, as always, there is possibility it will not work or create further issues, BUT, this issue has been running rampid lately, just doa google search for it and you;ll see. Many folks are claiming various reasons and fixes, but I just outlined what I had to do to fix mine a week or two back.....
REMEMBER.. You renamed your system file to system old, so if you get back in and things don't seem right, you can go back and delte the system file you just copied over and rename the systemold to system and be back to where you started.
Good Luck.
Budreaux
Thanks! Was able to solve following this suggestion.

[Budreaux]

Grats, glad we were able to help ya out.

Budreaux