<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20605">
<style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div dir=""><p dir="ltr">> Please, everyone who has encountered this report it to Avast as a false positive.</p><p dir="ltr">I had that problem with the <em>previous</em> daily build -- it was mildly exasperating until I realized what was happening (Avast! was quietly deleting the EXE).</p><p dir="ltr">My workaround then was simply to whitelist the CHIRP installation directory -- and I submitted a false positive report at the time. Newer versions may need newer reports -- I’m unsure of the granularity of Avast! versioning.</p><p dir="ltr">However, whitelisting the directory is a one-time, everlasting workaround.</p><p dir="ltr">(That does of course presume that the user trusts CHIRP to remain virus-free.)<br></p>
</div></div>
</body>
</html>