171

When I start up an Experimental instance of VS from VS for debugging and stop debugging (sometimes directly from the parent VS), a zombile devenv.exe process remains running which I am unable to kill. It holds on to many of my dlls.

As I am logged onto this 64bit Win7 machine as Administrator, I would expect to be able to kill any process I wish to.

I tried (from Administrator command prompt):

End Task from Task Manager.
TASKKILL /F /IM devenv.exe
PSKILL devenv.exe

None return any error and TASKKILL and PSKILL returned success messages of terminating/killing the process. But devenv.exe still runs, it is not re-spawned as the PID remains constant. It goes away only on restart of the system which is not a great solution.

Note. LockHunter shows devenv has got a lock on itself. And it cannot unlock it.

Process Monitor shows devenv to be in some kind of 'Process Profiling' loop

The above screenshot is the output of Process Monitor showing devenv to be in some kind of 'Process Profiling' loop (Right click on it and click open image in new tab to see it properly).

Any ideas how to kill such a process on Windows?

Cœur
  • 37,241
  • 25
  • 195
  • 267
dushyantp
  • 4,398
  • 7
  • 37
  • 59
  • No idea why you don't get an error, but to verify one thing: Did you call these commands from an elevated command prompt? Otherwise the commands will not run with Administrator privileges, even though your account has them. (This shouldn't allow them to return success when they clearly failed though ;)) – SvenS Sep 21 '12 at 10:52
  • 1
    yes all commands were run from Administrator command prompts. – dushyantp Sep 21 '12 at 12:07
  • 3
    This sort of question is more appropriate on http://superuser.com. Yup, they have quite good explanations there. [This one](http://superuser.com/a/295990/167666) helped me. – Jarekczek Oct 29 '12 at 19:58

31 Answers31

99

you must kill child process too if any spawned to kill successfully your process

taskkill /IM "process_name" /T /F

/T = kills child process

/F = forceful termination of your process
LaurentG
  • 11,128
  • 9
  • 51
  • 66
aaa
  • 1,039
  • 7
  • 2
  • 29
    It prints two success messages in my case, but the process is still there. What the hell? – CodeManX Aug 24 '15 at 02:21
  • 3
    if that would be so easy :) no, it doesn't help. I think his problem is because the unkillable process is in some loop (socket, i/o, pipes...) where the main process is system process and killing it will make system unstable. It that case I would recomend first to understand what loop is the process in. Then, if that loop is network exchange with other endpoint, then just unplug network cable or disconnect the already established connection. –  Sep 12 '15 at 13:18
  • 112
    I get a `There is no running instance of the task` That process really does not want to die! – demongolem May 11 '16 at 03:59
  • 1
    still help me today, though I have to kill the "child of the child" too: taskkill /f /T /PID 4172 ==> ERROR: The process with PID 4172 (child process of PID 4724) could not be terminated. ==> taskkill /f /T /PID 4724 ==> Done – Hoàng Long Aug 12 '16 at 08:25
  • 2
    Yay for the under-mentioned `/T` switch! – kayleeFrye_onDeck Apr 27 '17 at 20:03
  • in case of „There is no running instance of the task“ it must be killed some associated process which holds lock on this process, for example devenv.exe is associated with some_debugged_process.exe – tibx Apr 12 '19 at 05:34
  • YAY! this has been affecting the enjoyment of my LIFE. thank you – Justin Mar 10 '20 at 23:14
  • 1
    Did not work for me, trying to delete the Windows Defender process that uses near 100% of disk access.. – David Spector Jun 08 '20 at 12:04
64

The taskkill and powershell (kill) methods didn't work for me; it still said "Access Denied".

I had better luck with this:

wmic process where "name='myprocessname.exe'" delete
twasbrillig
  • 17,084
  • 9
  • 43
  • 67
41

Reboot is the only solution that worked for me (so far).

The ever excellent Mark Russonovich has a good explanation for unkillable processes.

To summarise, it's quite possible it is due to unprocessed I/O requests that hasn't been handled properly (by a device driver your program has possibly accessed)

https://techcommunity.microsoft.com/t5/windows-blog-archive/unkillable-processes/ba-p/723389

