Agnitum's Outpost Pro 3.5 don't let Avast! Pro update

Hi,

I’m having problems with Outpost Pro because no matter what rule I create it don’t let Avast! setup access internet, are you aware of this issue in the firewall???
Do you have a workaround for this???

Tnx in advance!!!

martosurf

When I’ve used Outpost in the past, this happens very rare but, anyway, you can try allow and check for remember the avast.setup ask for connection. Close and EXIT Outpost. Boot and start Outpost again to try if the entry is correctly saved into its settings :wink:

The best option is if you have an entry for avast.setup is to delete it and do a manual iAVS Update, this will force Outpost to ask again, ensure you accept it as a trusted application.

I have had this happen previously (Pro v3.0) with a different application permission and despite it having the correct permissions it couldn’t access. The only solution was to delete the entry and force Outpost to ask again.

tnx a lot guys, but Agnitum have a bug that block internet access at boot time if avast! tries to update itself, the only way I see is to tell avast! to not uptdate when loggin on but do it 3 minutes after.

tnx again for your support and quickness :slight_smile:

What connection do you have ?
I use dial-up and have my Update settings set to ‘ask when update is available’ and that is fine for me and no blocking with Outpost.

If you use broadband, you can extend the delay before avast checks for updates by editing the avast4.ini file [InetWD] section and add or amend the line entry in Red.

[InetWD]
AlwaysConnectedWaitSeconds=60

You can set for longer than the 60 second example above, hopefully that will avoid the Outpost bug you mention. Somehow I don’t think this is a bug in outpost as I haven’t seen anything about not allowing connections at boot time and avast doesn’t connect that quickly. avast checks for the presence of an internet connection (it doesn’t establish one), if one exists then it would check for updates.

Dearl DavidR, I have broadband connection but the problem with Outpost and Avast! when logging on is Agnitum wrongly identifies avast! as some type of attack and block all access of AVAST.SETUP to the net, bypassing even the rules that explicity says to TRUST and LET avast.setup connect to internet, I think this real is an Agnitum Outpost PRO bug.

Thank you very very much for your advice, I will try and tell!!!

Best regards !!

Outpost doesn’t block it automatically, it requires user input, you at some point must have denied it access and that is remembered.

Do as I have previously suggested, open the Outpost interface, select, Options, Applications:

The best option is if you have an entry for avast.setup is to delete it and do a manual iAVS Update, this will force Outpost to ask again, ensure you accept it as a trusted application (see image).

I have had this happen previously (Pro v3.0) with a different application permission and despite it having the correct permissions it couldn’t access. The only solution was to delete the entry and force Outpost to ask again.