Unable to create a large number of Dynamic Host Configuration Protocol (DHCP) scopes

View products that this article applies to.

This article was previously published under Q216369

Expand all | Collapse all

SYMPTOMS

When you create a large number of Dynamic Host Configuration Protocol (DHCP) scopes with exclusions within each scope, the following error message may be displayed when the computer is restarted twice:

Windows NT could not start because the following file is missing or corrupt:
\%SystemRoot%\System32\Config\System\Hardware Profile/Last Known Good menu

Back to the top

CAUSE

This problem can occur because the scopes, exclusions, or reservations added to the DHCP scopes generate large amounts of KEY data to the registry.

The SYSTEM hive is limited to approximately 11.5 MB in size. This is because the SYSTEM hive and the NT kernel must fit below 16 MB to start the system.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5.

Back to the top

MORE INFORMATION

The resolution to this problem is not found in the DHCP service but rather in how the size of the registry is managed. Documentation on the actual fix is available in the following Microsoft Knowledge Base article:

197632 (http://support.microsoft.com/kb/197632/EN-US/ ) Registry Hive Fragmentation Leads to Excessive Size

Back to the top