Difference between revisions of "Microsoft KB Archive/171773"
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
|Line 72:||Line 72:|
'''AT 10:30:40 C:<resource kit root
'''AT 10:30:40 C:<resource kit root\kill -f 175'''<br />
Latest revision as of 20:09, 20 July 2020
Article ID: 171773
Article Last Modified on 2/23/2007
- 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
This article was previously published under Q171773
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 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.
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.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
138340 Trouble Quitting Program Started with AT.EXE Scheduler
Additional query words: NT Backup
Keywords: kbenv kberrmsg kbprb KB171773