Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote. But i am able to kill any other exe say notepad. Tuesday, February 12, PM. Also before doing Kill it is better to check if process has exited.
This can be done like this Sleep ; if! HasExited myprocess. Kill ; Show 12 more comments. JosepStyons is right. Open cmd. Shades 5, 7 7 gold badges 27 27 silver badges 48 48 bronze badges. Dhruv Chandhok Dhruv Chandhok 7 7 silver badges 18 18 bronze badges. Running as administrator, the error changes. Reason: There is no instance of the task.
As it can't find the parent, it won't kill the orphaned child. In my case, the zombie process I told it to kill was the only child and there was no parent, though the zombie still thought it had a parent. In my case, resolved by using the Windows 8. Non-trivial getting it to do a full shutdown. For example if you had just attempted to close it earlier. You'll need to wait till it gets closed. Add a comment.
Iain Holder Iain Holder That does provide more info and some limited ability to search for lock handles but I've not had any more success at killing tasks with it than with basic Task Manager.
Certain processes like anti-virus, and SugarSync. One trick that works well is to attach a debugger and then quit the debugger. On XP or Windows you can do this using ntsd that ships out of the box: ntsd -pn myapp. I've known this to work even when task manager doesn't seem able to kill a process. Rob Walker Rob Walker When Visual Studio and an application being debugged both hang, attach and kill the old instance of VS.
The killer can be a new instance of VS, which can then open the old project and allow you to continue working. You can now get it in the Windows 10 SDK by running the installer and then unchecking everything but "Debugging Tools for Windows" docs. David Ruark David Ruark 69 1 1 silver badge 1 1 bronze badge. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.
Learn More ». Ghost Chili. Verify your account to enable IT peers to see that you are a professional. A and T This person is a verified professional. How are you shutting down the server? I'll go through the shutdown plan when I don't have people on the network but going through your list - Backups are onsite and offsite cant be too careful - no LAN - I'll test this later - No external anything devices attached - as above, nothing external so all shutdowns are kb, mon, ms and LAN only Once the machine gets flakey I can only do some of the following - shutting all applications and services - last time they just wouldn't die, couldn't even kill them - then it go so bad that I couldn't remote in and by this point I also can't log on at the console I'll try some more non LAN shutdowns but this box is only DHCP DNS and File server to about 50 clients - barely ticks over.
Techgyver Mar 30, at UTC. Its not much, but maybe that can help. I am still curious if the hardware itself is having an issue. We have a major issue with a process that we can not kill and the only way to get rid of the process is to reboot the machine.
The command reports as sucessful but the process remains. I have tried to start task manager with system rights by calling "psexec -s -i -d taskmgr" and attempting to kill the process but no joy. Nothing I do will kill this process. Even logging off and logging back on will not kill this process. Using Process Explorer I notice that there is on stubborn thread that is in the Wait:Executive state.
I have tried to kill this thread using Process Explorer but again no joy. We are using Windows Server R2 Bit. The server is brand new and windows is freshly installed. Now heres the thing. We have brought two identical servers from Dell with the same specs and the same OS installed and I can not replicate this issue on the other server.
Only on this server, under certain circumstances does this server process hang and can not be restarted! I have also changed the compatability mode by setting it the process to "Windows " but this has not helped. I have noticed in Process Explorer that DEP is turned on but im not sure this has got any bearing on the issue ot not. I have used a trick with scheduler for some time. Open Task manager and try to kill the process.
It seems that this funcationality was removed in Windows and Windows 7. You can now, no longer schedule a task and have it run under the user account where you can interact with it.
It seems to be HW specific. Have you asked Dell support for the help?
0コメント