Avast has destroyed my MSYS2 installation

Avast Free Antivirus / Premium Security
1

Hi all,

I was doing an MSYS2 update, and avast suddenly decided that C:\dev\msys64\usr\bin\gpg-agent.exe is a virus, and moved it to the virus box(!).
This caused the package database to cannot be signed, which corrupted the package databases.

So, my MSYS2 installation is now useless.

Unbelievable!

2

How to report >> https://forum.avast.com/index.php?topic=14433.msg1289438#msg1289438

3

Can confirm that this also happened to me. I have now had to whitelist the whole Msys2 directory and reinstall from scratch. Stuff like this shouldn’t happen!

4

I’m running into the same problems, even with with the MSYS2 directory whitelisted under “exceptions” in the file AND the behavior shield.
Already submitted a false-positive report. Will report back when I get an email telling me what actions they’ve taken.

Symptoms:

  • installation breaking before it completes
  • operations failing during the installation in which you can “retry” but which never succeed the n-th time either
  • update issues when using pacman to update packages (whitelisting under “exceptions” didn’t fix this problem for me!)

Current work-around is disabling avast. Either disable the file/behavior shield or uninstall avast completely.

5

I don’t understand why avast, by default, deletes stuff without asking first.
Doesn’t avast trust it’s users?

6

It has nothing to do with thrust but has everything to do with protection.
Most users unfortunately aren’t experts in that field.

7

I understand what you’re saying, the problem I have is that
this action taken and too many false positives can be a disaster for
the user when avast is wrong.
Should we just accept that for “the greater good” ?
we should demand better

8

Since the reporting of a false positive is fairly simple and the subsequent resolution is fairly quick,
I can’t think of anything better.
It’s certainly better than allowing something a users deems a false positive to infect their system.
Your computer, your choice. I know what mine is. :slight_smile:

9

Under Settings, Components, File Shield, Customize, Actions … you can select what Avast will do when it thinks a file is a problem. One of the choices is “Ask”

https://lh3.googleusercontent.com/EpCDgo1wiaMQ15-rh4l2okJOIbTLax5ShIegEtUsTkZNRufjSe4fFTGwKzKMNoxFWpWV8BW8miSdHboy60L0ujGI4MJAb1lnjyUIJWhVwaKalROS0VY3-n-da3ZX_-S7ljxl93M0P9KlBA-5LavzctZnrncg7ePOKOFSM3ZrQbWEKEKnVtjimFUylv0tOoOtW2SUmLMKGAbALozXdHWiP77PE1sTJ6qsxitQ0zFoHrbPN2DC2yibwTkQ1pKQPO2xppxCRHeo0Pwvb8Gu_nSFOugleuLpsesZl2-bztjIWTMRBhHk7QE1GJ2xvcjGlrwVgn4lwjQXzh9d3ev6Xh7h9NRvgewBA1U_NNVpmhc1B2bdE1trriAw9ASXDgHp1tvouQDyr6XpejP4GUZimgeLBciQIR4VZXkJr_GZJVQIVDkBMZUgKhMFM4CFYTw6l3UzC2lskyqixIeLSVUAk9DndV3WGas_A0xBs8049CE4aZ-hTo1sOxxeQ9VYWDMlRBK9-KAkGAeeK9AHWjxvi0xjsVX7xK7EFArktslLs6Hnke1CZFKBxm1Cg96ohLx8CNqxASZAwYAtkL6mXNj60tfOonOfpfSJNEmW3NrteOo=w934-h525-no

10

Looking at the date of the first post, this is an old issue. Is there a reason it’s not resolved? I just had the same problem on a fresh install, and it insists on interfering with installation through excepted paths. I got ticked and fully disabled avast shields so it would quit breaking my crap. Avast interfering with programs that are fine, blocking exceptions, not being able to restore a deleted file, and all the intrusive crap it does recently is becoming too much. Hit the point where i’m tempted to start looking for a new AV.

11

Since you don’t give any specifics, it’s impossible to answer you or help you.
If you’re looking for help, start your own topic and give specifics. If you just wanted to get something off your chest, you’ve already done that.

12

This just happened to me, that is serious shit, waste of time. I am unable to restore as the filed is not even in the chest. I am uninstalling this shitty AV from all my comp and will not recommend it to anyone anymore.

13

I ran into this problem when installing some MSYS packages (NOT while installing MSYS itself). I think I’ve managed to recover from this by doing the following:

  • add the msys64 folder (or maybe msys32) to Avast exclusions so it doesn’t happen again (hopefully). The folder is likely C:\msys64.
  • disable all Avast shields (otherwise signing will fail apparently)
  • reinstall gnupg from an MSYS terminal (pacman -S gnupg)
  • re-enable shields

Also consider using bruce_b’s answer to get Avast to (again, hopefully) ask before nuking false positives.

14

Hello,
report the potential false positive through https://www.avast.com/false-positive-file-form.php, please.

Milos