Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Snagglegrain on April 05, 2010, 11:25:42 PM

Title: manual update problem when set to auto update
Post by: Snagglegrain on April 05, 2010, 11:25:42 PM
I am running 5.0.462 and have avast set to auto update on two different computers.
One has virus definition version 100405-1 and the other has 100405-0.
When I try to manually update the 100405-0 computer, it says I am already up to date.
Did that second update get pulled or something?
It's been like this for over an hour, and I have tried to manually update at least three times.
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 06, 2010, 12:19:00 AM
No, it is more likely to be a hiccup (virus definition version 100405-1 is the latest), try a reboot and see if that bump starts the UI reporting of the version you have.

Or try a repair of avast. Add Remove programs, select 'avast! Anti-Virus,' click the Change/Remove button and scroll down to Repair, click next and follow. This has in the past resolved this out of sync issue between reported and actual virus definitions version.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 04:24:27 AM
Hello David

I rebooted and that did not fix the problem.
Then I tried a repair, and that did not fix it either.
I tried changing settings from auto updating to manual, but that didn't work.
I tried a few other settings changes, like auto update intervals.
It's still not updating, and is saying virus definition version 100405-0 is current.

I have been running this version for about a month with no updating problems whatsoever.
My firewall is not blocking updates.
I haven't added any new software.

What now?

Edit: I just read on another thread about updating problems to reboot after repair.  I have not done that.  Will try and report back.  :)   
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 04:51:53 AM
Reboot after repair.  Not fixed.  Manual updating says I am current.
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 06, 2010, 05:15:36 AM
I think that the reboot may have been the catalyst for the resolution (in the other post) rather than the repair.

Since you aren't massively out of date I would:
a) set the update back to auto.
c) set the update interval to 120 minutes, the minimum interval for avast 5.0 free.
b) change any of the 'other' settings you mention to their default value.

Now just leave it for a while longer.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 05:58:50 AM
Okay.  Good advice.  If after the next update (tomorrow), it still hasn't updated, I'll post back.

What about rolling back (or deleting) a definition file so as to trigger an update from today?
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 03:02:27 PM
I turned on the pc this morning to see that avast had updated to 100406-0.
Hopefully this was just a hiccup, as you suggested, David.
Thanks for the help and advice.
What can you tell me about rolling back (or deleting) a definition file so as to trigger an update if/when this situation arises again?
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 06, 2010, 03:09:21 PM
You're welcome.

As to your previous post (Bad idea):
Personally rolling back (if you are talking system restore) is worse than doing nothing in the interim as you could be introducing other issues.

You can't delete a definition file because of a) self-defence and b) avast 5.0s virus definitions are fully integrated into a number of areas, so that too could cause complications rather than solutions.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 03:12:55 PM
You're welcome.

As to your previous post (Bad idea):
Personally rolling back (if you are talking system restore) is worse than doing nothing in the interim as you could be introducing other issues.

You can't delete a definition file because of a) self-defence and b) avast 5.0s virus definitions are fully integrated into a number of areas, so that too could cause complications rather than solutions.
Yes, I was referring to the latter- deleting a definition file.  I'll follow your advice and not do that.
David, is this update 'hiccup' a common problem with avast5?
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 06, 2010, 03:20:58 PM
I haven't experienced it at all from the first regular non-beta release of avast 5.0. Thought there are some that have reported this after doing an update and a reboot normally resolves it; I haven't seen any common reason, e.g. a particular OS or 32bit or 64bit versions of an OS.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 04:22:00 PM
Good news.  I saw that 100406-1 was available, so I did a manual download and it worked fine.
I should mention that last night (before 100406-0 was automatically downloaded) I also removed all firewall permissions in order to make it ask for connection rights again.  That may have had an effect on things.  Glad it's back to working properly.  And I hope it remains this way!  :)
Title: Re: manual update problem when set to auto update
Post by: bong2x on April 06, 2010, 04:27:12 PM
 ;) avast prompt me also that when im going to manual update that the auto update is on ;D

