Unsolved
This post is more than 5 years old
2 Posts
0
6872
August 18th, 2005 14:00
Windows 2000 Recovery
I'm sorry if this has been posted but I need information on how to configure the Windows 2000 Recovery.
Whenever I try to start up W2K Pro it says
'Windows 2000 could not start because the following file is missing or corrpupt;\Winnt\system32\config\systemced...'
I have read other threads on how to solve this problem but most of them aren't very well explained in a way i could understand. I had read there is a way to rename some files, but which do I rename and what do i rename it too. Also how would be able to make a copy of it if I cannot log onto windows? Thank You in advance.
Whenever I try to start up W2K Pro it says
'Windows 2000 could not start because the following file is missing or corrpupt;\Winnt\system32\config\systemced...'
I have read other threads on how to solve this problem but most of them aren't very well explained in a way i could understand. I had read there is a way to rename some files, but which do I rename and what do i rename it too. Also how would be able to make a copy of it if I cannot log onto windows? Thank You in advance.
Message Edited by kmle on 08-18-2005 02:39 PM
0 events found
No Events found!


SloMoShun
532 Posts
0
August 21st, 2005 16:00
Error Message: "Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEMced."
Translation: This message, which is sometimes also followed by the error message, "System hive error," indicates that Windows was unable to load the System hive (Windows Registry file) at boot time because the System hive is too big, badly fragmented (scattered across multiple locations on a hard drive), or missing.
This problem occurs during an early phase of the boot process, during which available memory is limited. The Registry must share this limited memory with other boot processes, including loading the kernel (core portion of an operating system), boot drivers, and other components. If the System hive is too large to fit into the available memory, or is so fragmented that it prevents complete loading, you'll see this error message.
Solution: Use the Recovery Console to try to create a nonfragmented (or at least, less fragmented) version of the System hive. Insert your Win2000 installation CD and reboot your computer. At the beginning of the boot process, when you see the option to Press Any Key to boot from CD, press any key. When the Welcome To Setup screen appears, press R to repair Win2000. On the next screen, press C to start the Recovery Console. Select the installation you want to repair. Enter your administrator password at the prompt. The Recovery Console will display a command prompt. Type the following, one line at a time, and press ENTER after each line.
cd System32\config
ren system system.old
ren system.alt systemalt.old
copy system.old system
copy systemalt.old system.alt
exit
reboot
If you still see the error message, you will need to restore a copy of the System hive. Follow the above instructions to boot into the Recovery Console. If you have never created a Registry backup, you will need to restore the default System hive. If you have backed up the Registry, you should restore the System hive from the backup.
If you have never backed up the Registry, type the following at the command prompt, one line at a time, and press ENTER after each line.
copy c:\winnt\repair\system c:\winnt
\system32\config\
y
exit
If you have backed up the Registry, type the following at the command prompt, one line at a time, and press ENTER after each line.
copy c:\winnt\repair\regbackup\system c:\winnt\system32\config\
y
exit
You may need to reinstall any hardware or software you installed after you last backed up the Registry.
If you still cannot boot into Win2000, consider reinstalling Win2000 or editing the Registry to reduce its size.
kmle
2 Posts
0
August 23rd, 2005 02:00
speedstep
11 Legend
•
47K Posts
0
August 25th, 2005 16:00
Get a new drive and try a clean install then once windows is back up and running add the bad drive as a secondary and try to recover data off of it.
Somewhere along the road people have become convinced that
scandisk and chkdsk and reinstalling will fix physical damage on a dying drive.
The truth is It wont and never has and in most cases makes things worse not better.
Drives die after a few years and many new drives only come with a 1 year
warranty. That should tell you a bit about expected life.
sros
120 Posts
0
September 9th, 2005 04:00