"Avast needs to restart your computer"

[bob3160]

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.

[Dinobot2]

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?

[DavidR]

There is one topic with a confirmation of that build number and another where they may have that build. 

Both are having banking mode issues, one after it was fixed in version 22.12.6044 (build 22.12.7758.768) now that he has 769.

If you have Avast Secure Browser, you could check to see if it has an issue.

However, not wanting to take this topic even further off track, just confirming some have that build number.

[Dinobot2]

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.

[chris..]

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

[DavidR]

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.

Wasn't me, as chris.. mentioned.

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.

[Dinobot2]

You're right, it was Chris, my bad.

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.

[DavidR]

You're right, it was Chris, my bad.

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.

[Dinobot2]

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.

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.

[bob3160]

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?

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.

[Dinobot2]

I know it isn't the same.

What i'm saying is I shut down (not restarted) my computer on the 24th, then turned it back on a few hours ago. Before the shut down my build number was .768. After turning it back on, it was .769. No "proper" restart in between.

[bob3160]

I know it isn't the same.

What i'm saying is I shut down (not restarted) my computer on the 24th, then turned it back on a few hours ago. Before the shut down my build number was .768. After turning it back on, it was .769. No "proper" restart in between.

Some updates don't need a restart. If it doesn't need to bypass anything that's in use, a restart isn't needed.

[DavidR]

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.

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.

The whole point of that comment is, if there aren't a lot of people reporting it, is it time to look for issues unique to your system/settings, etc.

As I said in a previous comment:

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.

[Dinobot2]

Well like I said it hasn't happened since Dec. 20, but if it happens to me again, i'll put my program update setting on Manual and see if that fixes it, since it seems like "I'll update Manually" is the setting most used by people on this forum.

[bob3160]

Well like I said it hasn't happened since Dec. 20, but if it happens to me again, i'll put my program update setting on Manual and see if that fixes it, since it seems like "I'll update Manually" is the setting most used by people on this forum.

I personally opted to be notified when there's an update available.