Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: Karel Šťavík on December 20, 2017, 02:39:50 PM
-
Hi everyone,
new beta version 17.9.2322 (build 17.9.3761.0) is released.
Changes / Fixed Bugs
- Fixed crash of Avast service during computer shutdown
- Added localization for new features in 17.9
Download links:
https://forum.avast.com/index.php?topic=179943.0
Enjoy this beta!
We are looking forward to your feedback.
AVAST Team
-
Thanks for the new beta :)
-
Tray icon animation still broken?
-
Does it work on latest redstone 4 windows 10 insider preview builds without it causing a looping crash?
-
Tray icon animation still broken?
Yep, not fixed yet.
-
I just don't get it how can anything, regardless of significance ever be as unimportant that they can break it and leave it unfixed for so long. For example, the amoeba animation loop bug was half a year in the fixing, just so they absolutely completely broke it now after just what, 2 months of being functional? Importing of setting, broken ever since this version was released in February 2017. Almost one whole year and it's still broken with excuse that they are working on new configuration storage. Ok, cool. But you can't then leave the old one just broken and useless for whole freaking year. Because it's not working, I have to set everything over and over again when I install avast!. Not to mention people can't use my custom configuration because importing simply doesn't work. It's just so weird what's happening for quite a while now...
-
This build was today promoted to public channel
-
What is the point of having a beta released one day and the next day released as a regular program update. That gives zero time to check anything, much less report it. I despair about the betas and if it is worth bothering any more.
Lets not forget my pet hate released to regular stream with the same version number.
I look at the change log entries for this beta and then the regular release, so different how could they possibly have the same version number.
-
I look at the change log entries for this beta and then the regular release, so different how could they possibly have the same version number.
Change log in the latest beta would only contain changes made since the previous beta release.
As for the release, they would have to list all of the new features / fixes since previous full release.
-
I look at the change log entries for this beta and then the regular release, so different how could they possibly have the same version number.
Change log in the latest beta would only contain changes made since the previous beta release.
As for the release, they would have to list all of the new features / fixes since previous full release.
There are a lot of What's new: items, that I haven't seen mentioned in other betas.
But two things as I have said:
1. What is the point of releasing a beta version for just one day.
2. Plus my usual hobby horse, the regular release having the same version number as the last beta build. Especially when there are many 'What's new:' entries.
-
There are a lot of What's new: items, that I haven't seen mentioned in other betas.
But two things as I have said:
1. What is the point of releasing a beta version for just one day.
2. Plus my usual hobby horse, the regular release having the same version number as the last beta build. Especially when there are many 'What's new:' entries.
Well, they did very few changes in last beta, fixing a single bug and mostly focusing on localization. I wouldn't expect too much trouble when no new features are added, but certainly it doesn't hurt to release the last Release Candidate as a Beta version, shortly before final release, wouldn't it?
In case of a major blocker, they would learn about it from beta testers. Plus keep in mind the release is initially going to be installed only by early adopters who update manually. The auto-update will trigger some time later.
-
That's the problem, a day simply isn't enough, you could trawl through the beta sub-forum and see just how much activity there was in that day.
And as I keep saying, what about the new stuff. Not forgetting the stuff that wasn't working in the previous bets that still aren't working. Avast need a period of consolidation to fix bugs that have been reported many times, before introducing new stuff.
-
Yes, I would prefer a "bug FREE" version against a "new feature" . The GUI for months does not open properly. Packed full filling stuff Not good direction. The STABILITY is the suitable route.
-
Why I have this Beta version: 17.9.2322 (Build 17.9.3761.0) In the Stable version?
Yesterday was released the new version (Stable) with the new gui for protection and scanning, but I had them for a month without having downloaded the beta.
https://imgur.com/a/aLIWb
-
It now shows I have the Beta. Yesterday I had the latest stable version. I don't want the Beta.
-
It now shows I have the Beta. Yesterday I had the latest stable version. I don't want the Beta.
Clean install needed to go back to the stable version.
Don't use the installer from this section.
-
Are we expecting new beta this week?
Edited my post
-
Are we expecting new beta this week?
Edited my post
No, in around 2-3 weeks.