I have to apologize, I had abandon posting this thread because I had Whitelisted a few more of Avast’s executables and thought I was ok but it was still not updating.
I had searched the forums and did find a similar post that was viewed over a thousand times but had no reply to it. I had copied the post and intended to adjust it to my own issue but I Logout of the Forum. The post did stay open for a long time before I checked out.
I come back to post for real this time and I already have a post ??? Sorry, it was not my intention to repost somebody else’s stuff. So time for a big EDIT, for the people who had already answered, please review the corrected information.
I have problems with Avast Free Antivirus and the Windows 7 Firewall that is set to block all outbound. (Whitelist-mode)
I’m REALLY using the Avast Free Antivirus version 11.2.2262 ( NOT v.8 ) down loaded last week from here. ( NOT v.8 )
It’s running on a desktop with Windows 7 Ultimate 32 Bit.
I created Outbound rules for the AvastSvc.exe, ashUpd.exe, instup.exe and AvastUI.exe
When I want to update the virus definitions, it flashes an error but it does update as my present Virus Definition is 160807-0 and it dates from 8/7/2016… even if I see some error flash, it seems to work.
When I want to update the Program, it contacts the server, Step 1, then it repeats Step 2 half a dozen times and finishes with:
You aren’t using the latest avast free version, that is 12.2.2276.
Not that that would make any difference with your problem of finding what you need to allow.
The problem most will have is trying to help anyone with avast free 8.0.1489, which is positively ancient by AV standards. Most will have forgotten the files that would require internet access. Your topic has actually been a bit of a memory for me.
I think you are going to have a bit of a hard time achieving this as there is a scheduled task to check for emergency updates, C:\Program Files\AVAST Software\Avast\AvastEmUpdate.exe, but if there is one present than a uniquely named executable is created in the C:\Program Files\AVAST Software\Avast\setup and C:\Program Files\AVAST Software\Avast\setup\emupdate sub-folders.
See image example/s.
You will notice a whole shed load of uniquely named sub-folders of avast\setup and these for the most part will be empty, but I suspect that they will have been created and used for emergency updates checks.
EDIT: See new image 3 as that shows my firewall having allowed one of these uniquely named files
The simple answer is this, you hired Avast to keep you safe.
Either trust it and allow all of it access or, fire it and hire something else that you intend to totally trust.
David, Thank You for the precise information.
I delete the “Emergency Update” task as it was no use for the way I’m set up.
For the “Avast settings backup” task, I switched it from Daily to Weekly.
Since it did finally update, all is well for now, I will be switching the rules off one by one and see which stops the updates.
I understand the point about having a constantly changing name but for anyone running a REAL hardware firewall, this condition is untenable.
Bob… you are out of order.
You, if you want, can put your (computer) life in someone else’s hands… your prerogative.
I, will never.
Please Dude… when you do not know the answer… do not reply. You have no right to waste other people’s time.
You may find that avast will reinstate the emergency update function, but if you haven’t given firewall permission it doesn’t really matter if it runs or not, it would fail.
The emergency update however, has a purpose that I feel is worth persevering with. IN the event of there being a problem with avast and the current update setup can’t/doesn’t work (broken) then that is where the emergency update comes into its own.
As for settings backup, generally I only do that prior to any program update, outside of that I haven’t felt it that necessary. Possibly because I do weekly drive image backups and keep 6 backups, this too would cater for my settings backup should it be required.