You are currently offline, waiting for your internet to reconnect

Windows NT May Not Start with Many DFS Shares

This article was previously published under Q270028
This article has been archived. It is offered "as is" and will no longer be updated.
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
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...
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This information does not apply to Microsoft Windows 2000 because DFS shares are not stored in the SYSTEM registry hive in Windows 2000.

Article ID: 270028 - Last Review: 10/21/2013 00:13:04 - Revision: 1.2

Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kberrmsg kbprb KB270028