Just figured it'd be worthwhile to let people here know, so they don't find it wiped off of network shares for them 
]]>Just searched their site and Knowledge Base no mention of the error - base, driverpacks or autoit
and nothing comes up at all for false positives in the KB Period.
They do tout thier low false positive rate in thier advertising -
and now I can only assume that low figure it is because they don't keep track
When they find False Pos. nor when they are reported.
I am sticking to SARC...
]]>edit, well, still false on roe.exe
]]> Just figured it'd be worthwhile to let people here know, so they don't find it wiped off of network shares for them ]]>EDIT, 1, deleted.
EDIT 2
yep. after update it triggered on base80417RC, in particular on roe.exe
edit 3
(and on dps_base.exe too.)
AVG has also reported mute as a virus and they have updated their definitions successfully.
there is nothing we can do - this must be reported to the offending (offensive?) company
please update your definitions... double check that the problem still exists and report to avast as a "False Positive".
Please choose a good title in the future I belive 'Base' was not detected as a virus - 'mute.exe' was?
]]>