NEW Version: 19.7 (July/August 2019)

[DavidR]

How do I clear my history? It is a commonly used computer, and I would like to protect my private zone.

ATM, you can't. But it has been reported, let's hope this option gets (re)added later on.

Thanks Mate!

You're welcome.

Info, it's back in UI 408 (released today).

Still on UI 1.0.406, how was this released or is this in the beta build ?

[schmidthouse]

How do I clear my history? It is a commonly used computer, and I would like to protect my private zone.

ATM, you can't. But it has been reported, let's hope this option gets (re)added later on.

Thanks Mate!

You're welcome.

Info, it's back in UI 408 (released today).

Still on UI 1.0.406, how was this released or is this in the beta build ?

Interesting you should mention that David as my latest Stable version has UI 408 but my latest beta installation has UI 407

Edit: the beta installation after reboot now shows v.409

[bob3160]

This is what I have?

[DavidR]

<snip quotes>
Info, it's back in UI 408 (released today).

Still on UI 1.0.406, how was this released or is this in the beta build ?

Interesting you should mention that David as my latest Stable version has UI 408 but my latest beta installation has UI 407

Edit: the beta installation after reboot now shows v.409

Well I know that in order for UI updates to be applied requires a restart.  However, there was no popup or notification of a restart being required.

I decided to do the same as you on the regular program stream and restarted my system and the UI version is now on 1.0.408.

Se we are still in limbo/confusion about when and how a UI update is applied and why we aren't notified about it.  It isn't that long ago when everyone was asking what this notification about a restart was about !!!

Looks like Avast felt they shouldn't frighten the horses when a restart is required outside of program updates.  There certainly needs to be some clarity here !
EDIT: since the UI update also changes the build number.

[schmidthouse]

<snip quotes>
Info, it's back in UI 408 (released today).

Still on UI 1.0.406, how was this released or is this in the beta build ?

Interesting you should mention that David as my latest Stable version has UI 408 but my latest beta installation has UI 407

Edit: the beta installation after reboot now shows v.409

Well I know that in order for UI updates to be applied requires a restart.  However, there was no popup or notification of a restart being required.

I decided to do the same as you on the regular program stream and restarted my system and the UI version is now on 1.0.408.

Se we are still in limbo/confusion about when and how a UI update is applied and why we aren't notified about it.  It isn't that long ago when everyone was asking what this notification about a restart was about !!!

Looks like Avast felt they shouldn't frighten the horses when a restart is required outside of program updates.  There certainly needs to be some clarity here !
EDIT: since the UI update also changes the build number.

Agreed, clarification is always helpful

[bob3160]

Even a restart didn't change things for me.

[DavidR]

<snip image>
Even a restart didn't change things for me.

Well your program version, build number changed (build: 19.7.4674.526) as mine did from (build: 19.7.4674.524).

I just wonder if your UI version reflects that you also have Avast Omni as 1.0.85 isn't even close to that of the regular Avast program UI.  After a restart for Avast Free (no Omni) the UI version was 1.0.408 or even that before a restart (UI 1.0.406).

[Luana32]

My license won't work now with the update. I bought my license from a reseller.

[bob3160]

My license won't work now with the update. I bought my license from a reseller.

Not a good sign. I suggest you contact that reseller. Good luck.

[Asyn]

Se we are still in limbo/confusion about when and how a UI update is applied and why we aren't notified about it.  It isn't that long ago when everyone was asking what this notification about a restart was about !!!

Looks like Avast felt they shouldn't frighten the horses when a restart is required outside of program updates.  There certainly needs to be some clarity here !

Hi Dave, that was a bug and has been fixed last week.

[DavidR]

Se we are still in limbo/confusion about when and how a UI update is applied and why we aren't notified about it.  It isn't that long ago when everyone was asking what this notification about a restart was about !!!

Looks like Avast felt they shouldn't frighten the horses when a restart is required outside of program updates.  There certainly needs to be some clarity here !

Hi Dave, that was a bug and has been fixed last week.

Well if that bug was fixed last week and I'm reporting related issues (zero notification of a restart required and nothing in the Notifications area) 2 days ago, it doesn't appear fixed to me.

To me there is still confusion, clarity is required when updates that require a restart that would also change the build number, users need to know.

[Asyn]

There usually isn't any notification about UI update, so it's basically back to normal.

[DavidR]

There usually isn't any notification about UI update, so it's basically back to normal.

Well you have seen the confusion in the forums this caused when a restart is required.

[Asyn]

There usually isn't any notification about UI update, so it's basically back to normal.

Well you have seen the confusion in the forums this caused when a restart is required.

Sure, and (as said) the bug has been fixed.

[DavidR]

There usually isn't any notification about UI update, so it's basically back to normal.

Well you have seen the confusion in the forums this caused when a restart is required.

Sure, and (as said) the bug has been fixed.

I don't get what has been fixed, if it relates to getting notifications as I have mentioned then it isn't fixed. 

Or that Avast are not giving notifications when a restart is required to apply an update (UI or otherwise).  If that is what they have chosen to do, then I feel this is wrong, that isn't a graceful fix but a hide it under the carpet tactic.