Too Many Local Printers Can Cause Unsuccessful Boot

ID: Q239907

The information in this article applies to:

Microsoft Windows NT Server versions 3.51, 4.0
Microsoft Windows NT Workstation versions 3.51, 4.0
Microsoft Windows NT Server, Enterprise Edition version 4.0
Microsoft Windows NT Server version 4.0, Terminal Server Edition

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

When you reboot your computer, you may receive the following error message:

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

\%winnt%\SYSTEM32\CONFIG\SYSTEM\Hardware Profile/Last Known Good menu

CAUSE

This behavior can occur if there are too many printers installed in Windows NT. Based on the number and types of drivers involved, the problem may start at around 900 printers.

For a detailed description of the underlying problem, please see the following article in the Microsoft Knowledge Base:

Q102721 Err Msg: Windows NT Could Not Start Because the Following...

RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

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 Windows NT 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

Note that this hotfix requires you be running at TSE SP5 in order to install.

The English-language version of this fix should have the following file attributes or later:


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

NOTE: To activate this fix, you must add the following registry entry

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print

named UseSoftwareKey, type DWORD with the value of 1.

If you use the fix you need to make this setting before you upgrade to Service Pack 6. In case you uninstall Service Pack 6 you need to make sure you are still running the fix above.

Windows NT 3.51

A hotfix is not available for Windows NT 3.51.

Windows NT 4.0, Terminal Server Edition

There is a separate hotfix that addresses both local and network printers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q244135 Too Many Printers Can Cause Unsuccessful Boot

WORKAROUND

For workarounds for this problem, please see the following article in the Microsoft Knowledge Base:

Q102721 Err Msg: Windows NT Could Not Start Because the Following...

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

Additional query words:

Keywords : kbenv kbprint winboot
Version : winnt:3.51,4.0
Platform : winnt
Issue type : kbbug