« Reply #56 on: August 10, 2024, 10:50:46 PM »
That is a build number update you are referring to, the program version hasn't changed. These could be bug fixes delivered either by virus definition update or emergency update function.
You don't say if you have program updates set to automatic or manual ?
- mine is set to manual and I haven't got build 24.7.6124 (24.7.9311.859), it is still on 24.7.6124 (24.7.9311.856) as in my signature.
I always have manual updates set for the program. This would have to be pushed through that second silent update mechanism that Avast has and doesn't brag about. The date (Jul 29) is also not too close, which suggests even more that it was a silent update without changing the date...
I also have program updates set to manual and I haven't got the build number that you are reporting. My update is reported as Jul 29, and that it is up to date for the version. I suspect that the difference on the build number may depend on what Avast components you have installed if there was an update for that component.
There were a number of notifications at the start of this topic, I just wonder of depending what that could have an impact on the build number.
Major public announcement:
Avast AV supports Windows 11 ARM.
Web shield improvements - Support for TLS Early data (read-only mode).
RealSite - new settings allowing to set up real site with respect to trusted and untrusted networks.
Onboarding UI overhaul - we reviewed the onboarding path for the free and premium users.
Improved Easy Anti-Cheat compatibility
More bug fixes
« Last Edit: August 10, 2024, 10:53:14 PM by DavidR »
Logged
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD - 27" external monitor 1440p 2560x1440 resolution - avast! free 24.9.6130 (build 24.9.9452.762) UI 1.0.818/ Firefox, uBlock Origin Lite, uMatrix/ MailWasher Pro/ Avast! Mobile Security