Microsoft KB Archive/165313

{| = Documentation Error for DisableTaskManager Registry Setting =
 * width="100%"|

Last reviewed: December 2, 1997

Article ID: Q165313 The information in this article applies to:
 * Microsoft Windows NT Workstation version 4.0
 * Microsoft Windows NT Server version 4.0
 * Microsoft Windows NT Workstation Resource Kit version 4.0
 * Microsoft Windows NT Server Resource Kit version 4.0

SYMPTOMS
The Windows NT Resource Kit 4.0 documentation includes the information on how to disable the Task Manager in Windows NT 4.0 Workstation and Server with Service Pack 2 or later applied by adding a certain key and value to a user's registry.

However, if the registry setting "DisableTaskManager" with a value of "1" is added to a user's registry as documented in the resource kit, the Task Manager still can be started using any of the methods available.

MORE INFORMATION
The Task Manager in Windows NT 4.0 can be started using any of the following methods:


 * Press CTRL+ALT+DEL to get the Windows NT Security dialog box and click Task Manager.
 * Right-click the Windows NT Taskbar and select the Task Manager menu option.
 * Start the program Taskmgr.exe, which is located in the %systemroot%\System32 folder by default.
 * Press CTRL+SHIFT+ESC.

In the Windows NT 4.0 Resource Kit, the following information is provided in the Registry Entry Help (Regentry.hlp) under the Topic "New Entries for Service Pack 2": System Policy Entries

DisableTaskManager  REG_DWORD Range:  0 or 1 Default: 0 If the value of this entry is 1, Task Manager will not run. Instead, a message appears explaining that Task Manager has been disabled by  the network administrator. This value entry is supported by  Windows NT 4.0 Service Pack 2 and later.

CAUSE
This is a documentation error in the Windows NT 4.0 Resource Kit.

RESOLUTION
The correct spelling for this registry setting is DisableTaskMgr.

You can also use the System Policy Editor (Poledit.exe) to disable the usage of Task Manager. The System Policy Editor is included in Windows NT Server 4.0 and the Windows NT Workstation Resource Kit 4.0.

STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
 * }