"Avast needs to restart your computer"

[Dinobot2]

I got a message like this out of no where maybe 20-30 minutes ago asking me to restart my computer, saying "You're still being protected but Avast needs you to restart" or something. I should have taken a screenshot before doing so. There wasn't a new program update, nor was there a repair initiated by me. I had the Avast UI open on the Settings->Update area when I got that message, but I didn't initiate anything so I don't see there being a connection there as it's not the first time i've had it open on that section while idle.

I restarted and there's no other information given by Avast to me. Ran a Smartscan after, ran a manual Windows Defender scan and will likely run an EEK scan just to be safe, but I have a feeling this isn't malware related.

Has anyone experienced this before? I can't remember Avast asking me to restart my computer for no apparent reason.

[DavidR]

There may well have been a fix delivered in the 'Engine' and virus definitions update that could requiring a restart.

I haven't seen it but I'm still running  avast! free 22.10.6038.

[Dinobot2]

Is that something you have personally experienced before, or something you know for certain does happen?

[DavidR]

Is that something you have personally experienced before, or something you know for certain does happen?

I have certainly seen it before, though it isn't a regular occurrence. Mind you I have been using Avast for over 18 years.

[Dinobot2]

That's good to know, and comforting to hear. I would imagine it's not a regular occurrence as I don't have any recent memory of it happening, and I've been using Avast for about 11 years. If it happens regularly, would that be cause for concern?

[Dinobot2]

So I just saw that the Program version slightly changed before and after restarting after comparing screenshots (I knew those would come in handy eventually). The program version is the same (22.12.6044) but the build is slightly different. Pre-restart it was 22.12.7758.765, and post-restart it is now 22.12.7758.766.

I can't say for sure if that was the cause of the restart, but there is that and probably worth noting.

[DavidR]

Probably a bug fix, there have been a couple in the forums, though I don't know which, bank mode issue is a possible that would warrant an out of sequence update/fix.  Repairing may have required a restart, however that is speculation on my part.

[chris..]

.....bank mode issue is a possible that would warrant an out of sequence update/fix.....

Unfortunately, this does not seem to be the reason.
22.12.6044 (version 22.12.7758.766) and the bug is still there 
but maybe for another reason.
It wouldn't be the first time that avast asked to restart after a micro update like yesterday's. 

[Dinobot2]

.....bank mode issue is a possible that would warrant an out of sequence update/fix.....

Unfortunately, this does not seem to be the reason.
22.12.6044 (version 22.12.7758.766) and the bug is still there 
but maybe for another reason.
It wouldn't be the first time that avast asked to restart after a micro update like yesterday's. 

Did yours ask you to restart?

Did anyone else's?

[DavidR]

.....bank mode issue is a possible that would warrant an out of sequence update/fix.....

Unfortunately, this does not seem to be the reason.
22.12.6044 (version 22.12.7758.766) and the bug is still there 
but maybe for another reason.
It wouldn't be the first time that avast asked to restart after a micro update like yesterday's. 

Yes, I have just seen this in another post, living in hope I guess.  Not being a Chromium based browser (or ASB), I haven't had any problem.

That said, on something so crucial 'how the hell did this get past QA, Alpha and Beta testing' is the question I ask ?

[chris..]

That said, on something so crucial 'how the hell did this get past QA, Alpha and Beta testing' is the question I ask ?

You'll have to ask Bob, who seems to be the only one who doesn't have a problem even without ASB as his default browser. 

Did yours ask you to restart?

No but my system was shut down last night(at the time avast asked you to do so?), the micro update (765->766) was certainly done this morning at startup and therefore did not need to ask me to reboot.
This request may have been made by overseer which is a scheduled task (not set to the same time for all)

[Dinobot2]

This request may have been made by overseer which is a scheduled task (not set to the same time for all)

I just checked the history in the task scheduler for Overseer, and the timestamps don't line up with when the restart request popped up.

[Dinobot2]

Ok it just asked me to restart again, and this time I took screenshots.

Why is it doing this? Is there something wrong with my installation? Is it asking anyone else to restart? I'm getting more than a little bit concerned here.

[DavidR]

I think this may have had something to do with it:

Hi,
we just released the fix for the Bank Mode issue and it's being distributed as an independent update.
To install the update, open your Antivirus, go Settings - General - Update, click on “Check for updates” button under the Antivirus version and restart your computer.
Sorry for inconvenience caused!

[Dinobot2]

I don't have the Avast browser installed, so Bank mode isn't something I would need, unless it needs to update Avast completely in order for it to work. Also, I don't have my application update to automatic, I have it on "Remind me when an update is available" which just gives a pop up saying there's a new version available; it doesn't (shouldn't?) ask me to automatically restart.

I did do a restart (had to wait until my lunch hour as i'm working from home and use my computer for work), and noticed that the build did update to .767 (other numbers in the build version unchanged), but it didn't update that it until after the restart, which I guess would make sense but I can't remember if regular application updates do the same.

EDIT: I did a Change on Avast from Control Panel (thinking that would bring me to online repair), didn't add or remove any components and did a restart which changed my build number to ending .768. Did an actual repair, restarted (which didn't change the build number). Just to cover those bases to make sure nothing was broken. Hopefully I don't get a request to restart again. I could uninstall and reinstall but I did that three days ago and have done it several times over the last couple of months, so I don't know if that would have an effect. Also, shit's just too time consuming.