Ok so, this might be a really stupid question, but is there an equivalent of a “streaming update” for the program updates? Are there micro updates to the program/app itself that gradually get downloaded and installed in between the monthly updates? If so, is that what the last three digits of the build number represent?
To be clear, the 765->766 and 766->767 came after the prompted restarts from the Avast popup. the 767->768 update came after I clicked “Change” from the Programs list in Control Panel and then a restart after that Change.
You either have Program Updates set to Automatic or Manual.
Program bug fixes and some updates can be delivered in the Engine and Virus Definitions update. Also there is the Emergency update, which by its nature would be delivered if one is found on checking. These would obviously be related to how serious/urgent the update is.
The last three digits, just give a definitive build number where the four digits aren’t as exact, just more detailed.
And i’m assuming ‘Manual’ and ‘Automatic’ are umbrella terms where one includes “Remind me when an update is available”?
Would a broken installation be a cause for these ‘emergency’ updates and restarts? Like I mentioned, I’ve uninstalled and re-installed Avast several times over the last couple of months, but the most recent update was two days before that ‘restart’ message (so four days ago overall), so maybe the most recent installation didn’t go swimmingly or something got messed up in the process.
Well it comes under the heading of the Automatic: checking function, the check is automatic and if an update is available they are the options. Where Manual is just that.
No, emergency updates are initiated by Avast, serious issue/bug fix etc. and the program periodically check if there is an emergency update available.
I can’t comment any further than what I have previously, I have no idea why you are getting these restart notices.
I haven’t gotten any restart notices since my second one two days ago. I’ve also put my laptop in sleep mode the last two nights, and then my computer sat idle for about 11 hours after waking it back up, so we’ll see if laptop use has an impact.
I don’t think it’s a coincidence, for me the reboots are related to the 765->766->768 updates
Even if it doesn’t explain why these requests appeared to you :-\
to be checked for the next change of the last 3 digits of the version number
Update for anyone still curious: No requests for restart since that second one on Dec. 20th (so three days ago). Barring one happening, I guess it did have to do with the version updates to fix everyone’s bank mode. Still don’t know why it requested to restart for me, nor do I know why it did it for me even though I don’t use bank mode nor use the Avast Secure Browser, but at least this isn’t a recurring thing over and over.
As I understand it, ASB Bank Mode is tied closely to Avast AV. So it does not matter if you have (or don’t have) ASB, the update to Avast AV would be pushed out regardless.
In my experience such emergency updates to Avast AV resulting in a need to “restart” your PC, are infrequent. Maybe that is why this one received so much attention here.
Putting Avast aside for a moment, it is good practice to restart your system on a regular basis.
Turning the system on and off ,unless you’ve made changes to your system, does nothing
except save a few pennies of electricity.
Restarting your system cleans out certain trash and updates items that require a restart
in order to complete the update process.
Since this was discussed in this thread somewhat, I turned my computer back on after having it off for a couple of days while I was away visiting family, and when I looked at the build number, it now ends in .769.
Does anyone else have build .769? Is this something that changes after certain restarts/boot ups? Or is it based on the number of days elapsed?
I guess I just don’t know how Avast’s build numbers work and when, how often, and/or why they change. It’s also not something I was paying attention to before the last week or so, so I don’t really even have a frame of reference for whether this is “normal.” I also remember you (DavidR) saying that yours went from 765 to 766 to 768 in between computer shutdowns and boot-ups.
it was not David who said that but me #19
I have also 769 for now but I don’t know when it arrived, probably while my pc was switched off, what is certain is that I have still not been asked to reboot
However, the build numbers are more detailed than the simple program version number.
Every change to a program is incorporated into a build version number, e.g minor changes or fixes to the program. The build number is more useful to Avast as every change to to the program is assigned to a build number. There could be multiple changes within a build number, but Avast knows what those changes are.
For the most part users are mainly interested in the program version, outside of issues like this when related to the Bank Mode issue, where the fix would have had an assigned build number. More relevant when a new update/build number breaks something Bank Mode, hopefully Avast can pin down the problem in that build number to break it again.
Note I haven’t got 769 as I don’t often restart this laptop, so still on 768 as in my signature.
So restarting/booting on and off must be the trigger for the build number changes. So, perhaps if my computer wasn’t off for the last couple of days I would have gotten bugged to restart.
I guess i’ll just have to monitor closely and test it out with random restarts and shutdowns over the next little bit before Version 23.01 comes at us.
Not necessarily so, remember the Engines and Virus Definitions and the Emergency Updates mentioned before, they may or may not require a restart. It depends on what is being changed.
In all honesty you will give yourself an ulcer with this level of concern. As I have mentioned before, I’m not seeing a rash of people reporting requests to restart by Avast in the forums.
I have no idea what changes to the default settings you have made. I just wonder if you would be better restoring the default settings and see how that goes.
If we were getting a rash of people reporting requests to restart, I would be far less concerned.
But resetting the defaults wouldn’t really do much since I would just reload my settings from the back-up file for my scheduled scans and other preferences.
Turning your computer of and then back on regardless of how long that off mode is, is not the same as doing a restart of the system. AS restart allows clearing of certain items and, installing of those things that required a reboot of the system.
