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

I received the above message indicating the file:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM

I was going to follow the instructions here:
http://support.microsoft.com/kb/307545

However, it says:
Warning Do not use the procedure that is described in this article if your computer has an OEM-installed operating system.

Which it is.

After searching for another solution and not finding anything, I thought I would at least attempt the above solution.

At the point where it says to copy the SYSTEM file, I get the error:
The system cannot find the file specified.

It also does this for the SECURITY and DEFAULT files.

I checked the DIR listing and all of those files are there.

Before moving on I notice that the next steps are to copy the files from the Repair directory, and there are .BAK files there for all of the necessary files.

So my questions are these:
1.) Is there another process that I should follow, since I am using an OEM machine?

and

2.) If I can use this process, can I just copy the .BAK files from the Repair directory, and not worry about not being able to copy from the config directory?

Thanks in advance for all of your help!

 

1. There is no other recommended for an OEM setup. This is apparently widely used for OEM setups ... I have seen no ill-effects, nor have I read of any.

2. You need to fully understand the whole process ... before proceeding. Maybe get out a pen and paper and draw diagrams ... ? The whole series of steps need to be completed in sequence, as setout, for the best chance of a positive outcome.

It appears that you have a good grasp on how to go about the process, so that is a good, and with understanding and care taken, you should be successful. If you have any specific questions please ask ... and use the aforementioned MS article to reference exactly what you are asking about.

Good luck.

Edit: Oh and btw ... WELCOME to the MajorGeeks forums!

 

Thanks for the welcome!

So I guess what you're saying is, to go ahead with the procedure at the microsoft site?

What about the errors while copying from the CONFIG directory?
It says it cannot find the specified file, but I see that it is there at the indicated path.

Do I need to stop right there and go to plan B? Is there another way to copy said files?

 

Yes, that is what I am saying ... let's continue ....

You said: "Is there another way to copy said files? Do I need to stop right there and go to plan B?"
There is, yes. But, there is little point in changing direction right now. Let's try and see what is actually happening with the way you are doing the steps with the current method.

You said: "What about the errors while copying from the CONFIG directory?
It says it cannot find the specified file, but I see that it is there at the indicated path."
Reassure me that you are here ...
Part 1
Step 5. At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
--------------
You successfully made the temporary directory "tmp".
You successfully copied two of the files, renaming the copies, namely:
software.bak
sam.bak
You were unsuccessful with system.bak, security.bak & default.bak.

Please use the "dir" command to check the content of the tmp directory.
Please use the "dir" command to check the content of the config directory.

Double-check what you have done and what needs to be done and try it again carefully and deliberately. Let me know the details of anything you do that is giving you trouble.

 

no post

 

... to avoid confusion ...

thanks sach2

 

Ok here we go,

Yes I am at Part 1, step 5.

I successfully made the TMP directory, and copied the SAM and SOFTWARE files.

After using the DIR command in the TMP directory, I see that there IS a SYSTEM.BAK file, a well as the SAM.BAK and SOFTWARE.BAK files made previously.

After a second attempt at step 5 the SECURITY file did copy, as well as the DEFAULT file, but still not the SYSTEM file.

Does the fact that I see a file named SYSTEM.BAK in the TMP directory mean that it did in fact work?

Finally, you asked that I check the contents of the CONFIG directory, do you want to see the whole list?

At first glance, I do notice that there are files named:
default
default.log
default.sav
SAM
SAM.LOG
SECURITY
SECURITY.LOG
software
software.LOG
software.sav
system
SYSTEM.LOG
system.sav

Thanks again for your time!

 

Thank you: Very good report and all successful too! Yes to the above question: Where else would it have come from if you did not just put it there?
I think we can move on to the next step now.

You said: "the contents of the CONFIG directory, do you want to see the whole list?"
No, I have seen enough, and thank you for showing detail to me. That is very good and I do like it!
------------------------

Carry on ...
#
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

# Type exit to quit Recovery Console. Your computer will restart.

 

If you have any problem, please use the "dir" command to check for the presence of the required files in the "repair" directory (you may have to use one with a .bak extension if the correctly named one is not present).

When finished, please again use the "dir" command to check that all the required files have indeed been copied to the "config" directory and that they are all named correctly.

