Article ID: 323148 - Last Review: August 28, 2007 - Revision: 2.2 Windows 2000 Server or Windows 2000 Advanced Server Computer That Is Running Terminal Services Stops Responding Immediately After You Start the ComputerThis article was previously published under Q323148 SYMPTOMSImmediately after you start a computer that is running Microsoft Windows 2000 Server or Microsoft Windows 2000 Advanced Server that also is running Terminal Services in Remote Administrator mode or in Application Server mode, the computer may stop responding. When you restart the server, you may also receive the following error message: Windows could not start because the following file is missing or corrupt: \WINNT\SYSTEM32\CONFIG\SYSTEMced CAUSE
This issue may occur if the Print Spooler service is stopped or turned off on the computer that is running Terminal Services. The Terminal Services service distributes Terminal Services ports for redirected Windows printer mappings, redirected LPT ports, and redirected COM ports from Terminal Services client computers. When the Print Spooler service is stopped or disabled, and a user logs on or logs off a Remote Desktop Protocol session, the inactive Terminal Services ports are collected in the registry. When the following registry key exceeds 12 megabytes (MB), the computer does not start: HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers RESOLUTIONTo resolve this issue, follow these steps:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
| Article Translations
|

Back to the top
