Display of Current Virus Definitions

I am using Avast Internet Security 19.8.2393. Virus Definitions Update is set to “Automatic”.

Currently, when I check the display of the current virus definition detail the resulting display shows 190923. (This display has NOT changed in three days). If I “check for updates” … the resulting display display is 190925… (The current and correct detail)

My Avast Install appears to be updating but NOT displaying the updated information.

Any ideas anyone?.. Thanks

When you have this issue, appears to be out of sync with what you have and what is reported, try an Avast Repair and reboot.

AvastUI > Menu > Settings > General > Troubleshooting - scroll down and use the Repair APP button.

This has worked for me in the past on the occasions where it appears out of sync.

Thanks DavidR…The problem seems to have corrected itself… I will wait and see what happens in the morning when I reboot… and will take your advice as needed.

Thanks again… Cheers…\

I think that this may be the problem that was reported in the beta forum by Asyn https://forum.avast.com/index.php?topic=229373.msg1519176#msg1519176

Information on the VPS displayed using the “About” button doesn’t update between restarts/reboots at least on my GUI version 409 under Windows 10. However, the information is shown correctly by using “Settings” > “Update”

Confirmed, unfortunately it hasn’t been fixed yet.

I just wonder if this is why my win10 system still has 1.0.408 (has Avast pulled 409, pending a fix) despite numerous update checks and reboots.

Unfortunately this issue ap[ears to be the same on UI version 1.0.408, my defs sub-folder and Menu > Settings > General > Update are showing VPS 190925-2 but About Avast showing 190923-2.

Probably not, as it isn’t fixed in UI 413 either.

Well I did a manual program update (for it to report up to date) and dis a system restart and now I have 19.8.2393 (build 19.8.4739.539) and UI 1.0.409.

And both now report the same vps version 190926-2, which matches that in the defs sub-folder.

Strange, it’s still broken here.

Very strange, mine is still reporting the same version in About Avast and the Settings > Update section, backed up by the defs sub-folder.

Is this possibly due to your UI version being 1.0.413 mine is still 1.0.409.

I have to say this issue of any update totally screwing things up Program/UI updates is getting very tiresome. Things that were working just fine are suddenly broken.

I really have to wonder about this monthly update cr4p (breaking stuff) and how it got through Alpha testing and supposed beta testing only to break on release. I think there needs to be a period of consolidation (one month really isn’t long enough) to fix what is reported as broken in the forums before moving to the next update.

No idea, I could only guess. :-
Out of interest, does it work for you if you don’t reboot the system (due to W10 updates)…?

Well ordinarily I always reboot the system after W10 updates, otherwise my win10 system isn’t restarted frequently. I certainly have more restarts as a result of Avast updates or trying to force Avast updates when there are no notifications and I know there should be (seen in forums) for UI updates.

But this recent issue I hadn’t had any win10 updates prior to yesterday and I already had the UI update to 1.0.409.

Let’s put it this way, the bug only shows up if the system isn’t rebooted.

Well for a time I had this bug, despite regular reboots to try and get/force an Avast update.

Just for the record, this still isn’t fixed for me with build 541/UI 416.

I don’t see any problem or, am I missing something?

https://screencast-o-matic.com/screenshots/u/Lh/1570017052719-78477.png

Hi Bob, according to your screenshot, it seems Omni has a totally different UI (1.0.85).

I still have UI 415 showing as latest on Free version, even after forcing any updates.
So maybe difference also between Premium and Free. Are any others still on UI 1.0.415?

Yes, just look at the signature below my posts for my win10 system:
avast! free 19.8.2393 (build 19.8.4739.541) UI-1.0.415

Nope, but there’s a difference between stable/beta update channel.