Error Message: Windows NT Could Not Start Because the Following File Is Missing or Corrupt: \%Winnt%\System32\Config\SystemHardware Profile/Last Known Good Menu (102721)
The information in this article applies to:
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
- Microsoft Windows NT Server 4.0 Terminal Server Edition
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
This article was previously published under Q102721 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 This behavior may occur if the System subkey of the
HKEY_LOCAL_MACHINE hive in the registry is too large to fit into the allocated
memory space. Typically, this part of the registry is too large because
services store a lot of information in their Parameters keys under the
CurrentControlSet\Services key. The following services store large amounts of
data under this key under certain conditions:
- Spooler (number of printers)
- DHCP (number of reservations)
- AT Scheduler (number of jobs)
- DFS (number of shares)
- Other and third-party services
WORKAROUND To try to work around this problem, use an Emergency Repair
Disk (ERD) or reinstall Windows NT. After you recover the computer from a
backup or an ERD, you can either reduce the amount of data that a service
stores or install the hotfix for the spooler service. Windows NT Server or Workstation 4.0To try to work around this problem, obtain the latest service pack
for Windows NT 4.0 or the individual software update. For information about how
to obtain the latest service pack, visit the following Microsoft Web site: For information about how to obtain the individual software
update, contact Microsoft Product Support Services. For a complete list of
Microsoft Product Support Services phone numbers and information about support
costs, visit the following Microsoft Web site: Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest
service pack for Windows NT Server 4.0, Terminal Server Edition. For additional
information, click the following article number to view the article in the
Microsoft Knowledge Base: 152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUSWindows NT Server or Workstation 4.0Microsoft has
confirmed that this is a problem in the Microsoft products that are listed at
the beginning of this article.
This problem was first
corrected in Windows NT Server version 4.0, Terminal Server Edition Service
Pack 6.Windows NT 3.5, 3.51Microsoft has confirmed that this is
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 only
for information that is required to start the computer.
Intel and ARC
(RISC) computers have a design limit such that 16 MB of memory is available at
this stage of startup. The System registry file must 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).
| Modification Type: | Major | Last Reviewed: | 6/24/2004 |
|---|
| Keywords: | kberrmsg kbprb KB102721 |
|---|
|