Windows 7: Processes not shutting down

Hi all,

I am running Windows 7 64 Bits, installed from scratch and all is not too bad EXCEPT that processes do not terminate. What a pain in the nuts.

Often, when I shutdown an application, the application window closes but the process remains in Task Manager. Killing the process does not do anything. It seems to affect any programs, no one in particular. The only cure is to reboot the system.



1. Anybody else having this mega problem?

2. Is it 64 Bits problem only? Is it fine under Windows 7 32 Bits?

3. Any other way to kill the tasks?

Please help before I throw my laptop by the window!
Thanks

This is not a Windows problem, it is a problem with the programs involved. Open the Task Manager and find the process for the program involved, and kill it there. See if the programs have Windows 7 x64 versions available.

I do not think, it is a problem with the programs involved. It happens with any programs, Itune, firefox, Outlook 2007, Word 2007, Visio 2007, does not matter which program.

I googled up this issue and seems like many people have the exact same problem.

It's a known issue with Outlook 2007 according to Microsoft it happens because of the Anti Spam plugin. Can you tell me how long it stays in the Task Manager ? Because sometime it might take a while to End the process.

Hope this helps,
Captain

It stays forever. That it very annoying.

Thanks

Try PSKill from Sysinternals

How to Kill Stubborn Processes That Fail to End Process in Task Manager My Digital Life

Do these processes any CPU time? If not, they are just cached - their roots repectively. They will be thrown out as soon as the RAM is needed. This may explain it better SuperFetch: How it Works & Myths

If a process was simply cached, shouldn't a cache app be able to remove the process? The reason that I ask, is because I do have O&O's CleverCache installed, and I still have had problems at times with processes that remain until I reboot.

Suggest you read what I linked above and also the link given on the bottom of that page to the Mark Russinovich blog. There is a detailed explanation how it works.

But those processe do no harm. They are just sitting there idle and give way whenever the RAM is needed.

Clever Cache may well be the culprit here...