Fix a fragmented or corrupted SYSTEM hive file with Recovery Console

by Jim Boyce | Apr 24, 2002 7:00:00 AM

Takeaway: Problems with a SYSTEM hive file can stop Windows 2000 cold in its tracks. Find out how defrag and the Windows Recovery Console can help solve your hive file troubles.

The Windows 2000 Registry comprises a handful of hive files located in the %systemroot%\System32\Config folder. When Windows 2000 starts, it builds the Registry from these files. One of the Registry files is the SYSTEM hive, and if this hive becomes corrupted or fragmented, it can prevent the system from booting. Here's how you can solve such a problem.

Yet another reason to defrag regularly
When the system first boots, it’s limited to 16 MB of memory. A highly fragmented SYSTEM hive can cause the maximum amount of memory to be exceeded, thereby preventing the system from booting. Defragmenting the file can be a quick fix.

You can defragment the system drive inside Windows 2000, which is a good reason to do it on a regular basis; but if your system has sufficient contiguous free space, you can overcome the problem through the Recovery Console (RC).

Boot the system to the RC and then use the CD command to change to the %systemroot%\System32\Config folder.
Rename the existing SYSTEM file to SYSTEM.OLD.
Use the command COPY SYSTEM.OLD SYSTEM to create a new, unfragmented copy of the SYSTEM hive.
Exit the RC to restart the system.

Check out this article from TechRepublic's Erik Eckel for more information on the Windows 2000 Recovery Console.

Always keep a backup
If creating an unfragmented copy of the SYSTEM hive doesn’t fix the problem, it’s possible that the SYSTEM hive file is corrupted. If you have a good version backed up in the %systemroot%\Repair or %systemroot%\Repair\Regback folder, boot to the RC again and then copy the backup SYSTEM hive file to the %systemroot%\System32\Config folder.

More Windows Registry tips
Check out the following articles and columns to learn more about the Windows Registry:

4 comment(s)