In any case, it is a cosmetic bug… I hope this will be fixed until Avast 2016 SP1 release.