Task Manager CANNOT KILL PROCESSES

  • Thread starter Thread starter j90qfj90q34fjwefi2
  • Start date Start date
J

j90qfj90q34fjwefi2

It's really great at ending the processes that are running fine, but when one
hangs, oh no, you're doomed. Reboot.

It's not even the TASK MANAGER. VISTA simply does not have the capability
to manage processes. Even 3rd party programs like Process Explorer and
Process KO can't do it.

My suggestion to MS would be, if you're going to mane an OPERATING SYSTEM,
spend less time on the USELESS AERO GLASS SKIN and more time on actual
FUNCTIONALITY.

Your TASK MANAGER should be able to MANAGE TASKS.

/end

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/co...fae&dg=microsoft.public.windows.vista.general
 
j90qfj90q34fjwefi2 said:
It's really great at ending the processes that are running fine, but when
one
hangs, oh no, you're doomed. Reboot.

It's not even the TASK MANAGER. VISTA simply does not have the capability
to manage processes. Even 3rd party programs like Process Explorer and
Process KO can't do it.

My suggestion to MS would be, if you're going to mane an OPERATING SYSTEM,
spend less time on the USELESS AERO GLASS SKIN and more time on actual
FUNCTIONALITY.

Your TASK MANAGER should be able to MANAGE TASKS.

/end

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/co...fae&dg=microsoft.public.windows.vista.general
Click to expand...


Which programs will not close?

--
Mike Hall - MVP
How to construct a good post..
http://dts-l.com/goodpost.htm
How to use the Microsoft Product Support Newsgroups..
http://support.microsoft.com/default.aspx?pr=newswhelp&style=toc
Mike's Window - My Blog..
http://msmvps.com/blogs/mikehall/default.aspx
 
it takes a while, but if you are patient, it does close them. At least I
haven't found one yet that won't. Java vm is the biggest culprit for me -
sometimes printing international mailing labels it either crashes Firefox or
just hangs til I end
process on it.

Lori
 
My suggestion to MS would be, if you're going to mane an OPERATING SYSTEM,
spend less time on the USELESS AERO GLASS SKIN and more time on actual
FUNCTIONALITY.

Your TASK MANAGER should be able to MANAGE TASKS.
Click to expand...

And the explorer should be able to manage files
and the search tool should be able to find them
and the....
 
And the explorer should be able to manage files
and the search tool should be able to find them
and the....
Click to expand...

Wrong!
The Search tool should "Search" files. It does. It won't find, however. That
would be a "Find" tool. Maybe in Windows 7 :P

Honestly, I have Vista here and after getting acustomned to it, I very much
like it. It has a few quirks, but it'S OK.

My only problem is, that drag-drop of files between elevated and
non-elevated programs does not work.
 
Programs like FireFox, HL2.exe (counter-strike source), Winamp, etc when they
hang will not close even if i repeatedly push End Process > OK, End Process >
OK, End Process > OK, End Process > OK

Not ALL hanging processes can't be shut down--Sometimes they WILL shut down.

BUT

Sometimes they will NOT, and I have even pushed SHUT DOWN and turned my
monitor off... in the morning when i check, vista has STILL not been able to
kill the process or shut down... how sad.. The only way is to cold shut down
or cold reboot.

I am not talking about system processes--i know they are not to be closed.
I am talking about 3rd party programs that hang and the operating system has
no control over them to kill them.

It is not an uncommon problem. I don't know why you are asking like you
have never heard of this before??????? Apologies if I am mistaken. Google
"cannot end process" and you will see many results in both XP and Vista. I
had hoped Vista would have an improvement in this regard. it has not.
 
Hey guess what, I know what the problem is. Microsoft had another brilliant
idea (sarcasm--as usual) called "Clean service shutdown" .

Microsoft's SysInternals software engineer Mark Russinovich, describes this
at WinHEC 2007 (link at bottom of my post).

"One of Windows' historical problems concerns its system shutdown procedure.
In XP, once shutdown begins, the system starts a 20-second timer. After that
time is up, it signals the user whether she wants to terminate the
application herself, perhaps prematurely. For Windows Server, that same
20-second timer may be the lifeclock for an application, even one that's busy
spooling ever-larger blocks of data to the disk.

In WS2K8, that 20-second countdown has been replaced with a service that
will keep applications given the signal all the time they need to shut down,
as long as they continually signal back that they're indeed shutting down.
Russinovich said developers were skeptical at first about whether this new
procedure ceded too much power to applications; but in practice, they decided
the cleaner overall shutdowns were worth the trade-offs."

WOW WHAT A GREAT IDEA, LETS ASK PROGRAMS NICELY TO SHUT THEMSELVES DOWN!!!
No wonder the Vista Task Manager is completely useless and can't kill
anything. What a bunch of BONEHEADS. Your OS can't even dump a hanging
process.

LINK
http://www.betanews.com/article/Top_10_New_Features_in_Windows_Server_2008/1180045346
 
Yep. This has always frustrated me. Of course, nobody CAN explain why
the Task "Manager" is so terribly inadequate. Or...maybe it should just
be renamed to Process/Status Viewer to eliminate confusion.

In fact, I need to force a shutdown right now due to a 3rd party
process that has hung and cannot be killed. *Sigh*
Click to expand...

You can kill a process IF it is behaving. If it is acting up then Task
Manager often is sluggish. The trick is "kill" the process once, then
wait. How long depends. In time, usually less than 60 seconds Task
Manager should be able to shut down the offending service or force it
to pop a shut down window of it's own which often will work.
 
I can not believe this, I can not end my OWN process, it tells me access
is denied. I am administator, I am the creator of that f**n process. How
come something like this vista "thing" can be called an operating system
while it is NOT even capable of control the OPERATIONS ! I hate this, I
really really do, as a programmer, I have to waste my time, money and
LIFE for this kind of BS, becouse it is so called mainstream ! Damn !
Click to expand...

Lol...
taskkill /f /im <image name>
?
 
There are some processes that cannot be killed. They are needed by windows
security. If you want to kill them i think you should try using procexp and
but you will get a BSOD
 
robogeek said:
I agree with most of you. Vista is a shambolic operating system that
cannot manage its own processes. With Unix and Linux there is the kill
Click to expand...

I didn't see the earlier part of this thread, but ... well, Windows - or
at least, Win32 - has no Signals mechanism, so a kill -9 SIGKILL does
not and cannot exist, as such, on Windows. The Windows POSIX subsystem
supports both Signals and kill -9 (although, POSIX/Interix/SFU/SUA has
been shamefully neglected by MSFT; they didn't realise what they had).

However, if you have a Command Prompt open, (and which true geek
doesn't?) then you can kill a Win32 process with extreme prejudice from
the command line, by issuing a "taskkill /PID <nnn> /f /t", as
documented here:

http://technet.microsoft.com/en-us/library/bb491009.aspx

By running in the Console, this seems to bypass some of the Windows
message loop processing that can gum up other task managers like Process
Explorer or, uh, Task Manager. Mind you that's just my subjective
impression, I haven't stepped through it in the debugger.

Overall, Windows decided to prefer to allow processes to shut down
gracefully, rather than making it easy to kill them outright. Whereas
POSIX systems (Unix, Linux etc) let you easily kill a process, without
much "are you sure" graceful graciousness, aforethought. Is one better
than the other? How many lives have been lost, and how many sysadmins
have turned grey, as a result of one or the other design decision? Hard
to say .. I think there's no clear winner there.

Just my 2 cents :-)

Andrew
 
Back
Top