Article ID: 222161
Article Last Modified on 12/27/2006
APPLIES TO
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT 4.0 Service Pack 1
- Microsoft Windows NT 4.0 Service Pack 2
- Microsoft Windows NT 4.0 Service Pack 3
- Microsoft Windows NT 4.0 Service Pack 4
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT 4.0 Service Pack 4
This article was previously published under Q222161
SYMPTOMS
When you start your Windows NT-based computer, a service may not start.
CAUSE
This behavior can occur if a program file in the %SystemRoot% folder has the same name as a Windows NT service that is located in the %SystemRoot%\System32 folder. When this occurs, the program in the %SystemRoot% folder is started instead of the service with the same name.
RESOLUTION
To resolve this behavior, move the file whose name is the same as the service that should start to another folder.
STATUS
This behavior is by design.
MORE INFORMATION
All users who are authorized to log on locally to a Windows NT-based computer have write access to the %SystemRoot% folder and can cause this issue to occur by placing a file in the %SystemRoot folder. To minimize the risk of this issue, you may want to implement stringent security guidelines on your computers running Windows NT. For additional information about Windows NT security, please visit the following Microsoft Web site:
Keywords: kbnofix kbprb KB222161