this is in my case:

i run only 921kbps mobile phone to connect in my pc.

my automatic update is on, and every time i open my computer the update takes about 5min and don't prompted me that i am updated.
so to make sure that it is updated i run the manual update, but its prompted me im already updated :o

but ok because the it say im updated i leave it that way and next 6 min prompted me VDB is updated.

so on the next day i disable the auto update and make it manually.
but then by the time that i manually update the definition it take so long so i thinking of refreshing i cancel it and start update again. it say also im already updated :o

but i last week i turn on again my auto update and leave it so that it will update automatically.

but this morning again auto update is more longer so im manually update again it say again that im already updated.

so maybe that auto update cannot be take place by manual update if the update is being download by the computer. or double update is making that prompt.

so my new motto be patient and wait for auto update is done ;D

Regards!!!
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 06, 2010, 06:06:37 PM
Good news.  I saw that 100406-1 was available, so I did a manual download and it worked fine.
I should mention that last night (before 100406-0 was automatically downloaded) I also removed all firewall permissions in order to make it ask for connection rights again.  That may have had an effect on things.  Glad it's back to working properly.  And I hope it remains this way!  :)

I'm glad too that it all appears to be working fine, though personally I would have let the auto update do the download for further confirmation that the primary update method works.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 07:17:07 PM
I'm glad too that it all appears to be working fine, though personally I would have let the auto update do the download for further confirmation that the primary update method works.
That thought crossed my mind, David.  But since two things were broken (auto updating and manual updating), I opted for the instant gratification of manual updating.  :)  And now, I wait to see if the next release makes it onto my system via the auto updating route, though I have already seen that auto is working again with the magical  ;) appearance of 100406-0 on my computer this morning.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 07:19:40 PM
Thanks for the details and the advice, bong2x.   :)
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 06, 2010, 10:57:58 PM
Okay, I'm patiently waiting for this one computer to auto update to 100406-2.
My other pc installed it about half an hour ago.
Keeping my fingers crossed.

Edit: Aha!  I didn't have long to wait.  Virus database has updated.   ;D
Title: Re: manual update problem when set to auto update
Post by: bong2x on April 06, 2010, 11:09:19 PM
ok make sure that you have the same as the picture. and and refresh your net connection ;)

edit: sometimes mine i set it in 360min but its originally 60 its fit in my dial-up somtimes. best fit is 240 :)

and better also to auto detect
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 07, 2010, 12:13:24 AM
The minimum setting is 120 minutes for the update check, anything lower is ignored I believe.
Title: Re: manual update problem when set to auto update
Post by: bong2x on April 07, 2010, 12:20:43 AM
ah ok, thanks DavidR :D

Title: Re: manual update problem when set to auto update
Post by: YoKenny on April 07, 2010, 12:07:50 PM
@ Snagglegrain

Go to PROFILE then Modify Profile then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.

DavidR an avast! Überevangelist has his system's information in his signature.  8)
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 07, 2010, 11:35:02 PM
I'm glad too that it all appears to be working fine, though personally I would have let the auto update do the download for further confirmation that the primary update method works.
Auto update appears to be working fine once again.  This v5.0.462 sure is a nice improvement over v4.8.  :)
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 09, 2010, 10:01:31 PM
This issue continues to visit me.  Today on my other computer 100409-0 is the last update, even though 100409-1 has been out for many hours.  An attempt to manually update does not result in a message saying "Already up top date", but instead shows the amount of time taken, like 27s, without any of the other usual details like Server or Downloaded files, etc.

I suppose I shall try a repair, as DavidR has previously suggested.  But I wonder how common this update hiccup condition is with v5.0.462? 
Title: Re: manual update problem when set to auto update
Post by: Asyn on April 09, 2010, 10:30:00 PM
You might want to try the pre-release version 5.0.492...
http://forum.avast.com/index.php?topic=58183.0
asyn
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 09, 2010, 10:49:57 PM
A reboot triggered an auto update to 100409-1, which doesn't fix my little problem of manual updating not working when an update is available.

