I haven’t used Avast in a number of years and when I did I was using Comodo FW. Just installed latest version tonight. Can’t get a connection to host via right click tray icon or inside GUI screen. I KNOW it’s the Win7 Firewall as I can get a connection to the host if I turn off the Win7 FW briefly.
I’ve browsed down the files in the Avast program folder and only see one (AvEmUpdate) but am not sure that is the one, since the properties/details say Avast Emergency Update. What specific Avast filename(s) do I need to grant access through the Win FW? And do those files require just Outbound access? or do they need two-way access?
I do know how to add new rule(s) in the FW Advanced Settings if you can just provide the file name(s) I need to create rules for. Thanks in advance for your help with this pending issue.
There are several, and there may be even more most would require both outbound and inbound.
The AvEmUpdate.exe that you mentioned, checks for emergency updates outside of normal updates, if one is found I presume it would require inbound connections to install it.
AvastSvc.exe is the main service, controlling the various shields.
Also AvastUI.exe, ashUpd.exe there is one I recall from earlier versions, instup.exe (Installation & Update function). EDIT: instup.exe is in the avast\setup folder and I have noticed instup.dll (I don’t know if this requires access) also in the setup folder.
I have never used the win7 firewall, I have always used a 3rd party firewall (much easier to control) until I got windows 10 and on that system I use the windows firewall.
And thank you, DavidR. I was pretty sure the Avast Service monitored the shields and am thinking it will need in/out access. Just don’t remember what their updater is called. I’m thinking there were two files back in the day that needed FW clearance both out/in: ashUpd.exe (which I can see now in the program folder, having overlooked it earlier) and ashQuick.exe as well, which I think has to do with the virus scanner?
But I’m sure the program has changed so much since I used it last, I don’t dare trust my aging memory. I’ll see if any other Avast helper’s have any further suggestions to be certain of the rules before I build in my not-so-user-friendly-FW rules lest I have to do it twice.
Well, I’m stumped. I’ve made inbound/outbound rules in my Win7 FW for all 5 of the the files we discussed so far and I’m still getting “Host Unreachable” with an update request. When I then turned the FW off, it connected and updated definitions for me. Turned my FW back on. I really don’t want to have to manually do all this every couple days if there’s a better way.
Any other thoughts on what file may still needs access to a connection in/out?
Okey-dokey. I’ll go out and make a rule for aswidsagent, aswrundll, avlaunch, avbugreport and avdump32 as well and see what happens. I did a rule for the others on your list. I will report back my findings.
To start off, I don’t see aswidsagent.exe in my program folder, nor would Win Explorer find any such file name. I’m running the free version. Does this file go by another name? I set up the rules for all the others on your list (see screen shot Inbound rules. I set up the same rules for outbound as well). Note I did not specify ports. Do I need to? Still no success getting to the host server though.
OK, I browsed the sub-folders within the Avast program folder and found something similar: aswidsagenta.exe (note the “A” on the end of the filename) that sits in my Avast x64 sub-folder. Is this the same file and should I do connection rules in/out for it as well?
On that image I posted there are two columns ‘Network’ and ‘Anti-Leak’ the important one is the Network (access) one, the Anti-Leak is prevention of changes of the file. Unless the file has Green Square for it the Network column I don’t think you need it, but having it shouldn’t hurt.
I have seen the aswidsagenta.exe mentioned in the forums, I’m not sure if this is OS dependant or 64bit dependant.
Unfortunately the image of the avast processes in my firewall are from my XP Pro 32bit and my win7 netbook is also 32bit and I have that running an old version of avast.
I also have a windows home 64bit on my laptop, but that I let the win10 firewall handle I haven’t needed any interaction with that.
The location on my XP system is C:\Program Files\AVAST Software\Avast\aswidsagent.exe and no aswidsagenta.exe.
At present there are differences in XP as avast prepares to end program support (end of November) for XP and Vista, so I don’t know if this aswidsagenta.exe is one of those differences.
Well, I went on and allowed aswidsagenta.exe it to connect in/out but still can’t do an update without turning off the firewall. I won’t give up on this. I’ll go out to the Win7 forums and see if they can possible help on why the firewall is blocking, but I’m sure they will refer me back to Avast forums for help finding the file(s) that I have not done an allow rule for. But it’s worth a try. I’ll check back here to see if anyone else has any ideas on what my problem might be. Thanks so much for your time spent and help on this problem thus far, David.
Well, when I first ditched Comodo FW and chose to use the Win7 Firewall, I WAS using the default settings. Avast would not install… even when I built an Allow Connection rule in the Advanced FW settings for the Avast setup/installer to get through to the internet. So I’m not sure that will solve my problems either, Pondus. Thanks for that suggestion though, and I’ll keep it in the back of my mind as a possible option.
BINGO! Found my problem! Told ya I don’t give up, David. LOL I opened up my WinFW Notifier GUI (I’m new to that SW, too, and never looked at the log) and found a log that showed me connection attempts today. There were a bazillion attempts to get out by a file in the Avast Setup folder called instup.exe. The moment I gave it outbound access, the GUI updater worked just fine.
Consider this one resolved! Peggy is a happy camper now.
Yes you did, and I immediately remembered the filename. But silly me, I was only looking for the file in the main program folder. My WinFWNotifier log told me where it was in residence and I indeed found it there. Thanks again for your help David.
;D