From: Rey Santos on
See this if it could help: (see Note below)

How to recover from a corrupted registry that prevents Windows XP from
starting
http://support.microsoft.com/kb/307545

When you try to start or restart your Windows XP-based computer, you may
receive one of the following error messages:
Windows XP could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM

Note:
When you have finished the procedure, a registry is created that you can use
to start Windows XP. This registry was created and saved during the initial
setup of Windows XP. Therefore any changes and settings that occurred after
the Setup program was finished are lost.

--
Rey


"Chris" wrote:

> the name of the file is called system. its in the folder
> C;\windows\system32\config and the back up was supposed to be located in
> c:\windows\repair but its not there. The system is unbootable and i found
> out the file is missing from ubcd4win.
>
> "Ken Blake, MVP" wrote:
>
> > On Tue, 22 Jun 2010 16:38:15 -0700, Chris
> > <Chris(a)discussions.microsoft.com> wrote:
> >
> >
> > > I am trying to fix a computer that has a missing system file. I tried to
> > > copy it from repair\system but its missing from there?
> >
> >
> >
> > What is the name of the file that is missing? Exactly how do you know
> > that it's missing? What problems are caused by the file being missing?
> >
> >
> >
> > --
> > Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
> > Please Reply to the Newsgroup
> > .
> >
From: Jose on
On Jun 22, 10:26 pm, Chris <Ch...(a)discussions.microsoft.com> wrote:
> the name of the file is called system. its in the folder
> C;\windows\system32\config and the back up was supposed to be located in
> c:\windows\repair but its not there.  The system is unbootable and i found
> out the file is missing from ubcd4win.
>
>
>
> "Ken Blake, MVP" wrote:
> > On Tue, 22 Jun 2010 16:38:15 -0700, Chris
> > <Ch...(a)discussions.microsoft.com> wrote:
>
> > > I am trying to fix a computer that has a missing system file.  I tried to
> > > copy it from repair\system but its missing from there?
>
> > What is the name of the file that is missing? Exactly how do you know
> > that it's missing? What problems are caused by the file being missing?
>
> > --
> > Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
> > Please Reply to the Newsgroup
> > .

What file did you determine was missing that started you on this
adventure and is it really missing or is XP just telling you it can't
find it.

If you actually look in the c:\windows\repair folder, what files to
you see?

The files in there are not "backups" they are the original copies from
when XP was installed. What files are in that folder (third time
asking). Sometimes they look a little strange, but they should be
there in some form unless they have been deleted.

Did you make the UBCD4win CD yourself? If yes, then you must have a
bootable XP installation CD from which you could boot the Recovery
Console.

Those files are not supposed to be on the UBCD4win - they are supposed
to be on your afflicted hard disk.

From the XP Recovery Console (still don't know what the original
problem is) you should run chkdsk /r to verify the integrit of the
file system first - before you start trying to copy files around.

If you are trying to fix problems like this:

Windows XP could not start because the following file is missing or
corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

You always need to start with chkdsk /r first - that may fix you right
up. If you are sure your file system mis okay, then you may give
KB307545 a whirl and it works perfectly if you follow the directions
exactly, but you just don't start there.

KB307545 is written to follow if you really do have a corrupted
registry, but you don't know that. All you know is your system won't
boot. That is just the best error message XP can come up with when
the file system is unreadable (I can't find this file) and in need of
repair - you just don't start right in with it until the file system
has been checked out.

Those kinds of messages usually mean XP just can't find the file
usually after a power interruption has corrupted the files system, and
a chkdsk /r needs to be run first. There may really be something
wrong with the registry, but usually there is not (unless you
corrupted it yourself).

You can do all these things from the XP Recovery Console using XP
commands.

I don't remember that UBCD4win has an equivalent of the Windows NTFS
chkdsk /r command (someone will tell me though).

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

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 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 fixing that 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, or create on a bootable XP Recovery Console CD.

This is not the same as any recovery disks that might have come a
store bought system. If you are not sure what kind of bootable CD you
have, make a bootable XP Recovery Console CD and be sure.

You can create a bootable XP Recovery Console CD when no XP media is
available by following the directions in this link:

http://www.bleepingcomputer.com/forums/topic276527.html

After booting into the Recovery Console, you should be in this folder:

C:\WINDOWS

For each of your hard disk partitions, you should then run:

chkdsk /r

For example, from the Recovery Console prompt, enter:

chkdsk c: /r

Let chkdsk finish and correct any problems it might find. It may take
a long time to complete or appear to be 'stuck'. Be patient. If the
HDD light is still flashing, it 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.

The chkdsk /r needs to complete without any errors, so you may need to
run it multiple times until it does.

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

From: PA Bear [MS MVP] on
cf. http://www.ubcd4win.com/

UBCD4Windows Support forums
http://ubcd4win.com/forum/index.php?showforum=38


Chris wrote:
> the name of the file is called system. its in the folder
> C;\windows\system32\config and the back up was supposed to be located in
> c:\windows\repair but its not there. The system is unbootable and i found
> out the file is missing from ubcd4win.
>
>> What is the name of the file that is missing? Exactly how do you know
>> that it's missing? What problems are caused by the file being missing?
>>
>>> I am trying to fix a computer that has a missing system file. I tried
>>> to
>>> copy it from repair\system but its missing from there?

From: Jose on
On Jun 22, 10:26 pm, Chris <Ch...(a)discussions.microsoft.com> wrote:
> the name of the file is called system. its in the folder
> C;\windows\system32\config and the back up was supposed to be located in
> c:\windows\repair but its not there.  The system is unbootable and i found
> out the file is missing from ubcd4win.
>
>
>
> "Ken Blake, MVP" wrote:
> > On Tue, 22 Jun 2010 16:38:15 -0700, Chris
> > <Ch...(a)discussions.microsoft.com> wrote:
>
> > > I am trying to fix a computer that has a missing system file.  I tried to
> > > copy it from repair\system but its missing from there?
>
> > What is the name of the file that is missing? Exactly how do you know
> > that it's missing? What problems are caused by the file being missing?
>
> > --
> > Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
> > Please Reply to the Newsgroup
> > .

So there are no files in the c:\windows\repair folder (that folder is
empty)?

Did you run chkdsk /r from the Recovery Console yet?