Then exit the Recovery Console and restart.
-----------
When performing Part 2, DO NOT BE CONCERNED that things look a little different. This will all be taken care of in Part 3 of the fix.

 

Completed step 5, with a possible problem.

When attempting to delete the system file it says:
The delete operation failed

When attempting to copy system, it said:
The system cannot find the file specified

All other files deleted and copied correctly.

Typed exit and attempted to restart and I still get the same issue as at the start. As expected I guess since it's the system file that is giving me the problem to begin with! :cry

 

Ah! I posted before I saw this.

I don't see a System file in the repair directory, but i do see system.bak.

So, would my command be?:
copy c:windows\repair\system.bak c:\windows\system32\config\system

 

The "system" file needs to be deleted.
Please use "dir" to check the content of "config" directory.
If the "system" file is present, do not proceed until you have deleted it!

Yes, that is correct!

 

I keep entering the delete command and it keeps saying:
The delete operation failed

Do I just keep trying it?

Using the DIR command, it still lists the system file.

On a side note, if I'm in the config directory, do I need to type the whole path?
In other words, if it looks like this?
C:\windows\system32\config>delete system

 

Try renaming the "system" file to something else such as "system.NBG".

ren c:\windows\system32\config\system system.NBG

If that is successful, then delete "system.NBG".

delete c:\windows\system32\config\system.NBG

 

Not sure on that: The Recovery Console is a law unto itself. One way to find out is to try it?
-----------

If still no luck, try changing directory back one level to
C:\windows\system32>

If still no luck, try changing directory back another one to
C:\windows>

Use cd \ or cd ..
to change back one level (note space after cd)
------------

If still no luck, exit the Recovery Console and then start the Recovery Console again and try to delete the "system" file.

 

Tried to rename and it says:
The name specified is not a directory

?

 

Try ...

rename c:\windows\system32\config\system c:\windows\system32\config\system.NBG
-------------

If you are unsure of available commands, type "help" or "/?", for example

rename /?
or
rename help

 

The parameter is not valid. Try /? for help.

It says (among other things):
You cannot specify a new drive path for your destination file.

Which we weren't but it indicates
REN [drive:][path]filename1 filename2

Which we did initially.
:confused

 

We may have a permissions issue here ... ?
Please use "dir" and examine the content of the "config" directory.
Look at the attributes of the "system" file, and let me know what is shown, particularly if s h r

Then exit recovery console and re-start again please, while I work on my reply.

 

Using Recovery Console,
REN needs to be in right folder

C:\WINDOWS\system32\config>
and type
ren c:\windows\system32\config\system system.NBG

such that it looks like this ...
C:\WINDOWS\system32\config>ren c:\windows\system32\config\system system.NBG
---------------

I have booted into RC and tested the above and can confirm that it should work.
btw .... NBG = no bloody good

 

Still getting the same error:
The name specified is not a directory

BTW, looking at the config dir, I see that the attributes for system is a.

EDIT: I also see that there is now a file called systemprofile with an attribute of d.

 

Nice! :-D At first I read it wrong as NBD, I thought it was No Big Deal!

 

Please DOUBLE-CHECK that you have entered the EXACT command that I gave you, from the EXACT directory.

You said: "BTW, looking at the config dir, I see that the attributes for system is a."
OK that is good.
a = ?archive = file ... and there are no attributes to give you any grief.

You said: "EDIT: I also see that there is now a file called systemprofile with an attribute of d."
d = folder/directory ... that's OK

 

Yeah, I did it over and over just to make sure.

I really appreciate all of your help with this, but it's past midnight here and I got to get up early tomorrow.

I'll check back in tomorrow evening, Thanks again!!

 

dunnright00

The predicament: Unable to delete or rename the "system" file.

Explanation: The hard drive has suffered data corruption (the corrupt part just so happens to contain part of the "system" file). The corruption is responsible for the computer not starting, and it is responsible for thwarting your efforts to delete or rename the "system" file.

If we can repair the hard disk corruption/the "system" file ..... we can then delete the "system" file: That is the immediate goal.
----------------------------

So, let's try this ....
Access the Recovery Console by booting from the Windows XP installation CD.
At the command prompt, type chkdsk /r (with a space before the /) and press ENTER key.
There are 5 stages. This might take some time to complete.
Type "exit" to re-start the computer.

