Some programs unresponsible after certain file operations

Greetings,

have following problem. I started to notice a long unresponsiveness or even complete freeze of some applications after performing certain file operations. These are the issues:
- In µTorrent if I delete a task only, it continues operation instantly. If I delete task+associated torrent file, it becomes unresponsive for unusual period (mostly 30-60sec.). If I delete task+torrent file+torrent contents, it even freezes completely (didnot confirm if it only is a too long delay or complete freeze but after about 5 min I have given up and killed the application)
- In Corel PhotoPaint if I save a large image to disk, after confirming the filter settings the application becomes unresponsive for about 30-60 sec. and during this period I get continuous system dialogs about application not being ready, Switch To.../Retry/Cancel.
- In Win Explorer if I delete file, it becomes quite long before the confirmation dialog appears and it also takes quite a long the deleting operation self. This doesnot happen always.

I thing all issues are related, not seen these delays on other applications yet.
How do I locate the culprit and fix the problem? I didnot have these delays earlier.

Maguscreed said:

The utorrent problem should be solvable by simply moving the download directory out of your my docs area.
say c:\downloads

Thanks for quick response but this is not the case, I use various download locations and it happens always regardless where do I store the data.

Maguscreed said:

As for the other apps, it really sounds like your security software is sticking it's nose into these processes and slowing things down.

How can I find out which process sticking it's nose into them? I only use Comodo Personal Firewall with Defense+ deactivated, then SuperAntiSpyware but not autostarted and SAScore service set start to manual (not running during these file IO problems), UAC turned off, Security Center turned off, Microsoft Security Essentials with runtime protection turned off and MSE service set to manual (not running during the problems). I don't have more security sniffers installed Afaik.

OK I give it a try but I'm afraid this won't be the solution since I'm using CFW a long time already with same configuration and this issue appeared as late as few weeks ago.

Maguscreed said:

Well the quickest easiest test would just be to completely kill the comodo processes (exit program)
and see if the problem persist.
Comodo firewall actually monitors system services too, so it's not outside possibility.

I concur it gets you when you do not expect.

I have a simple BAT script that launches a few lines of VB script many times in succession.
The results were horrendously irregular so I switched the Firewall to Block All and Disabled Defense+ (prime suspect) and A.V.
That gave perfection, it iterated regularly many times a second,
BUT at regular 33 second intervals it froze for 5 seconds.

Windows Task manager saw nothing stealing processor time;
Systernals Process Explorer saw Comodo using 25% (1 out of my 4 cores)
Process Monitor gave me faaaarr toooo much information ! !

Then I unplugged the Ethernet cable to the router and the 33 second glitch vanished - perfection as desired.
I unplugged so that with safety from malware I could disable Comodo's firewall,
but with it unplugged there was perfection when both enabled and disabled.

Perhaps my ISP or my Router are checking my connection every 33 seconds,
and that ICMP or whatever makes Comodo catatonic whilst cscript is running.

Regards
Alan

I would say that it's not exactly µTorrent's issue. As I wrote similar delays appear in other apps/situations also. Just µTorrent is a good client to demonstrate the behaviour on. I suppose that this problem is more system wide, something interfering or blocking deleting files. I observe a longer delay not observed earlier on Firefox browser when starting a new download. The browser freezes for about 15s (not always but often). I really don't get an idea where I should start to find the problem source. Maybe event log? Some kind of debugging on the µTorrent case? Any profiler, diag tool that could analyze why the mentioned apps stay so long unresponsible? The only common factor of all those situations that they deal with file deleting operations, maybe creating also.