How to Eliminate a Hung Process Without Restarting the Computer

Last reviewed: February 19, 1998
Article ID: Q171773
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SYMPTOMS

If a program or process is not responding (hung) waiting for user input, and cannot accept input or be terminated, usually the only way to terminate the process is to restart the computer.

WORKAROUND

If you cannot restart the computer to terminate the hung process, use the Kill.exe program from the Windows NT Resource Kit to terminate the process for the hung program without restarting the computer.

Use the process button of Task Manager in Windows NT 4.0 to identify the process ID (PID) of the hung application or, in Windows NT 3.51, use Pviewer.exe or Tlist.exe to identify the process ID.

If the process was started with AT Scheduler, then use AT to schedule the kill command and terminate the hung process.

For example:

   AT 10:30:40  C:<resource kit root>\kill -f  175

NOTE: In many cases the process name will work if it is unique. This will terminate the program with Process ID of 175.

MORE INFORMATION

For additional information, please see the following Microsoft Knowledge Base article:

   ARTICLE-ID: Q138340
   TITLE     : Trouble Quitting Program Started with AT.EXE Scheduler


Additional query words: NT Backup
Keywords : ntbackup NTSrvWkst kbenv kberrmsg
Version : WinNT:3.5,3.51,4.0
Platform : winnt
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.