Microsoft Knowledge Base Email Alertz

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

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 171773 - Last Review: February 23, 2007 - Revision: 2.2

How to Eliminate a Process That Is Not Responding Without Restarting the Computer

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
This article was previously published under Q171773

SYMPTOMS

If a program or process is not responding (hangs) while 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 process that is not responding, use the Kill.exe program from the Windows Resource Kit to terminate the process for the program that is not responding. When you use Kill.exe, you do not have to restart the computer.

Use the process button of Task Manager in Windows to identify the process ID (PID) of the program that is not responding. In Windows NT 3.51, use Pviewer.exe or Tlist.exe to identify the process ID. If the process was started with AT Scheduler, use AT to schedule the kill command and terminate the process that is not responding.

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, click the article number below to view the article in the Microsoft Knowledge Base:
138340  (http://kbalertz.com/Feedback.aspx?kbNumber=138340/EN-US/ ) Trouble Quitting Program Started with AT.EXE Scheduler

APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbenv kberrmsg kbprb KB171773
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate