Avast 24.2.6104 (version 24.2.8904.819)

[DavidR]

@chris.. post:18

@bob3160 post:17

@chris.. post:1

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.

[chris...]

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.

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

[bob3160]

@chris.. post:22

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.

@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.

[DavidR]

@chris.. post:22

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.

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.

[DavidR]

@bob3160 post:23

@chris.. post:22

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.

@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.

[chris...]

@bob3160 post:23

@chris.. post:22

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.

@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.

[New_Style_xd]

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. >:(

[rocksteady]

@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.

[bob3160]

@New_Style_xd post:27

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.

[New_Style_xd]

@bob3160 post:29

@New_Style_xd post:27

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.

[DavidR]

@New_Style_xd post:30

@bob3160 post:29

@New_Style_xd post:27

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.

[midnight]

I don’t have a red x so should I update?

[New_Style_xd]

@midnight post:32

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.

[bob3160]

@New_Style_xd post:33

@midnight post:32

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.

[New_Style_xd]

@Dinobot2 post:3

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?

[Dinobot2]

Yes, and I discussed my experiences in the thread.

@Dinobot2 post:5

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.

[Nunzio77]

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.

[rocksteady]

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

[bob3160]

@rocksteady post:38

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

That’s a fair question considering that the latest new version announcement still states version 24.1.

[merckxist]

@rocksteady post:38

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.