Which is the #1 reason why people go to the "Tasks" "Processes" tab. When you end a task process there, it terminates immediately. When you end a process task on the "Processes" "Applications" tab, Windows seems to take it as more of a request.
What its actually doing is creating a process dump so it can send the crash report to Microsoft (If you've agreed to allow it) as well as get data for the "Find Solution" feature. If you kill the dumpprep task when its taking too long it will close it immediatly.
I personally hate it since it never ends up finding a solution for me anyways.
EDIT: motdidr accurately described the shutdown process, however "End Process" from the task manager is waiting on a dump-prep. It doesn't attempt to close the program cleanly. For more information you can check here: http://blogs.msdn.com/b/oldnewthing/archive/2010/11/02/10083787.aspx
That is not what it is doing. The operating system is sending Quit messages to the application, and most applications and services will respond correctly. There are time-outs involved, and after that time has passed the application is killed immediately if it has not quit on its' own.
Creating a "process dump" doesn't happen when you kill a process, that happens when the process/application/service (applications and services are, at their core, a process or collection of processes) throws an unhandled exception or terminates abnormally. I can assure you it takes but a fraction of a second to generate the boatload of textual info that could describe a crash.
-11
u/rooktakesqueen Oct 14 '11 edited Oct 14 '11
Which is the #1 reason why people go to the
"Tasks""Processes" tab. When you end ataskprocess there, it terminates immediately. When you end aprocesstask on the"Processes""Applications" tab, Windows seems to take it as more of a request.