This problem was reported a few releases ago, and confirmed by several users when 10.0.2206 and 2208 were released as well.
Back in version 9 Avast technical support said it was a bug and would be fixed in the next release, but it hasn't been fixed and no comment from Avast on any topics about if it will be fixed or is now considered normal.