Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Error Message: Windows Could Not Start Because the Following File Is Missing or Corrupt: \Winnt\System32\Config\Systemced
Article ID: 269075 - View products that this article applies to.
This article was previously published under Q269075
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
When you restart your Microsoft Windows 2000-based computer, you may receive the following error message:
Note The letters "ced" at the end of the error message are not really part of the error message. The previous screen included these letters and was not completely erased when the error message appeared.
Windows could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEMced
You may also receive the following error message:
System hive error
This behavior can occur if one of the following conditions is true:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To resolve this issue, use the appropriate method.
Remove the Promise Technology ATA66 PCI ControllerIf this issue occurs during the Windows 2000 installation process and a Promise ATA66 controller is installed in your computer, remove the Promise Technology ATA66 PCI controller card, check your BIOS settings to make sure that the IDE controller on your motherboard is enabled, and then run Windows 2000 Setup again.
Restore a Backup of the System HiveIMPORTANT: This procedure will not work on an active directory domain controller, because if you use the REPAIR folder system hive, then you are no longer a domain controller.
Use the Repair Console tool to replace the backup copy of the System hive from the repair folder. If the Repair Console tool is not installed on your computer, you can run it from the Emergency Repair process:
Reduce the Size of the System HiveIf a large number of resources are shared on the computer, the registry may become too large. To resolve this issue, use the following steps.
For additional information about how to obtain Windows XP Setup boot disks, click the article number below to view the article in the Microsoft Knowledge Base:
310994For additional information about System hive limitations in Microsoft Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/310994/EN-US/ )Obtaining Windows XP Setup Boot Disks
302594The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(http://support.microsoft.com/kb/302594/ )The System Hive Memory Limitation Is Improved in Windows Server 2003