Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Spiritual2016 on September 06, 2019, 08:12:20 PM
-
Virus Def Version: 190906-0
Program Version: 19.7.2388-Build 19.7.4674.526)
Hello.
This morning (Fri @ 10:45am Pacific), I opened Avast Free and it requested a restart. However, after reboot, the program section did not show an update for today.
What was the restart for?
-
https://forum.avast.com/index.php?topic=229239.0
-
Pondus:
I read the linked thread but my question has still not been addressed.
There was no program update (the last program update still shows Aug 15)
1a. Is 19.7.2388 the latest program update?
b. If it is, it is an old program update so why was the reboot required? If it is a new program update, why does it show Aug 15?
-
Hi
Same thing happened for me today. And it has happened two times before in the last two weeks or so. No idea why this happens. This time I did a manuell virus definition update and after that it requested me to restart. But the other two times it jus showed up when I opened the UI.
-
Pondus:
I read the linked thread but my question has still not been addressed.
There was no program update (the last program update still shows Aug 15)
1a. Is 19.7.2388 the latest program update?
b. If it is, it is an old program update so why was the reboot required? If it is a new program update, why does it show Aug 15?
It's the build that changes more often than the actual program version. This is as current as it gets:
(https://screencast-o-matic.com/screenshots/u/Lh/1567801711620-31295.png)
There are also emergency updates that can be passed along which can require a system restart.
-
Today was the third reboot I've done in the past 3 weeks for Avast. I sure hope things settle down.
-
Today was the third reboot I've done in the past 3 weeks for Avast. I sure hope things settle down.
I haven't had to do a single reboot, no obvious notifications, e.g. a pop-up window requesting a reboot outside of the last program update 19.7.xxxx in mid August.
I have however done a couple of reboots for other things, which would probably encompassed this requirement for a restart.
-
Bob:
Yes, the current build shows 19.7.4674.526 so it is the latest version.
When was build 19.7.4674.526 released? If it was released today and is a new release then a reboot would be required; However, why does the release date show Aug 15 at 1:54am instead of today's date and time?
If it was released on Aug 15 then the release date is correct (and it is an old program update) but it does not explain why a reboot was required.
-
Bob:
Yes, the current build shows 19.7.4674.526 so it is the latest version.
When was build 19.7.4674.526 released? If it was released today and is a new release, why does it show the release date as Aug 15 at 1:54am instead of updated to today's date?
If it was released on Aug 15 then the release date is correct (and it is an old program update) but it does not explain why a reboot was required.
As I stated, there could also have been an emergency update or, an update to something in Avast via a VPS update that may have required a restart.
I'm simply offering possibilities that could have required a restart. Like you, I use the product.
Anything else would have to come from an Avast employee.
I've reported this to Avast but, we are also starting the weekend.
-
If it was an Emerg update (which would obviously require a reboot) then why wouldn't the release date be updated?
Is the program update release date only updated if it is a program-specific update? If so, it would explain why the program update release date still shows Aug 15 at 1:54am.
-
If it was an Emerg update (which would obviously require a reboot) then why wouldn't the release date be updated?
Is the program update release date only updated if it is a program-specific update, which would explain why the program update releease date still shows Aug 15 at 1:54am?
You've answered your own question. :) Not all things effect a change in program build version.
-
1a. Has there been an update to whether Friday's reboot was the result of:
*A Program Update
*An Emergency Update
*An Update to something in Avast via a VPS Update
*Another type of update not mentioned
b. If this update changed the version, the build, both, or neither; Also, why the release date did not change to reflect Fri Sept 6 instead of still showing Aug 15 at 1:54am.
c. If the reboot was actually a glitch since there was no update released on Fri Aug 6.
-
1a. Has there been an update to whether Friday's reboot was the result of:
*A Program Update
*An Emergency Update
*An Update to something in Avast via a VPS Update
*Another type of update not mentioned
b. If this update changed the version, the build, both, or neither; Also, why the release date did not change to reflect Fri Aug 6 instead of still showing Aug 15 at 1:54am.
c. If the reboot was actually a glitch since there was no update released on Fri Aug 6.
1.a I don't believe anyone (avast user) can give a definitive answer to this other than what has already been mentioned. An update resulting in a build number increment, based on a change to the UI would appear to be the most likely (mentioned in other topics, the link in Reply #1 above).
1b Because the program hasn't essentially changed only the UI.
1c Not a glitch (if UI update is the reason) the only way a UI change could be implemented would be after a restart.
-
Thanks DavidR.
-
You're welcome.