New
#21
If PSKill did nothing then the task is not running...
What window view are you looking at ? ?
If PSKill did nothing then the task is not running...
What window view are you looking at ? ?
The Task Manager of course. In the capture you can see 5 conhost.exe process and 4 OutlookSyncClient.exe processes.
The more I look at this, I think it might have something to do with Outpost Firewall.
Simplest test would be to disable Outpost...re-boot and see what happens...
This is cached stuff. None of it is running.
I understand that it is cached stuff but when it happens with Firefox, you are not able to start another session because it says that it is already running. This is why it is a pain.
I scanned the thread and didn't see it mentioned, but have you tried Taskkill in the Command Prompt? It may fare no better than the other means to kill a process, but it would be worth a try.
While I have had this problem with a couple of programs, Firefox is not among them. I'm using the Shiretoko x64 version...I wonder if that is the reason for the difference?
I'm on 64 bit as well and had issues with Firefox sticking around after exiting, but I think I have nailed it to the Winamp add-on, which I've disabled.
Since Firefox is only a secondary browser for me, I never install any of their add-ons, that may be why it doesn't give me any problem.