Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Schilcote]

We all know that when you need a process to be killed, you press control-alt-delete and bring up the task manager to kill the process.

But what should I do to kill taskmgr.exe?

I've tried starting another instance, it doesn't work, both through Ctrl-Alt-Del and command line. It's just sitting in my task bar flipping out and eating my CPU. It's got me confounded.

[ein]

Try clicking randomly on it.
That works for me, bringing up the "whatever has stopped working. >Wait for it to respond >Close the program"
Which always works instantly.

[woose1]

You can't kill what's already dead.

Failing a shotgun blast to the head, restart your computer?

[Aklyon]

Unplug computer. (and/or remove battery if laptop)
wait 30 seconds.
Reboot.

[Schilcote]

Code: [Select]

c:\tasklist

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
...
taskmgr.exe                   9860 Console                    1     23,356 K
...

c:\>taskkill /pid 9860
SUCCESS: Sent termination signal to the process with PID 9860.

I swear they weren't there last time I typed HELP.

[Muz]

Did it work? I don't think it would. It'd make sense so that a virus or whatever doesn't tell the taskmgr to kill itself when it's control Administrator. But then again, who knows, Administrator has full power.

[Schilcote]

Did it work? I don't think it would. It'd make sense so that a virus or whatever doesn't tell the taskmgr to kill itself when it's control Administrator. But then again, who knows, Administrator has full power.

Notice the "SUCCESS" message.

[Mishy]

I used to bah the top of my tower every time my pc crashed. The whole to top the casing was bashed in at least 3 inches deep. Funnily enough it actually worked, every time.

[G-Flex]

Then you probably had components that weren't seated properly, and should have fixed it (or had it fixed).

[Muz]

Did it work? I don't think it would. It'd make sense so that a virus or whatever doesn't tell the taskmgr to kill itself when it's control Administrator. But then again, who knows, Administrator has full power.

Notice the "SUCCESS" message.

Lol, can never tell with these computers... sometimes SUCCESS messages mean that it tried to do it, failed, but returned 0 anyway

Then you probably had components that weren't seated properly, and should have fixed it (or had it fixed).

Not if you bash it with a mace, like any real dwarf would.

[Heron TSG]

Just go to the 'processes' tab and end the taskmgr.exe process.

[fenrif]

Nuke the site from orbit... It's the only way to be sure.

[x2yzh9]

Launch a rocket carrying it to a black hole many many light-years away, just to be sure.

[Schilcote]

Just go to the 'processes' tab and end the taskmgr.exe process.

The processes tab in what, exactly? Task manager had lost it's mind, but retained enough life to intercept any requests to start another instance of it.

[ed boy]

the processes tab in task manager.