Hi everyone, I just spent over an hour trying to upload a payments list from my Paymaker software to my bank. It was working fine last time I used it in December, since then my Avast Premium Security has updated itself. I tried adding the Paymaker software to the Firewall ok list, but it didn’t add it despite three attempts. The only solution was to temporarily switch off all the shields, which is not exactly the purpose of antivirus software.
How can I stop Avast from blocking my Paymaker software ?
Can you be a little more detailed, is Avast Alerting or you just can’t connect ?
If it is alerting a screen shot of the Avast Alert with the More Details option selected may help.
If it isn’t alerting there is a possibility bank may not like the man in the middle and can’t confirm its you/legit.
No, Avast is not showing any alert.
In my Paymaker program, when I have prepared the payments, I click on “Transfer Payments” and it shows me a message at the bottom (in Paymaker) that the connection to my bank has failed and “check Firewall settings”.
It was all working fine back in December and for several years until then.
In my Avast’s Protection log I have hundreds of entries for the three or four times I attempted to transfer the payments.
These include dozens of
windows/System32/svchost.exe
windows/System32/dasHost.exe
ProgramFiles\Bonjour\mDNSResponder.exe (Bonjour is in the firewall ok list)
In the Firewall list “All”, neither CLX Paymaker nor Paymaker is listed, despite my three attempts to add it last night. Neither is it in the “Active” list.
This is extremely annoying. I do not want to have to switch my security off every time I make payments.
First, I’m an Avast user and not an Avast Team member.
Unfortunately I can’t see what you can see, I don’t use Paymaker and have no idea how it works or interacts with the bank or how Avast might interact with Paymaker.
Avast’s Web Shield acts like a middle man (so that it can scan for malware, etc.) this interaction could conflict with what Paymaker is trying to do in connecting to the bank. At that point it is also possible the Banks security identifying who/what is connecting and is it legit.
So the problem is identifying where this conflict might exist. In disabling Avast completely doesn’t pin where the problem/conflict is, you try just disabling the Web Shield and not all and try connecting again.
If that works it may be possible to add Paymaker’s executable file location to the Avast Exceptions list.
Try not to make too many changes at once or the issue will remain as to why it happens or what Avast element/component.
I believe the firewall thing is a red herring as that is what Paymaker thinks it might be.
Hi David, OK, I was able to add three folders with Paymaker files in them as “exceptions”. Avast definitely did not want to add the .exe file as an App to the firewall list.
I don’t know whether it was necessary to add all three folders mentioned but I’ll test it tomorrow. If it works I’ll remove the folders and just add the .exe and test that (our daughter will be surprised at keep getting small sums of money - (the test payments), haha).
Personally I don’t think if you even could add that .exe file to the firewall list it would change anything.
As I said:
I believe the firewall thing is a red herring as that is what Paymaker thinks it might be.
The additions to the Exclusions List I believe would include/cover the firewall and the use of wildcards ‘*’ would save having to have 3 different exceptions. url/domain-name/wildcard/
I removed the three folder names from the Exceptions list, and just added the Paymaker exe file to the Exceptions list. I tested it and it’s working. So that was all it needed. Avast refused to look upon the exe file as an “app” though, which I find strange, because there are other .exe programs in the Allowed Apps list. No matter, it’s working. Thanks for your suggestion about adding it to Exceptions, David - I couldn’t find that option and had to google to find out where it was ! (top right Menu → Settings → Exceptions)
I assumed (dangerous) having entered the Menu function to get to the Firewall settings, you would be able to find with a little Screenshot.
Good that you now have it resolved.
You can flag my post as the solution.
Thanks for that, though I should have been clearer, make the post that resolved it for you 
Done ! Sorry 'bout that…
1 Like
No problem, I could have explained it better