Program update notification in 17.4.2294 (build 17.4.3482.0)

I have avast free Program Update set to Ask, Not Auto update.

When I started it up a short time after it stated I got not a notification but a request to restart to conclude the update (or words to that effect).

I checked the Update settings and ordinarily a program update would show your current program version and the update version. Nothing indicating that there was a program update and the fact that it must have updated otherwise why give the Restart required to conclude the update.

I really do hate cr4p like this:

  1. because I have program updates set to Ask.
  2. there is zero information why an update was installed and now asking me to restart.
  3. following my update setting to Ask, something has screwed up, either 1 or 2 above or it is an incorrect request to restart.

Continuing on, before even considering restarting, I have done a manual program update and guess what it reports I’m already up to date as I pretty much expected.

So looks like another interface/program bug (Invisible Program Update).

Hi Dave, this is related to the latest MU, see: https://forum.avast.com/index.php?msg=1393590

I think that micro updates should also be recorded in some way, be that in a increment to the build number or I wonder a toaster notification that a micro update has been done.

That way people know what is going on. Rather than just a notice to restart to apply the update.

Agreed, and usually there’s an increment to the build number. But not this time.

As far I’m concerned , it was exactly the same for port scan micro-update issue a month ago.
Avast said me to reboot , … , and no increment build number (17.3.3443.0)

At that time I was already beta testing the new version, so I can’t confirm/deny it.

I just got this and I restarted… The update is still asking me to restart. I think this is a bug.

You need to reboot twice.

You need to reboot twice.
[/quote]
As weird as I thought this was it worked… thanks.

You’re welcome.

It didn’t ask for a second reboot on mine, only one.

I got the same message about to reboot and so I did. Same message again. What the … I thought. Went to the forum saw the reebot twice solution and then it was OK.
So thank you very much for the help.

You’re welcome.

Unfortunately, the way avast has this set up, avast EmUpdate.exe runs either every 12 hours or once every cold start or system reboot in the first 12 minutes or so.

  • Essentially, what that means is, the original microupdate is installed or just gotten but
  • Another reboot should be done, as a second microupdate could follow the first or the first is not fully live yet

Two reboots seems to fix most issues with avast in any scenario in any case.

Hi,
yes I think it is .
However - even if I have not encountered the problem whose micro-update was deployed for …on all my 3 pc - avast said me to reboot only on my 2 win xp but nothing on my w7 - even now - 2 days after the fix was aviable.
Thus, the initial remark of DavidR makes sense because I can not have confirmation (?) of the increment of the build version number.

Not worried but surprised about that.

I think it best to reboot even when avast (or any other program just updated or freshly installed) even when not called for.

Mine is also set to Notify when update is available. It only did this on my Dell 8200 XP PRO SP3 computer. I think maybe the coders at Avast finally figured out why the Behavior Shield did not enable or stay enabled (at times) on XP PRO SP3 computers. I did not get this restart needed to complete update on the Toshiba Windows 10 Home 64 Bit Laptop

It seems to be correct as far as I have remarked

I think it best to reboot even when avast (or any other program just updated or freshly installed) even when not called for.
rebooted more or less 10 times my w7 Nevertheless, my concern is not to have to reboot several times to be sure that the update has been done but rather to have a clear indication from avast as for example an increment of version.