I'm running Windows XP SP3 with **bleep** Pro and Zone Alarm Pro 8.0.059 (firewall only)
I have ZoneAlarmCompatibility=1 in **bleep**.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 from the OSFirewall saying
**bleep**! 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, ZA reports that **bleep** 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, which appears to be genuine **bleep** not malware.
Why would **bleep** be trying to modify ZA files, or why would ZA think that? 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 **bleep** might be scanning ZAs files, but why modify?
I've asked a similar question on the **bleep** forum
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
Operating System:Windows XP Pro
Product Name:ZoneAlarm Pro