Err Msg: Windows NT Could Not Start Because the Following File Is Missing or Corrupt: \%Winnt%\System32\Config\SystemHardware Profile/Last Known Good Menu

ID: Q102721

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Windows NT Server versions 3.5, 3.51, 4.0

SYMPTOMS

When you start your Windows NT-based computer, you may receive the following error message:

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

\%winnt%\SYSTEM32\CONFIG\SYSTEMHardware Profile/Last Known Good menu

CAUSE

The System subkey of the HKEY_LOCAL_MACHINE hive of the registry is too large to fit into the allocated memory space.

A common cause for this problem is a large number of printers installed. Depending on the number of drivers and other services installed, you may see problems when you have more than 900 printers installed.

RESOLUTION

Windows NT 4.0

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp


   Date      Time     File Name       Platform
   -------------------------------------------
   03/31/99  08:11p   Localspl.dll    Intel
   03/31/99  08:09p   Localspl.dll    Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

The only resolution is to use an Emergency Repair Disk, or perform a reinstallation of Windows NT.

After you have recovered the system from a backup or an Emergency Repair Disk, you can install the hotfix.

Windows NT 3.5, 3.51

A hotfix is not available for Windows NT 3.5 or 3.51.

STATUS

Windows NT 4.0

Microsoft has confirmed this to be a problem in Windows NT 4.0.

Windows NT 3.5, 3.51

Microsoft has confirmed this to be a problem in Windows NT 3.5 and 3.51.

MORE INFORMATION

This issue may occur when something is writing too much data to the System subkey in the registry. The System subkey is designed exclusively for information that is necessary to boot the computer.

Intel and ARC (RISC) systems have a design limit such that 16 MB of memory is available at this stage of the boot process. The System registry file has to share the 16 MB with the loader, kernel, HAL, and boot drivers. In some instances, the System subkey may be as large as 13 MB in size (or larger).

Additional query words:


Keywords          : kberrmsg kbbug4.00 ntsetup ntboot kbbug3.50 kbbug3.51 ntregistry NTSrvWkst 
Version           : winnt:3.5,3.51,4.0
Platform          : winnt 
Issue type        : kbprb

Last Reviewed: July 20, 1999