The following command kills a task immediately in XP, but not in Windows 7, the task lingers for ~100 seconds.
taskkill /f /t /pid 123
The only account on the machine is an Administrator account. I've tried cmd 'run as admin' and powershell, without any luck.
The task which is being killed is from a third party and uses quite a few TCP and UDP sockets. During the time when the task is lingering netstat lists these sockets.
Why would XP terminate this process immediately and Windows 7 not? Are there services or policies which could cause this behavior?
Thank you.
-Tom