Problem:
Task Manager and taskkill both cannot kill a process, even with the /f argument.
In this case, the process is Virtual PC 2004 after a virtualised instance of Windows XP is shutting down. It freezes completely.
Is there any way to kill it without logging out? And how come logging out can kill the process fine, is there any way I can leverage the power of "NT AUTHORITY" to
really kill the process?
-
-
SysInternals has some pretty cool stuff (recently bought by M$)...
-
dcoolidge99508 wrote: SysInternals has some pretty cool stuff (recently bought by M$)...
I tried ProcessManagerXP, that couldn't kill it either.
-
The method I've used is to force the app into the debugger then tell the debugger to quit. it works better than any other method..
I'll try and find the commands and post them, it's been a while since I've had to do it..
rich -
skeletor wrote:
The method I've used is to force the app into the debugger then tell the debugger to quit. it works better than any other method..
I'll try and find the commands and post them, it's been a while since I've had to do it..
rich
I got VS2005 to attach to the Virtual PC process, but it threw an error about being unable to attach and left me with an empty *.sln
Speaking of which, why does VS create a new *.sln for every non-project-related debugging occurence?
-
Logging out probably works because it's the SYSTEM authority telling the process to get the hell out. Now if you could elevate your window station to SYSTEM...
-
Tom Servo wrote:Logging out probably works because it's the SYSTEM authority telling the process to get the hell out. Now if you could elevate your window station to SYSTEM...
at 0:00 /interactive cmd
(change time appropriately) -
PSKill from SysInternals http://www.sysinternals.com/Utilities/PsKill.html) should do the job properly!
PTB -
PatTheBaker wrote:PSKill from SysInternals http://www.sysinternals.com/Utilities/PsKill.html) should do the job properly!
PTB
Looks like a remake of "taskkill" for Windows 2000. Windows XP already has one.
-
AndyC wrote:

Tom Servo wrote:Logging out probably works because it's the SYSTEM authority telling the process to get the hell out. Now if you could elevate your window station to SYSTEM...
at 0:00 /interactive cmd
(change time appropriately)
I'm guessing that creates a cmd instance running as system?
Can't I just use Runas?
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.