Avast WEBforum

Consumer Products => Avast Mac Security => Topic started by: ItsTony on October 10, 2020, 08:23:27 PM

Title: Sorry, we couldn't move this file to the virus chest.
Post by: ItsTony on October 10, 2020, 08:23:27 PM
Anyone else getting this when they do a deep scan?

(https://i.imgur.com/L7Oe3nt.png)
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: Gary326 on October 10, 2020, 09:08:40 PM
I have the same problem with catalina 10.15.7
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: lokelani53 on October 11, 2020, 01:20:01 AM
Also getting this message today.  Catalina 10.15.6   
Noted a posting from earlier this year suggesting this was a false positive and would be addressed when virus definitions were updated.  The file that is supposedly infected is not one a user can remove, from what I can see. Hopefully it is truly a false positive.  I do regular scans and this is the first time have ever seen a MACOS:Pirrit.  There was a second one as well today, but the file was some microsoft one in the library and the threat was removed by AVAST.
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: guillaumelou on October 11, 2020, 03:26:07 PM
Same here with Sierra
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: lokelani53 on October 11, 2020, 05:23:18 PM
Based on reading that an earlier instance of this issue was supposedly deemed a false positive, have sent a message to AVAST asking about it.  If/when I get a response will post in this thread.
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: lokelani53 on October 11, 2020, 07:01:09 PM
No email response from AVAST thus far, but a deep scan this morning has just resulted in a "No Threats Found" message.
Title: Re: Sorry, we couldn't move this file to the virus chest.
Post by: lokelani53 on October 16, 2020, 03:17:01 PM
Just got a reply from Avast (Friday, Oct 16) confirming that this was indeed a false positive and and was corrected on October 11 and that we should not get that message again.