This error seems to be solved (at least for me) in Avast 4.6.623

Thanks Avast team :slight_smile: