Windows NT May Not Start with Many DFS Shares

Article translations Article translations
Article ID: 270028 - View products that this article applies to.
This article was previously published under Q270028
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

Creating a large number of Distributed File System (DFS) shares may prevent Windows NT from starting. The following error message may be generated:
Windows NT could not start because the following file is missing or corrupt:

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

CAUSE

This issue occurs because DFS shares are stored in the SYSTEM registry hive, which may have become too large. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
102721 Err Msg: Windows NT Could Not Start Because the Following File Is Missing or Corrupt...

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

This information does not apply to Microsoft Windows 2000 because DFS shares are not stored in the SYSTEM registry hive in Windows 2000.

Properties

Article ID: 270028 - Last Review: October 21, 2013 - Revision: 1.2
APPLIES TO
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kberrmsg kbprb KB270028

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com