Corrupt config file cannot be found to be recovered.

Question

Corrupt config file cannot be found to be recovered.

Anonymous

I have had a similar problem to many people, with my computer telling me that the windows\system32\config\system file is corrupt of missing. But, having tried the steps suggested on the support page, I got no further than the very first step as the files I need to copy cannot be found. I tried skipping to repairing them but, again, as they can't be found, they can't be repaired! Don't know what else to try as no commands seem to work with anything in the config folder. May try system restore next but don't even know if that's likely to work?

Any help would be greatly appreciated!

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

Usually the problem is a corrupted file system and not a corrupted or missing file. The message means that XP is trying to start, but just can't find or get to the file. A chkdsk /r will usually clear it right up, but when Googling the error, KB307545 is the first results, so unfortunately, that is where people start sometimes. KB307545 is for a corrupted registry, not an afflicted file system. If the file system is corrupted, you will get frustrated fast with KB307545.

KB307545 really does work if you follow the directions exactly and you don't have a file system problem, but I have never, never, never used it to fix the issue you describe since it is usually never really necessary. Registry file corruption is not usually going to be the cause of the error.

If you want to use KB307545, that is something you would do to just get your system running long enough to do a "real" system restore, but only after running a chkdsk /r from Recovery Console. There is no such thing as a "manual system restore". There is a "get my system functional enough to do a regular System Restore" though. KB307545 and a regular System Restore are not interchangeable. It could also be that your system restore is just totally whacked out from trying too many things.

What happens when you try to boot your system in Safe Mode? What is the last thing you see on the screen?

What does "not loading everything" mean?

If you are using the Recovery Console to implement KB307545 and have already tried it, the renames will not work until you delete the target file(s) from your previous efforts.

If you want to rename fileA to fileB, you need to remove the current fileB first (if there is one). Rename is not the same as copy so if the target file already exists, you cannot just rename another file over the top of it. You will get an error message. You would have to delete the old file first, then rename. That is why yours worked the first time, but not the second time - the file you are trying to rename to already exists. You can't rename over the top of an existing file.

Do, or do not. There is no try.

I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

0 comments

2 additional answers

Answer 1

Thank you for the advice. I tried this and my computer booted up further than before but was not loading everything. So I then thought I might retry my original plan, following the steps on the microsoft support website to repair the files in the config folder. I did this, as I could now access it, but only achieved step one before realising I couldn't access the system volume information folder to continue the process. So now my computer was booting up only in safe mode.

As I'd got to this point and couldn't think of what else to try, I attempted a system restore, which was only possible through the command prompt (following detailed instructions). My computer then appeared to be booting up properly again but got stuck (before even loading start menu etc). So I went back to loading the command prompt from the cd and hoped to attempt another system restore from a point further back but it appears access is now denied. This was previously the case but the steps I was following told me to use the command "ren system sytem.bak", which worked the first time but, second time round, it is telling me the file already exists and I don't know how I can get round this to be able to access another system restore. And am completely stuck for other ideas now! I'm exhausted and I'm sure anyone reading this will be too as I haven't written it very eloquently but any further suggestions would be very very appreciated!

Thanks again.

Answer 2

Was the issue preceded by a power interruption, aborted restart, or improper shutdown? (this includes plug pulling, power buttons and battery removal).

These can cause corruption in the file system which must be fixed before you do anything else.

If any of those events have occurred (or even if they have not occurred), you should verify the integrity of your file system before doing anything else (especially "trying" things).

It makes zero sense to start trying to start trying to edit or copy files around on a hard disk that has a corrupted file system so this must be fixed first using the XP chkdsk program, and running chkdsk on your drives may resolve your issue entirely.

Use the XP Recovery Console to verify the file system on your HDD and correct any problems and then try to boot your system - this may be all you need to do. Or, you are welcome to just start trying things that might work.

Boot into the Windows Recovery Console using a bootable XP installation CD.

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure.

This is not the same as any recovery disks that might have come a store bought system.

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:

xp_rec_con.iso

Download the ISO file from here:

http://www.mediafire.com/?ueyyzfymmig

Use a new CD and this free and easy program to burn your ISO file and create your bootable CD:

http://www.imgburn.com/

Here are some instructions for ImgBurn:

http://forum.imgburn.com/index.php?showtopic=61

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk. These adjustments are made before Windows tries to load. If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually 1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder. This is the same as the

C:\WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt.

First verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems. It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find. It may take a long time for chkdsk to complete or it may appear to be 'stuck'. Be patient. If the HDD light is still flashing, chkdsk is doing something. Keep an eye on the percentage amount to be sure it is still making progress. It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.

Remove the CD and type 'exit' to leave the RC and restart the computer.

You do not have to adjust the BIOS again to boot on the HDD since the CD will not be present.

Do, or do not. There is no try.

I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!

Share via

Corrupt config file cannot be found to be recovered.

2 additional answers