Thanks DavidR, Avast support forum, for sharing knowhow.
The two AAVM scanning warning messages appear isolated events that occurred when access was denied (returning error, 00000005) as you say. There appear no other associated entries in event viewer.
23-6-08
AAVM - scanning warning: x_AavmCheckFileDirectEx [UNI]: C:\DOCUMENTS AND SETTINGS\MKIS\APPLICATION DATA\MOZILLA\FIREFOX\PROFILES\FYCG5LV2.DEFAULT\PREFS.JS (C:\DOCUMENTS AND SETTINGS\MKIS\APPLICATION DATA\MOZILLA\FIREFOX\PROFILES\FYCG5LV2.DEFAULT\PREFS.JS) returning error, 00000005
17-6-2008
AAVM - scanning warning: x_AavmCheckFileDirectEx [UNI]: C:\DOCUMENTS AND SETTINGS\MKIS\APPLICATION DATA\MOZILLA\FIREFOX\PROFILES\FYCG5LV2.DEFAULT\PREFS.JS (C:\DOCUMENTS AND SETTINGS\MKIS\APPLICATION DATA\MOZILLA\FIREFOX\PROFILES\FYCG5LV2.DEFAULT\PREFS.JS) returning error, 00000005.
‘FYCG5LV2’ a bit of a worrying looking reference (profile or account reference perhaps?). I just didn’t like the look of it.
Default pref. Files seem to be preference settings from user customization of Mozilla toolbar functions which may have tried to launch at startup but access subsequently denied as part of Mozilla security I presume – and so error registered for the event.
http://www-archive.mozilla.org/catalog/end-user/customizing/briefprefs.htmlI’m not worried about the two files. I thought perhaps something more may have been happening than actually was. The Mozilla program / toolbar was uninstalled later and no entries have since registered outside the two originals.
‘FYCG5LV2’ still a bit worrying but can’t see any record of malware come to surface. So have to say okay. May be looking for too much that isn’t there. And I'll keep a closer eye on how I write any suspect urls from now on.
Much thanks
mkis