boot error

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

I have the media center edition and came accross a boot error saying a file
is missing or corrupt and refers to the entire system folder. Then suggests
I insert the xp cd and choose to repair... I got my computer from a retail
store who doesn't give you a disc for the operating system, so I need to find
out where I can get the tools necessary to repair. I've tried searching
microsoft's website but its just
about useless when trying to find anything useful I remember a day when it
wouldn't take but 30 seconds to download and burn a repair disc.


thanks
 
Chris

What is your computer make and model?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Acer Aspire
ASE650-U-P9301

Gerry said:
Chris

What is your computer make and model?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
What is the *EXACT* error message? Does your machine have a floppy
drive? Can you borrow a retail XP cd from someone?

John
 
exact error message says:
"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."

No floppy drive but cd burner available as well as plenty of blank cd's =P
I used to have 2 retail cd's of xp but I can't for the world of me find them.
 
It's a well known error see here:

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

If you can borrow a retail XP cd you will be able to fix the problem.
You can also fix the problem by mounting (slaving) the drive in another
Windows 2000/XP computer and moving the files about from the working
computer.

The whole purpose of KB307545 is to replace the broken files in the
System32\Config folder with the ones from the Snapshot folder, then
reboot the computer and do a System Restore to the newest available
date. Basically do step #10 but copy directly to the system32\config
folder (after you move the broken ones to another location):

10. From the Snapshot folder, copy the following files to the
C:\Windows\System32\Config

• _REGISTRY_USER_.DEFAULT
• _REGISTRY_MACHINE_SECURITY
• _REGISTRY_MACHINE_SOFTWARE
• _REGISTRY_MACHINE_SYSTEM
• _REGISTRY_MACHINE_SAM

John
 
Thanks I'll try that after lunch... also for future reference what is it that
generally causes this to happen?
 
Chris

http://www.acerpanam.com/synapse/fo...m/us&siteid=7293&words=all&keywords=&areaid=7

http://www.acerpanam.com/synapse/fo...m/us&siteid=7293&words=all&keywords=&areaid=7

http://www.acerpanam.com/synapse/fo...m/us&siteid=7293&areaid=7&formid=3425#results

There is a hidden partition where the back up system files are kept.

If John's suggestion works make sure you create a system CD so that you
do not get the same problem again.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
PS.

If you do this when the drive is mounted to another machine don't forget
to rename the files (from the Snapshot folder) when you put them in the
System32\config folder, when placed in the config folder the files
replace the existing files named:

DEFAULT
SECURITY
SOFTWARE
SYSTEM
SAM

You must rename the Snapshot files to the same names. I omitted this
*very* important detail in my other post. In the article that is
explained at Part 2, Step#11:

11. Rename the files ...as follows:
• Rename _REGISTRY_USER_.DEFAULT to DEFAULT
• Rename _REGISTRY_MACHINE_SECURITY to SECURITY
• Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
• Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
• Rename _REGISTRY_MACHINE_SAM to SAM

Good luck!

John
 
Back
Top