It is a known issued and Avast is working on a solution. Will probably not be fixed till after
Avast 2016 is released.