MaYaN
  • 6,683
  • 12
  • 57
  • 109
Francis
  • 1,798
  • 1
  • 26
  • 32
38

Just had the same issue on Windows Server 2008 R2 and nothing helped, not taskmanager or taskkill. But, windows powershell run as administrator worked with "kill -id pid"

DomainsFeatured
  • 1,426
  • 1
  • 21
  • 39
Gnampf
  • 995
  • 1
  • 14
  • 23
  • 4
    This worked for me... though there seemed to be about a 30 second delay before the process actually went away, so at first it seemed to fail. In the case that I had it was a process that was created procedurally by another application while the system was low on resources. Process Explorer, kill process tree, and several other things failed to work, but this did the trick. – J. Paulding Jan 06 '16 at 20:28
  • 4
    Didn't work for me, gave me an error unable to kill process etc etc – rboy Feb 24 '17 at 17:45
  • @rboy . I know its old, but just in case someone else sees this do what I did. Open powershell as Administrator and then run it. At first I ran it not as admin and it told me I couldn't do it. So then I ran it as admin and it worked. – Chris Jones Jun 14 '17 at 15:35
  • This worked for me on Windows 10 with a misbehaving Windows service. Had already tried CMD, in this case PowerShell is the right tool – ThetaSinner May 04 '18 at 15:49
  • 5
    No luck for me even after waiting for more than 2-3 mins. none of the command is working for me currently – Tarun Gupta Jul 16 '18 at 11:28
9

I know it's late but taskkill /im devenv.exe /t /f should work. the /t kills child processes too.

cure
  • 2,588
  • 1
  • 17
  • 25
9

In my case, after several days of fighting with this problem (it was happening to VirtualBox and µTorrent processes), I discovered it was caused by a network driver issue, provoked by Windows Update patch KB4338818 (Windows 7 x64). After uninstalling that patch everything went back to normal. I just thought it could be useful for others.

Danita
  • 2,464
  • 4
  • 23
  • 29
  • How did you discover that the update caused it? I think I would have never discovered that. ^^' – das Keks Aug 09 '18 at 14:29
  • 3
    I realized the only thing that changed in my machine before the issue become apparent was the updates, so I checked which was my last update and read the release notes. It seemed suspicious and I rolled back to see if the issue was solved, which it was. Then I read on some Apache forums, don't remember which, that this update has caused trouble for them too. BTW: Last Windows Update as of 2018/Aug/10 fixes the problem with KB4338818, so it can be installed again. – Danita Aug 10 '18 at 15:19
6

I could solve my issue rearding this problem by killing explorer.exe which in turn was addicted to the process I wanted to kill. I guess this may also happen if processes open interfaces via hook which may be locked.

seansilver
  • 435
  • 1
  • 6
  • 11
6

Native tskill <pid> (or tskill.exe <pid> ) worked for me on Windows 10 where no other native answer did.

In my case, I had some chrome.exe processes for which task manager's 'End Task' was working, but neither taskkill /F /T /PID <pid> nor powershell's kill -id <pid> worked (even with both shells run as admin).

This is very strange as taskkill is purported to be a better-api-and-does-more version of tskill.

In my case to kill all instances of a certain task I used FOR /F "usebackq tokens=2 skip=2" %i IN (`TASKLIST /FI "IMAGENAME eq name_of_task.exe"`) DO tskill %i

zig1000
  • 61
  • 1
  • 3
5

I've seen this a few times and my only solution was a re-boot.

You could try using PowerShell: Get-Process devenv | kill

