<snip>
and alanrf.....have check the thread you suggested. Is this a new problem between Avast & ZA, as I have had both for approx 5 years now without any form of dispute betwwen them.......that is until the most recent updates of Avast.
That thread also mentions the disabling of the second AV, a point which seems to have been missed. Your image clearly shows that the culprit accessing the avast4.ini file is the ZA anti-virus module.
My main concern isn't that this may or may not be a problem which has been fixed by the latest release which I think is an aside to the real issue, having two resident AVs installed on your system.
So you effectively have two resident anti-virus scanners on your system and this isn't recommended and this is even if there weren't any problems with the avast self-defence module. Uninstall/disable the ZA anti-virus module would resolve the problem and you could have the self-defence enabled and protecting avast now.