Avast tries to modify ZA files and is blocked?

I’m running Windows XP SP3 with Avast Pro and Zone Alarm Pro 8.0.059 (firewall only)

I have ZoneAlarmCompatibility=1 in avast.ini and no incompatibility symptoms or other obvious problems with the way my machine running.

My concern is that I’ve looked in my Zone Alarm logs and there are multiple entries in the OSFirewall log saying

avast! antivirus service was prevented from changing the behavior of ZoneAlarm Pro by modifying the file WINSYSDIR\ZoneLabs\lib*

After many reported blocked attempts to change this file, it appears that Avast then tried to change other ZA files, and was blocked. The executable which is trying to make the changes is c:\Progam Files\Alwil Software\Avast4\ashServe.exe

Why would Avast be trying to modify ZA files? I can see why ZA would not want its files altered, as that’s the sort of thing malware would attempt, and I can see why Avast might be scanning ZAs files, but why modify?

This didn’t happen with ZA 7.0.483 - only since upgrading to ZA 8.0.059

Anyone else seen this, or can help? Thanks

Chris

ASHSERV.EXE is the Standard Shield. As avast! is not alerting you, a straightforward explanation would be that avast’s scanning of files in this location is being reported by ZA as an attempt to modify them. Have ZA introduced enhanced/new self-protection?

avast is not trying to modify the file but scan it…

Thanks - it would seem logical that Avast was trying to scan it, but why is it doing so in a way which ZA interprets as modify?

I have posted a similar query on the ZA web site to see if anyone knows why ZA is interpreting Avast’s action this way (annoyingly, the ZA Forum replaces every occurrence of Avast with ** bleep **)

I have also excluded the ZA folders from Avast’s scanning, to see what happens.

Chris

Another ZA glitch… as many it has…