Please see here: http://forum.avast.com/index.php?board=2;action=display;threadid=9007
I dont know why people are having spate of problems with Avast, I have two different machines running Avast, one a dual Athlon and other a dual P-III 850, both using Win2K SP4, MS Outlook 2002 for email client and I have faced no problems whatsoever, I have updated to this version and as usual will give you feedback if there is any problems which I dont really anticipate.
hehehe same here, i’ve got win XP pro on one machine and 200pro on another
did i miss something ?? mine reads version 531 :o you guys must be gettin the hang of pumping out new versions now. ;D
Just to note: from 4.5.529 to 4.5.531 I was not asked to boot…
Hope it’s just cosmetic changes that does not requires a boot… 8)
That’s really strange…
There were certainly changes in the program itself (such as Vlk’s change in the Simple User Interface “Play” button)… or, a potentially bad bug was fixed in the core (that may cause the program to freeze on some files) - so a reboot should certainly be required.
Can you check the end of setup log, corresponding to the update?
Just to note: from 4.5.529 to 4.5.531 I was not asked to bootStrange indeed, it sure asked me to reboot.
This is the last update (build 529).
At the end, I have the line NeedReboot=false
The next shows that I have build 531.
Am I reading something wrong?
Btw, I suggest a way to limit the setup.log file… It’s too big for me 
It’s really strange - the new packages were downloaded, but not installed (it wasn’t even tried) ???
How did you invoke the update?
Command line:
C:\ARQUIV~1\Avast\ashUpd.exe program /silent /nodetails
Ah, it may be the case then.
I talked to Mr. Forejt about it and he said there should be another argument there (refresh - if I remember correctly(?)); he was wondering why it’s missing.
Invoking program repair should install the downloaded packages.
It’s not the case, Igor.
I did not invoke the repair function after that.
Usually, I just invoke updates by this way… It should update but it does not asked for booting… When I boot, it was refreshed…
Am I doing/thinking anything wrong?
Should I add another parameter to that command line? (usually I have /VPS but there are a lot of betas and I need to be updated with them too 8))
Igor, the same happened if I use the command line from 4.5.531 to 4.5.536. No boot is required. The about window show 4.5.526. I was surprised! I tried to manual update the program and, then, the boot was required :
Same thing happened to me (using Win 98)… req’d a reboot. No biggie though. 
That is what is suposed to happen now, Technical wasn’t being asked to reboot after an command line update. So in effect the update wasn’t applied.
Vampiric_Crow and RejZor
Isn’t this behavior - updating and not asking for a reboot - what you were looking for and posted in the wishlist? 8)
Yeah, only downloaded. Applied just on next boot
I found a good workaround to my conscience: I don’t have to boot immediatly 8)
Ooops, my fault! I really should read Technical’s messages better! ;D
Technical, this is what aswUpd.exe /help shows:
Usage: aswUpd.exe vps [/silent [/nodetails]] [/autoreboot] [/help]
aswUpd.exe program [/silent [/nodetails]] [/autoreboot] [/help]
/silent -- do not display the GUI and modal Summary screen
/nodetails -- do not print the console summary in silent mode
/autoreboot -- reboot the computer after update, if necessary
/help -- display this help screen
So - the behavior you’re seeing is perfectly normal. You didn’t use the /autoreboot switch but used the /nodetails switch which suppressed the reboot prompt…
Thanks Vlk, I was just puzzled because Igor wrote this:
I thought, wrongly as you say, that was missing an argument there: refresh and that something could be improved in the command line…