But if the other methods failed, this probably will too. :-(

Thomas Lee
  • 1,158
  • 6
  • 13
  • Sadly yes! For me also it's the case. did you ever get any solution? – manocha_ak Jan 16 '15 at 12:10
  • Not worked for me on win10: PS D:\work\Projects\libtiff.net_bin-2.4.560.0> Get-Process NSPRip | kill PS D:\work\Projects\libtiff.net_bin-2.4.560.0> echo $? True PS D:\work\Projects\libtiff.net_bin-2.4.560.0> Get-Process NSPRip Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName ------- ------ ----- ----- ------ -- -- ----------- 0 0 56 20 0.00 41236 1 NSPRip – zhaorufei Apr 28 '18 at 00:50
4

I am going to suggest something here because I recently faced the same issue and I tried every possible thing in the answers but nothing worked. I was getting errors like

ERROR: The process with PID 23908 could not be terminated. Reason: There is no running instance of the task.

using command prompt. Power shell wasn't helpful either. it would simply execute the commands and no response with process still running.

Until I decided to delete the associated '.exe' file. Since the file was active, windows would not allow the deletion, but in that warning window it gave me the name of the process which was holding up the task I wanted to kill. I was able to kill the original task and thus the buggy process.

It is definitely worth a try if none of the solutions works out.

Astroynamicist
  • 193
  • 2
  • 11
3

If taskkill /F /T /PID <pid> does not work. Try opening your terminal elevated using Run as Administrator.

Search cmd in your windows menu, and right click Run as Administrator, then run the command again. This worked for me.

Itchydon
  • 2,572
  • 6
  • 19
  • 33
Kevin Li
  • 2,068
  • 15
  • 27
3

I was getting the following results with taskkill

>taskkill /im "MyApp.exe" /t /f
ERROR: The process with PID 32040 (child process of PID 54176) could not be terminated.
Reason: There is no running instance of the task.

>taskkill /pid 54176  /t /f
ERROR: The process "54176" not found.

What worked for me was sysinternal's pskill

>pskill.exe -t 32040

PsKill v1.15 - Terminates processes on local or remote systems
Copyright (C) 1999-2012  Mark Russinovich
Sysinternals - www.sysinternals.com

Process 32040 killed.

You can get pskill from the sysinternal's live site

Phillip Ngan
  • 15,482
  • 8
  • 63
  • 79
3

taskkill /f /im "process.exe"

running cmd or .bat file as administrator worked for me

3

while taskkill didn't work

taskkill /f /t /pid 14492

ERROR: The process with PID 14492 (child process of PID 7992) could not be terminated.
Reason: There is no running instance of the task.

the simpler tskill has worked fine for me

tskill 14492
Jirka Buš
  • 41
  • 3
2

Some of the Exe files Dependents on Some services,

So you need find the respective service and stop first.

girish
  • 87
  • 4
  • 4
    any hints on how to work this out? On taskmanager it doesn't show any service corresponding to devenv.exe Right now I am trying to recreate the problem, once done I will use process explorer to dig into services which could be holding it. – dushyantp Sep 21 '12 at 12:09
2

Running as an admin works for me:

1.search cmd in windows

2.right click on cmd select as "Run as administrator"

3.netstat -ano | findstr :8080

4.taskkill/pid (your number) /F

My result

Eonasdan
  • 7,563
  • 8
  • 55
  • 82
Qing Yuan
  • 67
  • 2
  • If you get an error such as: 'nestat' is not recognized as an internal or external command, operable program or batch file. you may need to run the command as C:\Windows\system32\netstat.exe instead of just nestat – sk8asd123 Dec 02 '18 at 15:25
2

The same problem happened to me in VirtualBox with respect to Java processes.

In my case, it was due to a bug in Windows Update patch KB4338818 (Windows 7 x64).

I solved it by doing the following:

  • Uninstall Windows Update patch KB4338818
  • Install Windows Update patch KB4338821
Robert Columbia
  • 6,313
  • 15
  • 32
  • 40
Philippe GRANET
  • 453
  • 4
  • 7
2

For me, the way it worked is I have to kill the parent process. Figure the parent process out and kill it

taskkill /IM "parent_process_name.exe" /T /F
Zoe
  • 27,060
  • 21
  • 118
  • 148
Shahazan
  • 21
  • 1
2

In my case none of the solutions here worked. I eventually found that the program in question was frozen trying to poll USB audio interfaces. So I unplugged a USB DAC I had connected, and to my surprise the application quit instantly. Francis' answer mentions that it could be a result of "unprocessed I/O requests that hasn't been handled properly (by a device driver your program has possibly accessed)", which might explain why this fixed it.

I suppose it really depends on what the program was doing when it froze, but if none of the other solutions are working, try disconnecting all USB devices to see if one of them could be the cause.

Macklin
  • 146
  • 1
  • 1
  • 8
1

I have the Problem with debugged processes with gdb in Code::Blocks. As soon it is hanging while accidentally stepping into instructions out of scope of your sources (as libs without sources or system functions) you cannot quit the debugging neither from Code::Blocks nor from Task-Manager.

I think it is an error in the implementation of gdb in Code::Blocks, but could also be in gdb ;)

My Solution:

taskkill /F /IM process.exe /T

This shows the PID of the parent process. Now kill the parent:

taskkill /PID yyyy

Both are gone.

Done.

kolp
  • 13
  • 4
1

NirSoft's NirCmd did the job for me:

nircmd killprocess "process name.exe"

killprocess man page is here.

Saxtus
  • 131
  • 2
  • 5
1

I had the exact same issue, found this fix on another site: powershell.exe "Get-Process processname| Stop-Process" it worked for me and I was in the same boat where I had to restart, the /T would not work.

Jeremy
  • 11
  • 1
1

If you download the free sysinternals suite, it has a pskill.exe application which works well for these types of tasks: pskill.exe "process_name" It works on these processes even without using its -t option.

BenV136
  • 319
  • 2
  • 5
1

I did the following, on an elevated powershell:

PS C:\Windows\system32> wmic.exe /interactive:off process where "name like `'java%'`" call terminate

command Output:

Executing (\\SRV\ROOT\CIMV2:Win32_Process.Handle="3064")->terminate()
Method execution successful.

Out Parameters:

instance of __PARAMETERS
{ReturnValue = 0; };

I got some syntax information on : https://community.spiceworks.com/topic/871561-wmic-error-like-invalid-alias-verb

builder-7000
  • 7,131
  • 3
  • 19
  • 43
Lakoroll
  • 19
  • 2
1

As Francis mentioned some process can not be terminated because of

"unprocessed I/O requests"

In my experience i was dealing with buggy graphic driver that would cause my game to crash and not be able to close it, as last resort i disabled the graphic driver and the process finally went away.

If your application is waiting for a resource from driver like wifi or graphic try disabling them in device manager, you need to dig a little deep to see where they hanged.

This is of course not recommended but sometimes you have nothing to lose anymore.

Masoud R
  • 102
  • 3
  • 10
1

I had the same problem and as many others here have said none of the normal Kill commands worked. My problem file was an executable that was being run from a network share by a user on a Remote Desktop Server. With multiple shared users not an easy thing to restart in during a work day. Even when the user logged off the exe was still listed in Task Manager. I sent to the server where the folder was shared and from Computer Management -> Sessions found the user with the session still open from that RDP server even though he was logged off. Right Click -> Close Session and the file lock was released.

Beats me why I couldn't end the taks. The error message I was originally getting when I try and delete the file was "The action can't be completed because the file is open in System"

Hope this helps someone else.

David P
  • 411
  • 7
  • 21
0

I faced the same issue where I started a node app in port 3000 and it didn't close correctly and the process kept running even after restart.

None of the taskkill or powershell commands running in Administrator mode worked for me.

I used MS Process Expoler > Properties > Image > Current directory (which was supposed to be the my project directory).

Finally, I had to reboot in SafeMode and rename the project folder and restart. The Node processes which were consuming port 3000 killed itself.

YakovL
  • 7,557
  • 12
  • 62
  • 102
Aaman
  • 19
  • 5
0

For killing PID Tasks running in windows:

TASKKILL  /PID "Taskname"  /F
DescampsAu
  • 1,056
  • 2
  • 10
  • 29
Saran Zeb
  • 311
  • 3
  • 7
0

using wmic: show all running process where name of process is cmd.exe

wmic process where name="cmd.exe" GET ProcessId, CommandLine,CreationClassName

then terminate the specific instance of process by processId (PID)

WMIC PROCESS WHERE "ProcessID=13800" CALL TERMINATE

-6

Run CMD as Admin will fix the problem

-9
  1. open task manager
  2. select services tab
  3. select the process( devenv.exe ) you want to kill and click services button
  4. right on the process, select properties and disable it...
zoom
  • 1
  • 1