Thanks for the info Tybilly, but I already tried everything possible. From that utility to manual deletion in registry. But this is not a problem that is caused by malfunction of KAV, as I've tracked what is it doing.
Edit: Tybilly, this doesn't happen on my PC only, it happens on 11 more that have, let's say, fresh WinXP. Few programs installed. And 2 of them are freshly installed about 2 months ago.
I have several files that are stored in ISO and Acronis backup that are pulled back from server and transfered, by me, onto my PC for addition checkout of employees work, and of course few games from D2D that are "ISO" based. Anyway, I think I figured out why KAV is making those TMP files. At least what tracking software logged.
QUOTE
-- avp.exe - access/read - E:\Backup\25.09.2009\PC3 Backup.ISO - 27.09.2009 - 17:43:06
-- avp.exe - write - E:\Backup\25.09.2009\PC3 Backup.ISO - C:\Temp\PR2F5.TMP - 27.09.2009 - 17:43:08
-- avp.exe - access/read - E:\Backup\25.09.2009\PC3 Backup.ISO - 27.09.2009 - 17:44:15
-- avp.exe - write - E:\Backup\25.09.2009\PC3 Backup.ISO - C:\Temp\PR2F6.TMP - 27.09.2009 - 17:44:19
etc....
And even there is deletion captured in log file: -- avp.exe - delete - C:\Temp\PR2F5.TMP - 27.09.2009 - 17:51:06
And this is the "thinking" part:
Large files, ISO or any large "package" files, when modified, KAV scans them in unusal way. The part that is File AntiVirus in KAV, instead of scaning large files within, it somehow makes those TMP files, copies of the actual files, while checking with KAV File AntiVirus.
For example:
I store backup onto my HDD, KAV starts scaning that backup(no actual scan active), and makes TMP files while scanning. it's not immediate, but sometimes it does that upon finished copying. Although KAV scanned those files while copying. I wonder why it is doing that. Also, as I've said, it "scans" them upon finished modification, and even "scans" them without any modification or tempering with them. That last thing is what is bugging me, and ofcourse, making TMP files while "scanning".
Either devs must modify KAV that makes at most 100MB TMP files, and upon finishing of first 100MB TMP file KAV must delete that, and continue with new 100MB file. Or disable that function and let KAV scan files without any TMP. And possibly include that in update.
Now, what about other problem, with HTTP port monitoring?