I'll know in 30 minutes when the next scheduled auto update runs whether or not this was successful or not.Are you using the Pro version?
But if you insist the minimum I can set it to is 240 minutes, then I'll defer to you.I'm an user like you... they (Alwil programmers) set this minimum to 240 minutes to avoid servers fload.
And yes... with the firewall disabled, Avast still cannot seem to contact the mothership automagically.Are you checking your avast logs and there is stamped that you could not get the update automatically?
How soon after the automatic update failure "red flag" does your manual update work ... immediately ... after 10 minutes?
I know it sounds like a complete disconnect but do you have Windows Automatic Updates set to automatically update your system?
Tech, you said you use Comodo Firewall... could you post your relevant firewall config to see if mine looks similar?I think I'll write down and does not post a screenshot as it won't help that much in this case (configuration won't be shown in the screenshot).
"AlwaysConnectedWaitSeconds=" setting and had that set up to 10 minutes and still no go.I suppose you've wrote:
I suppose you've wrote:
AlwaysConnectedWaitSeconds=600
Did you change the service logon?Yes, I tried the administrator account and my own account (which has admin privs) and neither seemed to make a difference as well.
19:18:51 min/gen Started: 29.01.2007, 19:18:51
19:18:51 min/gen Running setup_av_pro-37c (892)
19:18:51 nrm/sys Operating system: WindowsXP ver 5.1, build 2600, sp 2.0 [Service Pack 2]
19:18:51 vrb/sys Computer WinName: MICINA
19:18:51 min/sys Windows Net User: SYSTEM
19:18:51 min/gen Cmdline: /refresh /noreboot /updatevps /verysilent
.
.
.
19:19:14 min/gen Return code: 0x20000000 [Something done]
19:19:14 min/gen Stopped: 29.01.2007, 19:19:14
I used to block svchost in my firewall when I didn't want windows update any outbound checking.Excuse me for runnig out of the topic, but I got curious about this, could you please say why do you do this? Is it for expect the patches of Windows Update to be more mature? Or did I misunderstand you? I btw observed that Microsoft .NET framework 2.0 accesses Microsoft's site each time I click at Start menu.
Interestingly I get lots of blocked inbound access to the DNS port with n/a as the Process Name, but it doesn't appear to have any impact on browsing etc.I believe the reason that happens is that the browser accesses the DNS subsystem directly as your local user. SVCHOST is used by the "Service Account". I must have blocked it at some point in the past few weeks because I got sick of seeing the popups and didn't realize the overarching importance of this obscurely named process.
Excuse me for runnig out of the topic, but I got curious about this, could you please say why do you do this? Is it for expect the patches of Windows Update to be more mature? Or did I misunderstand you? I btw observed that Microsoft .NET framework 2.0 accesses Microsoft's site each time I click at Start menu.
So if you have a similar problem, look into these things closely:
1) Firewall Logs - See if you are denying critical DNS (port 53) traffic.
2) Check to see if your DNS servers are valid and answering queries.
Hopefully this post will help other people from pulling out their hair if they run across this.
Thanks for all your help out there in Avastland! Cheers!