Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: chris... on March 05, 2024, 02:29:24 PM
-
Hi,
This morning avast told me that I was no longer protected (red cross) with my W7.
The notification said that I should update the program to the new version as a matter of urgency, which I did.
But it's surprising when you consider that I usually don't get any notification for a while after a new version.
I should point out that I was up to date (v24.1 and yesterday's VPS).
my 2 other devices haven't had this alert yet, and apparently no-one has mentioned version 24.2 here.
-
Exactly the same here Chris on win 10 pro
usually i start on my own pc so would of noticed this straight away but sods law i had some urgent nhs work to do on my work pc.
2 hours later i switch over to my own pc which looked like it had been unprotected for 2 hours due the the red x (maybe antivirus was still running in background) but usually a red x means unprotected.
I guess this was another rolling update as its release day was 1/3 but here in uk i received it on 5/3
so your not alone fella.
-
I got the same thing. First time I have ever seen this.
-
yeah same here, can confirm the weird behavior.
Never got an alert like that for a new program version
-
Installed the update and restarted. Looks like just the standard update to the next version with just "Regular bug fixes" as what's new with this new version.
So what I'm curious about now is whether this way of notifying about an update is going to be the norm for any updates going forward, or if there was something so important about this specific update that Avast had to alert users once it was available to them? I have my Update settings set to "Remind me when an update is available." Is this the new "reminder" for that?
This is also the third or forth update in a row where the update was pushed to me on a Tuesday before an Avast rep making a new post about it here, and the previous posts were made on Wednesday.
Hopefully some clarification can be added.
-
Same here, now have 24.2.6104 (build 24.2.8904.819), UI version 1.0.797. (Win10).
Why was version 24.1 indicated as "no longer protected". I went along with the update assuming it was an emergency update, not a version update. Version 24.2 is not even listed as released here on the forum yet.
This has me thinking that Avast have made a blunder releasing 24.2 unannounced. I will have to re-check my Update settings.
EDIT: I still have program updates set as "Manual". I do not expect any indication to do an update.
I normally update a few days after a new version announcement here on the forum, not Before a new version announcement here.
-
Installed the update and restarted. Looks like just the standard update to the next version with just "Regular bug fixes" as what's new with this new version.
So what I'm curious about now is whether this way of notifying about an update is going to be the norm for any updates going forward, or if there was something so important about this specific update that Avast had to alert users once it was available to them? I have my Update settings set to "Remind me when an update is available." Is this the new "reminder" for that?
This is also the third or forth update in a row where the update was pushed to me on a Tuesday before an Avast rep making a new post about it here, and the previous posts were made on Wednesday.
Hopefully some clarification can be added.
Ive got mine set to auto update but for years it never does.
usually i go to check updates randomly now and again and one is sitting there in red waiting.
this one is totally different and never seen the red x before.
-
I too got it, even though my program updates are set to Manual.
Generally I wait for program update topic in the forums and decide if (update then or later) but still no official notification on the forums for 24.2.
The fact that you haven't got the latest program version 'Shouldn't generate the fear mongering notice', the program should still be running and working!
Given what was in the beta subforum for 24.2 there was bugger all in that which should generate this heavy handed notice (which I have never had before) warning you are 'unprotected' with a red X over the tray icon.
See my response in the so called current beta topic - https://forum.avast.com/index.php?topic=326205.msg1715553#msg1715553
-
I got the important update too but I'm not going to. No red X though.
-
It's been another month since the team hasn't posted anything here on the forum stating that there is a new version, and this error is already recurring.
Another problem, what strange message is this? and stop users from being afraid? We all need avast team answer?
What are happening to you?
-
It's been another month since the team hasn't posted anything here on the forum stating that there is a new version, and this error is already recurring.
Another problem, what strange message is this? and stop users from being afraid? We all need avast team answer?
What are happening to you?
Another post that makes no sense. 24.2 was just released.
Go back to the ESET forum and use your wisdom there.
-
It's been another month since the team hasn't posted anything here on the forum stating that there is a new version, and this error is already recurring.
Another problem, what strange message is this? and stop users from being afraid? We all need avast team answer?
What are happening to you?
Another post that makes no sense. 24.2 was just released.
Go back to the ESET forum and use your wisdom there.
It doesn't make sense to you, but to me and others here it makes a lot of sense, avast fan.
-
24.2 was just released.
Yes, and they're saying no post with the summary of what was changed from Avast accompanied the release. They have been a day late with it in recent months.
-
24.2 was just released.
Yes, and they're saying no post with the summary of what was changed from Avast accompanied the release. They have been a day late with it in recent months.
Strange that so far it hasn't been revealed what was changed in the new release. I think this time it will take more than 2 days
-
24.2 was just released.
Maybe it only happens to me, but right now on the main page of this forum I only see, in the usual top position, the announcement "NEW Avast version 24.1", dated February 07.
Version 24.2, therefore, appears not to have been officially announced yet.
Maybe it was released but not announced in the usual way.
This is not a big issue, of course; nevertheless it is something unusual.
-
24.2 was just released.
Maybe it only happens to me, but right now on the main page of this forum I only see, in the usual top position, the announcement "NEW Avast version 24.1", dated February 07.
Version 24.2, therefore, appears not to have been officially announced yet.
Maybe it was released but not announced in the usual way.
This is not a big issue, of course; nevertheless it is something unusual.
What's worse is that this lack of information has been happening here on the forum regarding posting the topic at the exact moment it is released, the topic should be updated, but some previous releases have not been happening. I don't know what's going on with the AVAST team. which is not informing customers.
-
Hi,
This morning avast told me that I was no longer protected (red cross) with my W7.
The notification said that I should update the program to the new version as a matter of urgency, which I did.
But it's surprising when you consider that I usually don't get any notification for a while after a new version.
I should point out that I was up to date (v24.1 and yesterday's VPS).
my 2 other devices haven't had this alert yet, and apparently no-one has mentioned version 24.2 here.
Just to be 100% Accurate this is a BETA Version so the announcement is there but in the BETA Section.
-
Hi,
This morning avast told me that I was no longer protected (red cross) with my W7.
The notification said that I should update the program to the new version as a matter of urgency, which I did.
But it's surprising when you consider that I usually don't get any notification for a while after a new version.
I should point out that I was up to date (v24.1 and yesterday's VPS).
my 2 other devices haven't had this alert yet, and apparently no-one has mentioned version 24.2 here.
Just to be 100% Accurate this is a BETA Version so the announcement is there but in the BETA Section.
We've been talking about it for 2 days now, and it's not a beta version but the official version.
I've never had a beta version installed!!!
If it's a beta version that's been installed on an official version, I'd find that not very serious on the part of avast.
-
(https://d1ka0itfguscri.cloudfront.net/Lh/2024/03/07/14/37/cZei2AVKMyh/preview.jpg)
(https://d1ka0itfguscri.cloudfront.net/Lh/2024/03/07/14/38/cZei2BVKMyx/preview.jpg)
-
You didn't understand that we don't use the BETA version here. so much so that this topic we are talking about is not a BETAS session, we are all here using the final version. as this is a final version topic.
-
Hi,
This morning avast told me that I was no longer protected (red cross) with my W7.
The notification said that I should update the program to the new version as a matter of urgency, which I did.
But it's surprising when you consider that I usually don't get any notification for a while after a new version.
I should point out that I was up to date (v24.1 and yesterday's VPS).
my 2 other devices haven't had this alert yet, and apparently no-one has mentioned version 24.2 here.
Just to be 100% Accurate this is a BETA Version so the announcement is there but in the BETA Section.
We've been talking about it for 2 days now, and it's not a beta version but the official version.
I've never had a beta version installed!!!
If it's a beta version that's been installed on an official version, I'd find that not very serious on the part of avast.
Couldn't agree more with the bold text (my edit) in the quote above.
@ bob3160, according to your image you 'have' the beta We/I haven't other than the essentially forced update to 24.2.6104 (build 24.2.8904.819) no Beta flag in my UI.
I don't partake in the Beta trials any longer (several years and a clean reinstall since then), but I do monitor what is going on in the beta sub-forum.
Personally I haven't experienced any of the network problems mentioned. I don't have network shares other than my mobiles and tablets using wifi to connect to the internet.
-
I'd add that this isn't the first time that the version/build number of an official version has been strictly the same as that of a beta version ;)... but if it makes Bob happy to say that we're all using a beta version... then that's fine with me. :D
an example?
Bêta 24.1.6099 (build 24.1.8821)
https://forum.avast.com/index.php?topic=326060.0
official 24.1.6099 (build 24.1.8821)
https://forum.avast.com/index.php?topic=326107.msg1714430#msg1714430
-
I'd add that this isn't the first time that the version/build number of an official version has been strictly the same as that of a beta version ;) ... but if it makes Bob happy to say that we're all using a beta version... then that's fine with me. :D
@Chris,
I simply posted the images from my version which is the same as yours. Mine is definitely a Beta version.
Maybe that's something else that needs to be addressed so that a Beta version is never the same as a released version.
-
I'd add that this isn't the first time that the version/build number of an official version has been strictly the same as that of a beta version ;)... but if it makes Bob happy to say that we're all using a beta version... then that's fine with me. :D
Yes, when the release of a new program update hasn't been posted in the forums. My way of thinking the regular release version should never be the same as the last beta version, I feel it bad practice and avoids confusion.
-
I'd add that this isn't the first time that the version/build number of an official version has been strictly the same as that of a beta version ;) ... but if it makes Bob happy to say that we're all using a beta version... then that's fine with me. :D
@Chris,
I simply posted the images from my version which is the same as yours. Mine is definitely a Beta version.
Maybe that's something else that needs to be addressed so that a Beta version is never the same as a released version.
You can see my attached image that shows no Beta flag - as for the beta to regular release I have said this in the past, it shouldn't be the same, it avoids confusion.
-
I'd add that this isn't the first time that the version/build number of an official version has been strictly the same as that of a beta version ;) ... but if it makes Bob happy to say that we're all using a beta version... then that's fine with me. :D
@Chris,
I simply posted the images from my version which is the same as yours. Mine is definitely a Beta version.
Maybe that's something else that needs to be addressed so that a Beta version is never the same as a released version.
so your post with just images and no explanation is just confusing and does nothing to solve the problem
an official update is often (always) the release of the latest beta version that has passed the (1st) tests.
-
From what I understand all of us who are not part of the avast beta tester. we are being guinea pigs without knowing it. This is really not good practice.
Since we bought a product that is not beta. We pay a lot to have the best quality and not be Avast's guinea pig. >:(
-
@Bob3160 I also want to clarify that I also do not subscribe to the Avast BETA programme.
But I now have Version 24.2.6104 (build 24.2.8904.819), UI version 1.0.797, which I installed assuming it was an emergency update, as Avast tray icon had red X and saying "unprotected".
I for one would welcome an explanation from Avast devs as to why this has update has happened to regular Avast Antivirus users, if indeed it is an escaped BETA version masquerading as a PRODUCTION version. If anyone has an inside track to the devs, can they please seek a response.
-
From what I understand all of us who are not part of the avast beta tester. we are being guinea pigs without knowing it. This is really not good practice.
Since we bought a product that is not beta. We pay a lot to have the best quality and not be Avast's guinea pig. >:(
Please stop your endless speculations and assumptions.
It would be nice if you actually had something of value to contribute to any of these discussions.
-
From what I understand all of us who are not part of the avast beta tester. we are being guinea pigs without knowing it. This is really not good practice.
Since we bought a product that is not beta. We pay a lot to have the best quality and not be Avast's guinea pig. >:(
Please stop your endless speculations and assumptions.
It would be nice if you actually had something of value to contribute to any of these discussions.
And you should learn to read what the topic is talking about so you don't get lost in the conversation.
-
From what I understand all of us who are not part of the avast beta tester. we are being guinea pigs without knowing it. This is really not good practice.
Since we bought a product that is not beta. We pay a lot to have the best quality and not be Avast's guinea pig. >:(
Please stop your endless speculations and assumptions.
It would be nice if you actually had something of value to contribute to any of these discussions.
And you should learn to read what the topic is talking about so you don't get lost in the conversation.
I would be careful what you ask/wish for as it wouldn't be the first time you have dived in at a tangent.
-
I don't have a red x so should I update?
-
I don't have a red x so should I update?
There was also no red "X" on my machine, I updated it and everything is working normally.
-
I don't have a red x so should I update?
There was also no red "X" on my machine, I updated it and everything is working normally.
Amazing, you updated had zero problems but are in here complaining.
-
I got the same thing. First time I have ever seen this.
Hugs friend, today I installed the latest version of Avast. to test if everything is ok.
So far everything is ok. did not give the "X" message.
Have you updated your version and are you still having problems?
-
Yes, and I discussed my experiences in the thread.
Installed the update and restarted. Looks like just the standard update to the next version with just "Regular bug fixes" as what's new with this new version.
So what I'm curious about now is whether this way of notifying about an update is going to be the norm for any updates going forward, or if there was something so important about this specific update that Avast had to alert users once it was available to them? I have my Update settings set to "Remind me when an update is available." Is this the new "reminder" for that?
This is also the third or forth update in a row where the update was pushed to me on a Tuesday before an Avast rep making a new post about it here, and the previous posts were made on Wednesday.
Hopefully some clarification can be added.
-
I noticed that in the latest version of Avast Free, the February version, the icon that marks a malware in quarantine is no longer in the shape of a "ghost".
I like this because it makes it more professional. :)
Surely from these small things you can see a change in Avast for the better and towards a more professional and safer protection software than in the past. :)
-
When are we going to see a formal (Avast) announcement of V24.2 and links to online/offline installers for that version?
Latest version announced on the forum here is still V24.1. https://forum.avast.com/index.php?topic=326107.0
Avast devs have remained silent for too long on this matter. It is about time they broke cover and gave an explaination about the way V24.2 was released, but now it is out in the wild, it should be announced properly. >:(
The only thing I have seen so far is this: https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762
-
When are we going to see a formal (Avast) announcement of V24.2 and links to online/offline installers for that version?
Latest version announced on the forum here is still V24.1. https://forum.avast.com/index.php?topic=326107.0 (https://forum.avast.com/index.php?topic=326107.0)
Avast devs have remained silent for too long on this matter. It is about time they broke cover and gave an explaination about the way V24.2 was released, but now it is out in the wild, it should be announced properly. >:(
The only thing I have seen so far is this: https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762 (https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762)
That's a fair question considering that the latest new version announcement still states version 24.1. :(
-
When are we going to see a formal (Avast) announcement of V24.2 and links to online/offline installers for that version?
Latest version announced on the forum here is still V24.1. https://forum.avast.com/index.php?topic=326107.0
Avast devs have remained silent for too long on this matter. It is about time they broke cover and gave an explaination about the way V24.2 was released, but now it is out in the wild, it should be announced properly. >:(
The only thing I have seen so far is this: https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762
FWIW, I had also been waiting for an updated "formal announcement" of V24.2 and held back on performing an online update via the app while the adventures of the automated update were "sorrted" so to speak. As the forum quieted down over V24.2 issues, I thought to try the download links in the V24.1 announcement and noticed that the size of the downloaded "offline, free" installer was different than that of the V24.1 installer I had saved in February when V24.1 was released. Also, the Files Properties [Details] showed the version of the installer to be V24.2.8904. I thought is was worth a try that this file would install V24.2. I ran my normal Customized install with the downloaded file and it produced V24.2.6104. I has not exhibited any of the unusual behavior noted so far in the forum, although my custom install does not include all the possible features. Not sure how long the link has been active for V24.2, but apparently its a generic pointer to the "latest" release, rather than a specific version release indicated by the version number in the Release Announcement. Yeah, a new V24.2 announcement would have been preferred.
-
When are we going to see a formal (Avast) announcement of V24.2 and links to online/offline installers for that version?
Latest version announced on the forum here is still V24.1. https://forum.avast.com/index.php?topic=326107.0 (https://forum.avast.com/index.php?topic=326107.0)
Avast devs have remained silent for too long on this matter. It is about time they broke cover and gave an explaination about the way V24.2 was released, but now it is out in the wild, it should be announced properly. >:(
The only thing I have seen so far is this: https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762 (https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762)
FWIW, I had also been waiting for an updated "formal announcement" of V24.2 and held back on performing an online update via the app while the adventures of the automated update were "sorrted" so to speak. As the forum quieted down over V24.2 issues, I thought to try the download links in the V24.1 announcement and noticed that the size of the downloaded "offline, free" installer was different than that of the V24.1 installer I had saved in February when V24.1 was released. Also, the Files Properties [Details] showed the version of the installer to be V24.2.8904. I thought is was worth a try that this file would install V24.2. I ran my normal Customized install with the downloaded file and it produced V24.2.6104. I has not exhibited any of the unusual behavior noted so far in the forum, although my custom install does not include all the possible features. Not sure how long the link has been active for V24.2, but apparently its a generic pointer to the "latest" release, rather than a specific version release indicated by the version number in the Release Announcement. Yeah, a new V24.2 announcement would have been preferred.
Please note that the download link posted will always install the latest released version of the App even if it hasn't been formally announced. It is a generic link not depended on the version posted in the forum.
-
When are we going to see a formal (Avast) announcement of V24.2 and links to online/offline installers for that version?
Latest version announced on the forum here is still V24.1. https://forum.avast.com/index.php?topic=326107.0
Avast devs have remained silent for too long on this matter. It is about time they broke cover and gave an explaination about the way V24.2 was released, but now it is out in the wild, it should be announced properly. >:(
The only thing I have seen so far is this: https://forum.avast.com/index.php?topic=326205.msg1715762#msg1715762
FWIW, I had also been waiting for an updated "formal announcement" of V24.2 and held back on performing an online update via the app while the adventures of the automated update were "sorrted" so to speak. As the forum quieted down over V24.2 issues, I thought to try the download links in the V24.1 announcement and noticed that the size of the downloaded "offline, free" installer was different than that of the V24.1 installer I had saved in February when V24.1 was released. Also, the Files Properties [Details] showed the version of the installer to be V24.2.8904. I thought is was worth a try that this file would install V24.2. I ran my normal Customized install with the downloaded file and it produced V24.2.6104. I has not exhibited any of the unusual behavior noted so far in the forum, although my custom install does not include all the possible features. Not sure how long the link has been active for V24.2, but apparently its a generic pointer to the "latest" release, rather than a specific version release indicated by the version number in the Release Announcement. Yeah, a new V24.2 announcement would have been preferred.
Even if you downloaded or saved the 24.1 off-line installation file from that link it isn't version specific, it downloads the latest version.
Even if you used the installation file that saved on your system for Avast 24.1 version - Unless you disconnect from the internet before you ran that, I believe that would also check for and include updates during installation.
-
Has anyone else seen this weird situation.
I posted days ago that I was "pursuaded" to update Avast to V24.2 due to "you are unprotected" status indication.
Today, whilst checking that virus definitions are updating OK, I found that a new Version is available to download.
What version is that, may I ask?
See screenshots.
-
Same strange thing
this is the same version number as the one already installed.
Is there any sand in the avast machine? :(
my apologies it's not the same version .819 -> .825
-
@Bob3160 I also want to clarify that I also do not subscribe to the Avast BETA programme.
But I now have Version 24.2.6104 (build 24.2.8904.819), UI version 1.0.797, which I installed assuming it was an emergency update, as Avast tray icon had red X and saying "unprotected".
@chris. Well thats a thing. Back at 07/03/24 when I posted the above quote, I had 819.
I have setting for Manual version updates and I have not done a manual update since 07/03/24. So how do I now have 825?
Was it a sneaky streamed update pushed out by maybe. The silence from Avast devs is deafening!
I wonder what version/build is awaiting a manual update on my machine now.
-
@Bob3160 I also want to clarify that I also do not subscribe to the Avast BETA programme.
But I now have Version 24.2.6104 (build 24.2.8904.819), UI version 1.0.797, which I installed assuming it was an emergency update, as Avast tray icon had red X and saying "unprotected".
@chris. Well thats a thing. Back at 07/03/24 when I posted the above quote, I had 819.
I have setting for Manual version updates and I have not done a manual update since 07/03/24. So how do I now have 825?
Was it a sneaky streamed update pushed out by maybe. The silence from Avast devs is deafening!
I wonder what version/build is awaiting a manual update on my machine now.
Given some of what was mentioned here, I guess there was a bug fix or - see the Avast UI right click menu 'Engine and Virus Definitions' engine update could also deliver a fix/update that would likely change the build number. As you mention the scheduled Emergency Update in the quoted text could result in a build number update.
-
@Bob3160 I also want to clarify that I also do not subscribe to the Avast BETA programme.
But I now have Version 24.2.6104 (build 24.2.8904.819), UI version 1.0.797, which I installed assuming it was an emergency update, as Avast tray icon had red X and saying "unprotected".
@chris. Well thats a thing. Back at 07/03/24 when I posted the above quote, I had 819.
I have setting for Manual version updates and I have not done a manual update since 07/03/24. So how do I now have 825?
Was it a sneaky streamed update pushed out by maybe. The silence from Avast devs is deafening!
I wonder what version/build is awaiting a manual update on my machine now.
Given some of what was mentioned here, I guess there was a bug fix or - see the Avast UI right click menu 'Engine and Virus Definitions' engine update could also deliver a fix/update that would likely change the build number. As you mention the scheduled Emergency Update in the quoted text could result in a build number update.
What's not clear is why an update to 24.2.6104 (version 24.2.8904.825) is proposed when the installed version (via the "about" menu) is already this version.
-
just had a look and same here version 24.2.8904.825 . set to auto update but sitting waiting to be manually installed.
installing now. at least we didnt have the red x this time.
-
@Bob3160 I also want to clarify that I also do not subscribe to the Avast BETA programme.
But I now have Version 24.2.6104 (build 24.2.8904.819), UI version 1.0.797, which I installed assuming it was an emergency update, as Avast tray icon had red X and saying "unprotected".
@chris. Well thats a thing. Back at 07/03/24 when I posted the above quote, I had 819.
I have setting for Manual version updates and I have not done a manual update since 07/03/24. So how do I now have 825?
Was it a sneaky streamed update pushed out by maybe. The silence from Avast devs is deafening!
I wonder what version/build is awaiting a manual update on my machine now.
Given some of what was mentioned here, I guess there was a bug fix or - see the Avast UI right click menu 'Engine and Virus Definitions' engine update could also deliver a fix/update that would likely change the build number. As you mention the scheduled Emergency Update in the quoted text could result in a build number update.
What's not clear is why an update to 24.2.6104 (version 24.2.8904.825) is proposed when the installed version (via the "about" menu) is already this version.
I got that too when I rechecked the UI About - I did the update and restart to get rid of it - I suspect we are due for a UI version update, soon.
-
Once again, I've gone too fast.
There has been an update:
24.2.6105 (version 24.2.8918.824)
-
am i missing something?
update shows as 24.2.8904.825
now updated it shows as 824 installed
-
you need to look at the figures just before (04 and now 18)
8904.825 < 8918.824
-
Updated myself. Must have just been a minor update as there was no 'What's new' pop up or notes.
Before and afters attached.
-
OK, so as I understand it, if I choose to manually update from the forced version 24.2.6104 (24.2.8904.825), I will expect to get 24.2.6105 (version 24.2.8918.824). I will let you know if I win the lottery with a different set of version numbers.
This 24.2 production version update fiasco would be considered funny, if it was not so serious and confusing to us users, without any explaination from Avast devs.
Anyhow, I guess we are all BETA testers now, as the last Avast BETA version announced on the forum was 24.2.6102 (build 24.2.8877) February 22, 2024. We are well beyond that version now.
EDIT:
I went and did manual version update. I now have this updated version/build and updated UI version:
-
Once again, I've gone too fast.
There has been an update:
24.2.6105 (version 24.2.8918.824)
I see the UI has also been updated to 1.0.799 given my last post.
-
Once again, I've gone too fast.
There has been an update:
24.2.6105 (version 24.2.8918.824)
I see the UI has also been updated to 1.0.799 given my last post.
yes, but strange
the UI went from 1.0.799 this morning to 1.0.798 after the midday update and now back to 1.0.799. ???
-
Once again, I've gone too fast.
There has been an update:
24.2.6105 (version 24.2.8918.824)
I see the UI has also been updated to 1.0.799 given my last post.
yes, but strange
the UI went from 1.0.799 this morning to 1.0.798 after the midday update and now back to 1.0.799. ???
I think this could be conflict in what was/is being updated and how. Program, Engine and virus definitions, UI and possible fix, or via Emergency update schedule.
This flip flopping isn't a confidence builder.
-
Here you go. (Full offline version from 24.1 announcement created February 7, 2024, png attached below) See: https://forum.avast.com/index.php?topic=326107.0 (https://forum.avast.com/index.php?topic=326107.0) Clicking offline avast version does not give 24.1, but gives 24.2.
Have not yet updated but did notice that the general download link Avast provided for all supported programs also has the most recent versions of program installers here: https://www.avast.com/installation-files#pc (https://www.avast.com/installation-files#pc) See screenshot from this site below:
As I have not yet installed the latest version cannot attest that either versions are identical at this time.
@DavidR: I concur.
-
The generic link always downloads the latest released version available at the time you download.
-
At last, an announcement of V24.2 by Lukas here: https://forum.avast.com/index.php?topic=326953.0
Also download links for online/offline installers.
There is mention of HOTFIX for UI issue, linked to the weird version update happenings we have experienced and documented in this thread.
I hope this underlines the problems and that normal service is now resumed re version updates.
-
At last, an announcement of V24.2 by Lukas here: https://forum.avast.com/index.php?topic=326953.0
Also download links for online/offline installers.
There is mention of HOTFIX for UI issue, linked to the weird version update happenings we have experienced and documented in this thread.
I hope this underlines the problems and that normal service is now resumed re version updates.
I would like to hope so.
-
Out of the blue, Avast wanted me to do a [Restart] in the middle of doing other things this afternoon. I don't know what that was for, but I packed up what I was doing and restarted. I will re-check my versions/builds later and report here if any have incremented.
EDIT: I now have. 24.2.6105 (build 24.2.8918.827)
-
Out of the blue, Avast wanted me to do a [Restart] in the middle of doing other things this afternoon. I don't know what that was for, but I packed up what I was doing and restarted. I will re-check my versions/builds later and report here if any have incremented.
EDIT: I now have. 24.2.6105 (build 24.2.8918.827)
Has the UI also updated ?
Mine are still the same as in my signature below my post. Mind you mine are set to Manual update.
A manual update reports up to date.
-
the UI hasn't changed for me (still 1.0.799) but the build has (827 from 14 March like rocksteady).... manual update too.
-
I just wonder if this build irregularity might be Avast Premier Vs Avast Free as in mine ?
-
I'm on build .824
For the ones who are on .827, did you restart or even power on/off your computers over the last couple of days, but not because of an Avast update? Sometimes the build numbers update after a power on or restart. I plan on doing a shutdown tomorrow while i'm out of my apartment so I can see if mine updates then.
-
I'm on build .824
For the ones who are on .827, did you restart or even power on/off your computers over the last couple of days, but not because of an Avast update? Sometimes the build numbers update after a power on or restart. I plan on doing a shutdown tomorrow while i'm out of my apartment so I can see if mine updates then.
Things update with a restart. Shut down down doesn't update which is why you're asked to restart your computer.
-
I have seen the build number update on a shutdown (not restart) with Fast Startup enabled. Just the last three digits of the build number, though.
Other things, like the UI version, will sometimes update without either and while your computer is still running.
-
Out of the blue, Avast wanted me to do a [Restart] in the middle of doing other things this afternoon. ...
EDIT: I now have. 24.2.6105 (build 24.2.8918.827)
Like I said, a central screen pop-up saying 'you need to do a Restart' suddenly appeared. It interrupted a backup I was performing, so not best pleased. This appeared extra to Restart from Manual update and Restart to 24.2 previous, so was it an emergency update, only Avast knows. After that Restart, I found I then had new build .827, but same UI .799.