looks like it was solved on Avast side - please re-test.