If errors were found and/or repaired, it may be prudent to repeat the process, so access Recovery Console again and repeat.

How to use CHKDSK in the XP Recovery Console:
http://pirules3.14.googlepages.com/recovery_console_chkdsk

Description of the Windows XP Recovery Console for advanced users:
http://support.microsoft.com/kb/314058
--------------------------------------------------

Access the Recovery Console by booting from the Windows XP installation CD.
At the command prompt, type
delete c:\windows\system32\config\system

Did it work? Did you get the error message "The name specified is not a directory"?
Type cd C:\WINDOWS\system32\config ENTER
Type dir ENTER
Check using "dir" the content of the "config" directory and confirm that the "system" file is not present (or if it is still present).
-------------------------------------------

If the above step successfully deleted the "system" file .... then continue with the instructions in the MS article.
---------------------

If the above step failed to remove the "system" file, then it will be on with PLAN B.
Visit this link:
Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD
http://www.nu2.nu/pebuilder/

Download, build and burn yourself a bootable BartPE CD.
Check that you can boot the afflicted computer with the CD ..... and then we can begin ....

This is getting interesting: Fortunately there is always more than one way to skin a cat.
I think you will enjoy the next bit.

 

Alright! Just got home, getting ready to start the CHKDSK, now I can't even seem to be able to get it to go into recovery console!

It's taking a REALLY long time to load, and when it finally comes up, it doesn't ask me to boot off of the CD.

It does finally go into the blue-screen windows set-up, and gives me the option to use recovery console, but the command prompt is C:\> and if I try any commands like DIR or CD it says There is no floppy or CD in the drive.

The CD is in there, but it seems unresponsive. It only works after I restart.


I'll it try a few more times. :-/

 

That does not sound like a promising start to the afternoon's work.

 

Just to see what would happen, I tried restarting without the boot disk in.

I get this:
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER

Not good?

 

So, can we use Recovery Console ... or NOT ?

Is it time to go straight to PLAN B ?
----------------------

Plan B ... fyi
How to Create a BartPE Bootable CD Using PE Builder
http://www.winhelponline.com/blog/create-bartpe-bootable-cd-using-pe-builder/

 

Looks like Plan B.

When I attempt to go into Recovery Console, it doesn't seem to be reading the HD. It just gives me the C:/> prompt and won't let me enter any commands. Or rather, I enter the commands but it doesn't connect to windows or anything on the C drive. A DIR command brings up the previous message of no CD or Floppy in the drive.

Also, the CD drive is completely unresponsive while in this mode, but as soon as I enter EXIT, it starts lighting up and will eject.

Heading over to Plan B...

 

Plan B it is then ....

Download, build and burn yourself a bootable BartPE CD.

How to Create a BartPE Bootable CD Using PE Builder
http://www.winhelponline.com/blog/create-bartpe-bootable-cd-using-pe-builder/

My preferred method:
1. Choose to create an ISO file (note the name and location of this, because you will need to know this in the next step)
2. Download, install and use IMGBURN to burn the IMAGE (ISO) to disk (CD).
IMGBURN home page http://www.imgburn.com/
IMGBURN download http://www.imgburn.com/index.php?act=download

 

One possible Issue.
Bart's site reads:

My version is XP Media Center Edition. Will this still work?

 

Perhaps an oversight by Bart, not mentioning the great MCE ?

I see no reason at all that it would not work!

 

Disk made, attempting the boot. It's taking a long time, but I think it's working...

Edit: It's up and asking if I want to start network support.

Standing by...

 

NO networking necessary.
--------------------

First I want you to check that you have had System Restore enabled and that you have a recent System Restore Point (RP) that you can use as a source of the required files.
When the BARTPE Desktop has completed loading ....
GO (Start) > Programs > A43 File Management Utility
Expand the folder tree .... (and I use mine here as an example) to

C:\System Volume Information\_restore{69B16775-E465-4340-B4AD-0A415A48C72D}\ .... (yours will be a different set of characters)

You will see a number of folders, the names beginning with RP followed by three numbers. These folders contain your system restore point information and the highest number represents your latest restore point (the one we want), so open that one.

