Reply to thread

Message: <blockquote data-quote="RejZoR" data-source="post: 689381" data-attributes="member: 57233">The problem is not on my end. avast! team screwed something up with v17 release and from their latest words, they won't be fixing this anytime soon. They are bringing in some new changes and that will fix this problem. Which might take a month or two. Basically, I'm expecting it to get fixed in avast! v18. Which is rather disappointing... I also don't get it why running my 2016 config file first (and not even applying it) fixes the issue with v17...</blockquote>

Top