@ asyn... thanks for the suggestion.  Have you read on a changelog that 5.0.492 deals with this issue?
Title: Re: manual update problem when set to auto update
Post by: Asyn on April 09, 2010, 11:02:15 PM
@ asyn... thanks for the suggestion.  Have you read on a changelog that 5.0.492 deals with this issue?

It's 5.0.499 now, just received the update... ;D
And no, haven't read about it, am not sure, if it's a real problem after all, as the update servers need some time till the receive the update for distribution, so maybe it's just about a little patience... ;)
asyn
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 09, 2010, 11:31:05 PM
It's 5.0.499 now, just received the update... ;D
And no, haven't read about it, am not sure, if it's a real problem after all, as the update servers need some time till the receive the update for distribution, so maybe it's just about a little patience... ;)
asyn
Think about it.  Two computers on a home LAN.  Both running avast 5.0.462.  But with pretty much the same software and hardware, sharing an internet connection.  One computer auto updates to 100409-1, and many hours later, the other has not.  Based on my experiences the other day, one did not update until the next day, i.e. it missed the second update of the day.  Today it only updated because of a reboot.

Yes, patience is a virtue, but I'm not seeing it as a solution to this failure to update condition.  :)
Title: Re: manual update problem when set to auto update
Post by: Asyn on April 09, 2010, 11:37:25 PM
Yes, patience is a virtue, but I'm not seeing it as a solution to this failure to update condition.  :)

I see... ;) Well it could be related to your shared connection on a home network, but let's talk again after you updated to 5.0.499, maybe it helps solving your problem and you won't have to wait any longer... :)
asyn
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 16, 2010, 12:24:25 AM
Updated to v5.0.507 and the issue is not resolved.

Even though avast! updates with each new date, it will not manually update after that when a new definition version is available during the day.

As of right now, current version is 100415-1.
That version has already automatically installed on one of my computers,
but the other one still has 100415-0.
When I attempt to manually update, all I get is:
"Already up to date (current version 100415-0)".

I have tried a repair, and rebooted, to no avail.  Sometimes the reboot triggers a new update, but not this time.

What's left?  Uninstall and reinstall, I suppose.

(This issue did not exist when I first updated from v4.8 to one of the earlier v5.0 builds.)

WinXP, SP3
Title: Re: manual update problem when set to auto update
Post by: Asyn on April 16, 2010, 11:25:12 AM
As avast has many update servers, it will take some time till all can offer the new updates.
So eg., your first machine connects to server xx1 and the second to xx45, it can happen that one gets updated and the other doesn't.
So no repair, reinstall, reboot will help, only waiting will help... ;)
asyn
 
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 16, 2010, 07:35:06 PM
I think you're wrong.

What you're overlooking is that while that computer isn't able to manually update for many, many hours in a row (like 18 hours yesterday), it also isn't auto updating, which avast! is configured to do.

So, one computer auto updates and manually updates just fine, and the other won't auto update or manually update all day long when a new update is available.

Exceptions are, as noted, sometimes a reboot will trigger the update, and a new day always triggers an update.

This is not a server problem, and telling me that "only waiting will help" contributes nothing.
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 16, 2010, 08:21:46 PM
When you say it wasn't able to manually update for 18 hours, what errors were you getting ?

When this happens again after a manual update attempt of failed auto update - Post the last 200 lines from the bottom of the setup.log file, located here C:\Program Files\Alwil Software\Avast5\Setup.

We have asked many times that you include your signature information in your profile, this helps us to help you as it saves us having to constantly ask questions about your system, as in the above location is for XP and I haven't got a clue what OS you have.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 16, 2010, 09:33:51 PM
No error messages.  (I would have noted any error messages.) 
As stated, when I attempt to manually update, I get this:
"Already up to date (current version 100415-0)".
Today the version number is 100416-0.
The other standard update info is also given, such as
Total time
Download time
Download files
Server

WinXP, SP3

Here are the lines of the setup log.
When I tried to post 200 lines, I got this --> "The message exceeds the maximum allowed length (10000 characters)", so I'm just posting the lines from the most recent manual update attempt.

I compared them to the same lines from the setup log on the computer that just successfully manually installed 100416-1 and there are some very noticable differences.


11:47:41 min/gen  Started: 16.04.2010, 11:47:41
11:47:41 min/gen  Running setup_ais-1fb (507)
11:47:41 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 3.0 [Service Pack 3]
11:47:41 nrm/sys  Memory: 41% load. Phys:610768/1047856K free, Page:2221636/2519156K free, Virt:2070652/2097024K free
11:47:41 vrb/sys  Computer WinName: A
11:47:41 min/sys  Windows Net User: SYSTEM
11:47:41 min/gen  Cmdline: /downloadpkgs /noreboot /updatevps /silent /session "29" 
11:47:41 vrb/gen  DldSrc set to inet
11:47:41 vrb/gen  Operation set to INST_OP_UPDATE_GET_PACKAGES
11:47:41 min/gen  Old version: 1fb (507)
11:47:41 vrb/reg  Deleted registry: Software\Alwil Software\Avast\5.0\UpdateReady
11:47:41 nrm/sys  Using temp: C:\WINDOWS\TEMP\_asw_aisI.tm~a01500 (3114M free)
11:47:41 nrm/gen  SGW32AIS::CheckIfInstalled set m_bAlreadyInstalled to 1
11:47:41 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
11:47:41 vrb/sys  Computer DnsName: A
11:47:41 vrb/sys  Computer Ip Addr: 192.168.1.101
11:47:41 nrm/sys  Installed in: C:\Program Files\Alwil Software\Avast5 (3114M free)
11:47:41 nrm/int  SYNCER: Type: no proxy
11:47:41 nrm/int  SYNCER: Auth: no authentication
11:47:41 vrb/pkg  Part prg_ais-1fb is installed
11:47:41 vrb/pkg  Part vps_win32-10041600 is installed
11:47:41 vrb/pkg  Part setup_ais-1fb is installed
11:47:41 vrb/pkg  Part jrog-9e is installed
11:47:41 vrb/gen  LoadState: Edition=1
11:47:41 min/gen  Old version: 1fb (507)
11:47:41 vrb/fil  skipped CPackageEngine_File::SetExistingFilesBitmap
11:47:41 min/gen  GUID: d178ea5e-1005-4bfc-b772-d271b135208b
11:47:46 nrm/gen  Server definition(s) loaded for 'main': 334 (maintenance:0)
11:47:46 nrm/gen  SelectCurrent: selected server 'Limelight AVAST5 Server' from 'main'
11:47:46 nrm/int  SYNCER: Type: no proxy
11:47:46 nrm/int  SYNCER: Auth: no authentication
11:47:46 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
11:47:46 nrm/int  HttpGetWinsock(http://ll002.avast.com/iavs5x/servers.def.vpx)
11:47:47 nrm/int  Used server: http://ll002.avast.com/iavs5x
11:47:47 min/fil  GetFileWithRetry: servers.def.vpx downloaded .
11:47:47 min/fil  servers.def.vpx not changed, 1270647376/0
11:47:52 nrm/gen  Server definition(s) loaded for 'main': 334 (maintenance:0)
11:47:52 nrm/gen  SelectCurrent: selected server 'Limelight AVAST5 Server' from 'main'
11:47:52 nrm/int  SYNCER: Type: no proxy
11:47:52 nrm/int  SYNCER: Auth: no authentication
11:47:52 nrm/int  HttpGetWinsock(http://ll002.avast.com/iavs5x/prod-ais.vpx)
11:47:52 nrm/int  Used server: http://ll002.avast.com/iavs5x
11:47:52 min/fil  GetFileWithRetry: prod-ais.vpx downloaded .
11:47:52 min/fil  prod-ais.vpx not changed, 1271443011/0
11:47:52 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx
11:47:52 vrb/pkg  LoadPartInfo: jrog = jrog-9e returned 00000000
11:47:52 vrb/pkg  LoadPartInfo: program = prg_ais-1fb returned 00000000
11:47:52 vrb/pkg  LoadPartInfo: setup = setup_ais-1fb returned 00000000
11:47:52 vrb/pkg  LoadPartInfo: vps = vps_win32-10041600 returned 00000000
11:47:52 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx ended with 00000000
11:47:52 min/gen  basGetRegistrationInfo return value: 0x00000000
11:47:58 min/int  submit has nothing to send
11:47:58 nrm/pkg  Submit: files 0, bytes 0, time 0 ms
11:47:58 nrm/pkg  Submit success: files 0, bytes 0, time 0 ms
11:47:58 nrm/pkg  Transferred: files 2, bytes 0, time 1297 ms
11:47:58 nrm/pkg  Retries: total 0, files 0, servers 2
11:47:58 vrb/fil  NeedReboot=false
11:47:58 min/gen  Return code: 0x20000001 [Nothing done]
11:47:58 min/gen  Stopped: 16.04.2010, 11:47:58
Title: Re: manual update problem when set to auto update
Post by: DavidR on April 16, 2010, 10:02:03 PM
Unfortunately I don't see anything obvious in there there doesn't seem to have been any attempt to access the download servers and I don't see why.

Quote from: Mine
18:23:53 min/gen  Started: 16.04.2010, 18:23:53
18:23:53 min/gen  Running setup_ais-1fb (507)
18:23:53 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 3.0 [Service Pack 3]
18:23:53 nrm/sys  Memory: 37% load. Phys:1318604/2096356K free, Page:3304232/4040440K free, Virt:2070396/2097024K free
18:23:53 vrb/sys  Computer WinName: DWR
18:23:53 min/sys  Windows Net User: SYSTEM
18:23:53 min/gen  Cmdline: /downloadpkgs /noreboot /updatevps /verysilent /session "0"   /limitcpu 
18:23:53 vrb/gen  DldSrc set to inet
18:23:53 vrb/gen  Operation set to INST_OP_UPDATE_GET_PACKAGES
18:23:53 min/gen  Old version: 1fb (507)
18:23:53 vrb/reg  Deleted registry: Software\Alwil Software\Avast\5.0\UpdateReady
18:23:53 nrm/sys  Using temp: C:\WINDOWS\TEMP\_asw_aisI.tm~a03668 (45139M free)
18:23:53 nrm/gen  SGW32AIS::CheckIfInstalled set m_bAlreadyInstalled to 1
18:23:53 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
18:23:53 vrb/sys  Computer DnsName: DWR
18:23:53 vrb/sys  Computer Ip Addr: 80.0.98.252
18:23:53 nrm/sys  Installed in: C:\Program Files\Alwil Software\Avast5 (45139M free)
18:23:53 nrm/int  SYNCER: Type: no proxy
18:23:53 nrm/int  SYNCER: Auth: no authentication
18:23:53 vrb/pkg  Part prg_ais-1fb is installed
18:23:53 vrb/pkg  Part vps_win32-10041600 is installed
18:23:53 vrb/pkg  Part setup_ais-1fb is installed
18:23:53 vrb/pkg  Part jrog-9e is installed
18:23:53 vrb/gen  LoadState: Edition=1
18:23:53 min/gen  Old version: 1fb (507)
18:23:53 vrb/fil  skipped CPackageEngine_File::SetExistingFilesBitmap
18:23:53 min/gen  GUID: a0263c12-5c1f-4cdd-9801-52951e024ded
18:23:56 nrm/gen  Server definition(s) loaded for 'main': 334 (maintenance:0)
18:23:56 nrm/gen  SelectCurrent: selected server 'Limelight AVAST5 Server' from 'main'
18:23:56 nrm/int  SYNCER: Type: no proxy
18:23:56 nrm/int  SYNCER: Auth: no authentication
18:23:56 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
18:23:56 nrm/int  HttpGetWinsock(http://ll002.avast.com/iavs5x/servers.def.vpx)
18:23:57 nrm/int  Used server: http://ll002.avast.com/iavs5x
18:23:57 min/fil  GetFileWithRetry: servers.def.vpx downloaded .
18:23:57 min/fil  servers.def.vpx not changed, 1270647376/0
18:24:00 nrm/gen  Server definition(s) loaded for 'main': 334 (maintenance:0)
18:24:00 nrm/gen  SelectCurrent: selected server 'Download872 AVAST5 Server' from 'main'
18:24:00 nrm/int  SYNCER: Type: no proxy
18:24:00 nrm/int  SYNCER: Auth: no authentication
18:24:00 nrm/int  HttpGetWinsock(http://download872.avast.com/iavs5x/prod-ais.vpx)
18:24:01 nrm/int  Used server: http://download872.avast.com/iavs5x
18:24:01 min/fil  GetFileWithRetry: prod-ais.vpx downloaded .
18:24:01 min/fil  prod-ais.vpx not changed, 1271434183/0
18:24:01 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx
18:24:01 vrb/pkg  LoadPartInfo: jrog = jrog-9e returned 00000000
18:24:01 vrb/pkg  LoadPartInfo: program = prg_ais-1fb returned 00000000
18:24:01 vrb/pkg  LoadPartInfo: setup = setup_ais-1fb returned 00000000
18:24:01 vrb/pkg  LoadPartInfo: vps = vps_win32-10041601 returned 00000000
18:24:01 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx ended with 00000000
18:24:01 nrm/int  HttpGetWinsock(http://download872.avast.com/iavs5x/part-vps_win32-10041601.vpx)
18:24:02 nrm/int  Used server: http://download872.avast.com/iavs5x
18:24:02 min/fil  GetFileWithRetry: part-vps_win32-10041601.vpx downloaded  and verified
18:24:02 vrb/pkg  Part vps_win32-10041601 was set to be installed
18:24:02 vrb/pkg  DeleteObsoletePackages: Removed part-vps_win32-10041600.vpx
18:24:03 min/gen  basGetRegistrationInfo return value: 0x00000000
18:24:03 vrb/pkg  IsFullOkay: vps_32-18a.vpx - not okay (doesn't exist)
18:24:03 vrb/pkg  IsFullOkay: vps_win32-19f.vpx - not okay (doesn't exist)
18:24:04 nrm/int  HttpGetWinsock(http://download872.avast.com/iavs5x/vps_32-18a-189.vpx)
18:24:17 nrm/int  Used server: http://download872.avast.com/iavs5x
18:24:17 min/fil  GetFileWithRetry: vps_32-18a-189.vpx downloaded  and verified
18:24:17 nrm/pkg  DldPackage: C:\Program Files\Alwil Software\Avast5\Setup\vps_32-18a-189.vpx, returned 0x00000000
18:24:17 min/pkg  PerformPkgDiff: pPkgDiffStorage->m_pbtBufNew allocated 36987707
18:24:18 vrb/pkg  PerformDiff: Ok
18:24:19 vrb/pkg  DeleteObsoletePackages: Removed vps_32-189.vpx
18:24:19 nrm/int  HttpGetWinsock(http://download872.avast.com/iavs5x/vps_win32-19f-19e.vpx)
18:24:21 nrm/int  Used server: http://download872.avast.com/iavs5x
18:24:21 min/fil  GetFileWithRetry: vps_win32-19f-19e.vpx downloaded  and verified
18:24:21 nrm/pkg  DldPackage: C:\Program Files\Alwil Software\Avast5\Setup\vps_win32-19f-19e.vpx, returned 0x00000000
18:24:21 min/pkg  PerformPkgDiff: pPkgDiffStorage->m_pbtBufNew allocated 5230955
18:24:21 vrb/pkg  PerformDiff: Ok
18:24:21 vrb/pkg  DeleteObsoletePackages: Removed vps_win32-19e.vpx
18:24:23 min/int  submit has nothing to send
18:24:23 nrm/pkg  Submit: files 0, bytes 0, time 0 ms
18:24:23 nrm/pkg  Submit success: files 0, bytes 0, time 0 ms
18:24:23 nrm/pkg  Transferred: files 5, bytes 72244, time 18467 ms
18:24:23 nrm/pkg  Retries: total 0, files 0, servers 2
18:24:24 vrb/int  Sending stats 'http://download872.avast.com/cgi-bin/iavs4stats.cgi': 00000000 204
18:24:24 vrb/fil  NeedReboot=false
18:24:24 min/gen  Return code: 0x20000000 [Something done]
18:24:24 min/gen  Stopped: 16.04.2010, 18:24:24

Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on April 16, 2010, 10:24:19 PM
I agree.  When I compared that log segment to another segment in which no update was retrieved, there is no difference.  The noticable difference I alluded to is when comparing the log segment I posted to one from a computer in which an update is retrieved.

And once again, I am unable to get the second update of the day (100416-1) that has been available for probably 5 hours now, either automatically or manually.  It installed manually just fine on my other computer hours ago.  I will probably go the entire day without 100416-1 ever making it onto this computer, until tomorrow's auto update installs 100417-0 automatically.

Thanks for posting yours.  I will view it more carefully to see if I spot any differences.
Title: Re: manual update problem when set to auto update
Post by: Snagglegrain on May 04, 2010, 10:34:31 PM
Just reporting back that, for whatever reason, the update issue has disappeared.
For the last 2+ weeks I have been able to do manual updates when available
and the auto updates are taking placed intraday, as they were not previously.
Can't say I changed a thing, but I'm happy with the results
and I appreciate the attempts to help.
Title: Re: manual update problem when set to auto update
Post by: ytahiti on May 06, 2010, 11:10:22 AM
I have readed all the post about this subject and don't find why since I have updated for Avast 5.5.507 It's impossible to update the VPS (manually, automatically, with install/uninstall, etc...
my VPS is 100414-1!!!!!
If I don't find how to update, I will change for an other AV because it will be very dangerous

The last log is
23:04:10 min/gen  Started: 05.05.2010, 23:04:10
23:04:10 min/gen  Running setup_ais-1fb (507)
23:04:10 nrm/sys  Operating system: WindowsXP ver 5.1, build 2600, sp 3.0 [Service Pack 3]
23:04:10 nrm/sys  Memory: 61% load. Phys:398068/1046576K free, Page:2003052/2517732K free, Virt:2070152/2097024K free
23:04:10 vrb/sys  Computer WinName: TOPYA
23:04:10 min/sys  Windows Net User: AUTORITE NT\SYSTEM
23:04:10 min/gen  Cmdline: /downloadpkgs /noreboot /silent /session "9" 
23:04:10 vrb/gen  DldSrc set to inet
23:04:10 vrb/gen  Operation set to INST_OP_UPDATE_GET_PACKAGES
23:04:10 min/gen  Old version: 1fb (507)
23:04:10 vrb/reg  Deleted registry: Software\Alwil Software\Avast\5.0\UpdateReady
23:04:10 nrm/sys  Using temp: C:\WINDOWS\TEMP\_asw_aisI.tm~a03744 (660M free)
23:04:10 nrm/gen  SGW32AIS::CheckIfInstalled set m_bAlreadyInstalled to 1
23:04:10 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
23:04:10 vrb/sys  Computer DnsName: topya
23:04:10 vrb/sys  Computer Ip Addr: 192.168.0.4
23:04:10 nrm/sys  Installed in: C:\Program Files\Alwil Software\Avast5 (660M free)
23:04:10 nrm/int  SYNCER: Type: use IE settings
23:04:10 nrm/int  SYNCER: Auth: another authentication, use WinInet
23:04:10 vrb/pkg  Part prg_ais-1fb is installed
23:04:10 vrb/pkg  Part vps_win32-10041401 is installed
23:04:10 vrb/pkg  Part setup_ais-1fb is installed
23:04:10 vrb/pkg  Part jrog-9b is installed
23:04:10 vrb/gen  LoadState: Edition=1
23:04:10 min/gen  Old version: 1fb (507)
23:04:10 vrb/fil  SetExistingFilesBitmap: 360->85->85
23:04:10 min/gen  GUID: 6e7f1fce-8a93-44cc-adb4-47e9799d54c1
23:04:11 nrm/gen  Server definition(s) loaded for 'main': 353 (maintenance:0)
23:04:11 nrm/gen  SelectCurrent: selected server 'Download914 AVAST5 Server' from 'main'
23:04:11 nrm/int  SYNCER: Type: use IE settings
23:04:11 nrm/int  SYNCER: Auth: another authentication, use WinInet
23:04:11 nrm/int  SYNCER: Agent=Syncer/5.00 (ais-507;p)
23:04:13 nrm/int  Used server: http://download914.avast.com/iavs5x
23:04:13 min/fil  GetFileWithRetry: servers.def.vpx downloaded .
23:04:13 min/fil  servers.def.vpx not changed, 1272345779/0
23:04:15 nrm/gen  Server definition(s) loaded for 'main': 353 (maintenance:0)
23:04:15 nrm/gen  SelectCurrent: selected server 'Download830 AVAST5 Server' from 'main'
23:04:15 nrm/int  SYNCER: Type: use IE settings
23:04:15 nrm/int  SYNCER: Auth: another authentication, use WinInet
23:04:16 nrm/int  Used server: http://174.120.184.234/iavs5x
23:04:16 min/fil  GetFileWithRetry: prod-ais.vpx downloaded .
23:04:16 min/fil  prod-ais.vpx not changed, 1271265655/0
23:04:16 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx
23:04:16 vrb/pkg  LoadPartInfo: jrog = jrog-9b returned 00000000
23:04:16 vrb/pkg  LoadPartInfo: program = prg_ais-1fb returned 00000000
23:04:16 vrb/pkg  LoadPartInfo: setup = setup_ais-1fb returned 00000000
23:04:16 vrb/pkg  LoadPartInfo: vps = vps_win32-10041401 returned 00000000
23:04:16 min/pkg  LoadProductVpu: C:\Program Files\Alwil Software\Avast5\Setup\prod-ais.vpx ended with 00000000
23:04:16 min/gen  basGetRegistrationInfo return value: 0x00000000
23:04:16 vrb/pkg  FilterOutExistingFiles: 85 & 85 = 0
23:04:17 vrb/pkg  FilterOutExistingFiles: 85 & 85 = 0
23:04:17 vrb/pkg  FilterOutExistingFiles: 85 & 85 = 0
23:04:17 min/gen  m_bOperationDidSomething 85/85/0
23:04:17 vrb/pkg  FilterOutExistingFiles: 85 & 85 = 0
23:04:17 vrb/pkg  FilterOutExistingFiles: 85 & 85 = 0
23:04:20 min/int  submit has nothing to send
23:04:20 nrm/pkg  Submit: files 0, bytes 0, time 0 ms
23:04:20 nrm/pkg  Submit success: files 0, bytes 0, time 0 ms
23:04:20 nrm/pkg  Transferred: files 2, bytes 0, time 3688 ms
23:04:20 nrm/pkg  Retries: total 0, files 0, servers 2
23:04:20 vrb/fil  NeedReboot=false
23:04:20 min/gen  Return code: 0x20000001 [Nothing done]
23:04:20 min/gen  Stopped: 05.05.2010, 23:04:20

Is it possible to help me?
Thanks in advance
Title: Re: manual update problem when set to auto update
Post by: Asyn on May 06, 2010, 12:27:13 PM
Is it possible to help me?
Thanks in advance

Use the latest build: http://forum.avast.com/index.php?topic=59223.0
Problem solved..! :)
asyn