C:\System Volume Information\_restore{69B16775-E465-4340-B4AD-0A415A48C72D}\RP134\snapshot

Inside, you will see a folder called "snapshot": Open that one and inside you will see the files you need to use to replace the ones removed from the "config" folder earlier. They will look like this:
_REGISTRY_MACHINE_SAM
_REGISTRY_MACHINE_SECURITY
_REGISTRY_MACHINE_SOFTWARE
_REGISTRY_MACHINE_SYSTEM
_REGISTRY_USER_.DEFAULT
(Yes, we will need to change their names when we put them in the config folder.)

Please confirm that this is what you can see on your machine.

 

Sorrry! Again, I will stay out of this thread.

 

Thanks sach2 ... good to see you interested.

 

I think I'm fearing the worst here. I think something happened between last night and this evening when I got home (while the kids were home).

Nothing is expanding in the folder tree in the C drive.

It shows 0 object(s) | C: 0.00KB free

 

Oh dear ... I do believe that calls for another coffee and smoke .... and a good long think!
----------------

Is there anything important on the hard drive that you need to rescue? ... if at all possible now?
--------------

Please what brand of hard drive?

 

Quite a bit actually. Mostly pictures and some financial information.

I was in the process of backing things up. Wish I had finished.

 

Checking on the hard drive.

Could it be a hardware issue? It's weird how it was responding last night and now, nothing!

 

......

 

Seagate Barracuda 7200.8 250 Gbytes

 

Thanks.

BARTPE comes with "Check Disk" .... good ole Bart!

At this stage it's looking more and more like a long shot .... but .... not a whole lot of options left ...

GO > System > Storage > Check Disk > and type in C: and press ENTER key.

"Do you want to fix errors on the disk and
locate bad sectors and recover readable information <Yes/No> ..."
ENTER "Y" .... YES

Will this work ... ? Fingers crossed. Meawhile, I'll make another coffee to steady the nerves and await the news.

 

Dang. I think I'm cursed. It seems to keep getting worse!!

In order to check the HD I unplugged everything and opened it up.
It was pretty dusty, so I vaccumed it out a bit, gently.

Plugged it back it and, nothing. It's not even powering up! I tried different cables, different outlets..

I'm looking inside to see if I jostled something loose, everything seems to be connected ok.

What next?!?! :cry

 

Sometimes there is a small ON/OFF switch on the back of the power supply unit (rear of the box) ... you haven't turned that off and forgotten to turn back on ... ?

I am empathizing ....
-------------

Edit: Oh ... and I don't really want to make you feel worse or unduly concerned, but just in case I don't get to tell you later ...
DO NOT USE a vacuum cleaner anywhere near the insides of a 'puter: Electricity/electrostatic charge/electronic circuitry ... and all that ... not good to get it all mixed up together in the one place.

 

The only switch on the back is the one that changes it from 115 to 230, I'm pretty sure I didn't switch that.

By any chance could it be the motherboard? I'm only thinking because of the progressive decline.
First the system file, then the whole hard drive, then the power itself.

Never noticed it before, but there is a blinking light on the back of the power supply. I don't remember if it was blinking, or always on. When I unplug it, the light blinks slower, and the light is dimmer.

I know, I'm grasping...


Edit:

Really? I thought I was being pretty safe with the long plastic nozzle. I could have sworn I've seen them used at computer repair places.
My bad!

 

That is interesting!
I have never seen one blinking before: Always glowing steadily bright, unless the power is switched off.

I don't know what that could mean.
? The power supply unit (PSU) is defective ... ?
-----------------

Are you sure that you are talking about the PSU here ... ?
You said: "When I unplug it, the light blinks slower, and the light is dimmer."
Surely when you unplug the power supply the light would go OFF ... !

There is ususally a blinking light on an ethernet/broadband connection socket.

 

It is definitely the PSU. I took a short video, I'll post it tomorrow.

Thanks for all the help tonight!!

There hasn't been much success, but I am learning something!

 

That's about the only success we have had here!

Perhaps we were "dead in the water" before we even started: We just didn't know it then? I have no idea what is happening your end now.

My pleasure to try and help: Just sorry things seemed to go from bad to worse ... apparently even without any input from us.