Error message: "Windows 2000 could not start because the following file is missing or corrupt: \Winnt\System32\Config\System" (319011)


The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server, when used with:
    • Microsoft Exchange 2000 Server
  • Microsoft Windows 2000 Server, when used with:
    • Microsoft Exchange 2000 Server
This article was previously published under Q319011

SYMPTOMS

When you restart a Microsoft Windows 2000 Server-based computer, you may receive one or more of the following error messages:
Windows 2000 could not start because the following file is missing or corrupt:

\Winnt\System32\Config\System

-or-

Windows 2000 could not start because the following file is missing or corrupt:

winnt_root\System32\Ntoskrnl.exe

Please re-install a copy of the above file.
Note You may experience this behavior intermittently.

CAUSE

This behavior may occur if McAfee GroupShield Exchange 5.0 for Microsoft Exchange 2000 Server is installed on the computer.

Sometimes, a failed AutoUpdate procedure can corrupt the Windows 2000 boot menu file (Boot.ini).

RESOLUTION

To resolve this issue, use one of the following methods, as appropriate to your situation.

You can start Windows 2000

If you can start Windows, obtain and install Field Patch 1 for GroupShield 5.0 for Exchange 2000. For information about how to obtain and install this field patch, contact Network Associates Inc. (the McAfee parent company).

For information about how to contact Network Associates Inc., click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:

65416 Hardware and Software Third-Party Vendor Contact List, A-K

60781 Hardware and Software Third-Party Vendor Contact List, L-P

60782 Hardware and Software Third-Party Vendor Contact List, Q-Z

You cannot start Windows 2000

If you cannot start Windows, repair the Windows startup environment, and then install the McAfee GroupShield Exchange field patch. To do this, use one of the following methods.

Use a Boot Disk

Note If you received the first error message that is listed in the "Symptoms" section of this article, do not use this method. Instead, go to the "Use the Windows 2000 Emergency Repair Process" method later in this article.
  1. Create a Windows 2000 boot disk that contains the following files:

    Ntldr
    Ntdetect.com
    Boot.ini
    Ntbootdd.sys

    For more information about how to create a boot disk, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    301680 How to create a boot disk for an NTFS or FAT partition in Windows

    101668 How to use a Windows boot disk to prevent boot failure in Windows 2000 or Windows NT

  2. Modify the Boot.ini file to point to the proper hard disk controller and volume for your Windows installation.
  3. Use the boot disk to restart the computer.
  4. Copy the Boot.ini and Ntbootdd.sys files from the boot disk to the system partition on the local hard disk.
  5. Obtain and install the field patch for the McAfee GroupShield Exchange program from McAfee.

Use the Windows 2000 emergency repair process

  1. Start the computer by using the Windows 2000 compact disc (CD-ROM).
  2. At the Welcome to Setup menu, press R.
  3. Press R to select the emergency repair process.
  4. Press M to select Manual Repair.
  5. Press ENTER to perform the selected tasks.
  6. Follow the remaining instructions to repair the Windows 2000 installation.
  7. Obtain and install the field patch for the McAfee GroupShield Exchange program from McAfee.

MORE INFORMATION

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

238359 Differences between Manual Repair and Fast Repair in Windows

242112 Ntdetect fails when computer starts

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The 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.
Modification Type:MinorLast Reviewed:4/17/2005
Keywords:kberrmsg kbprb KB319011
©2004 Microsoft Corporation. All rights reserved.