Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: irongod on December 18, 2015, 10:32:12 AM
-
I got notified yesterday eve that a new version .2246 was available and had to restart to complete the update... afterwards the Avast Services could not start. Tried to repair twice, but got always the same issue after rebooting... I will try tonight with a clean install. >:(
But what is this new version? new beta? I still cannot find anything in the forum
I currently have installed Win10 (Home)
-
But what is this new version? new beta? I still cannot find anything in the forum
Yep, it's a beta. Unfortunately no changelog yet.
-
It was also installed in me to start .2246 but fails to initiate protection of your computer
-
it would be nice to hear some beep from Avast! team what is that beta about
like critical fix, unimportant tweaks or so
-
it would be nice to hear some beep from Avast! team what is that beta about
like critical fix, unimportant tweaks or so
Its a non-functional Beta, thats what i can tell you :P
-
No way I have tried in many ways but also by uninstalling and reinstalling the version does not solve the problem, at this point I went back to the stable version until the team of programmers will not have solved the problem
-
it would be nice to hear some beep from Avast! team what is that beta about
like critical fix, unimportant tweaks or so
Its a non-functional Beta, thats what i can tell you :P
then it should be immediately withdrawn from the GUI!! :o (I removed Avast and planning to reinstall a clean stable vesrion tonight so I cannot see ... )
But this silence (soon 24h) from AVAST sounds scary considering that this issue seems to force every beta tester to perform a clean reinstall of AVAST!!!
-
Why would a non functional Beta be pushed? This makes no sense.
-
Why would a non functional Beta be pushed? This makes no sense.
I was wondering the same ... I hope it was not a kind of attack to disable Avast (I know it would be too much of a cyber-phantasy theory! ;D )
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
Maybe its all a server issue or something, seems theyre changing alot of IT-Stuff right now.
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
Maybe its all a server issue or something, seems theyre changing alot of IT-Stuff right now.
Not in my case. Download and install went fine, the problems started afterwards.
-
My avast is already updated, but I'm wondering I should postpone reboot of the computer until further notice. :-\
This beta might be internal beta that mistakenly pushed out to public.
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
Maybe its all a server issue or something, seems theyre changing alot of IT-Stuff right now.
Not in my case. Download and install went fine, the problems started afterwards.
Well HDW had issues downloading the free version, we have to wait and drink tea :)
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
Maybe its all a server issue or something, seems theyre changing alot of IT-Stuff right now.
Not in my case. Download and install went fine, the problems started afterwards.
I did a clean install of 11.1.2245, to come of the beta trial version - so it wasn't offered - interestingly today the Avast Emergency Update (with its uniquely named executable) took place shortly after boot.
I just wonder if this had anything to do with this failed beta update.
-
Its a non-functional Beta, thats what i can tell you :P
Confirmed for XP.
Maybe its all a server issue or something, seems theyre changing alot of IT-Stuff right now.
Not in my case. Download and install went fine, the problems started afterwards.
Well HDW had issues downloading the free version, we have to wait and drink tea :)
I'll post my experience in the German section shortly. ;)
-
I did a clean install of 11.1.2245, to come of the beta trial version - so it wasn't offered - interestingly today the Avast Emergency Update (with its uniquely named executable) took place shortly after boot.
I just wonder if this had anything to do with this failed beta update.
No, I had the EMU already installed before the beta update.
-
I have turned off all auto program updates.
-
.2246
No Protection. Can't start to get the protection to work.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450457820814-37948.png)
-
.2246
No Protection. Can't start to get the protection to work.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450457820814-37948.png)
I got to know now that this is a KNOWN BUG, so why are they releasing this BETA anyway? ::)
-
.2246
No Protection. Can't start to get the protection to work.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450457820814-37948.png)
I got to know now that this is a KNOWN BUG, so why are they releasing this BETA anyway? ::)
A repair took forever and resolved nothing.
-
The emupdate always runs right after a boot.
Part of the job is to check the integrity of the installed avast version.
In case it got infected or otherwise crippled, it will try to "repair" avast.
-
The emupdate always runs right after a boot.
Part of the job is to check the integrity of the installed avast version.
In case it got infected or otherwise crippled, it will try to "repair" avast.
As I've already stated, a repair did nothing. It's not protecting the system.
The fix button still fixes nothing.
-
The emupdate always runs right after a boot.
Part of the job is to check the integrity of the installed avast version.
In case it got infected or otherwise crippled, it will try to "repair" avast.
As I've already stated, a repair did nothing. It's not protecting the system.
The fix button still fixes nothing.
Did it twice, it repaired fairly quickly (and everything looked fine), but after booting the problem was still there!! (and still silence from Avast, at least on the forum!! :-[ )
-
The emupdate always runs right after a boot.
Part of the job is to check the integrity of the installed avast version.
In case it got infected or otherwise crippled, it will try to "repair" avast.
As I've already stated, a repair did nothing. It's not protecting the system.
The fix button still fixes nothing.
is among other bob3160 is not even easy to uninstall avast without avast cleaner because with the excuse that continues to ask you to restart your PC never starts uninstalling, I solved by turning off the updates and then uninstalling the beta version, now I have the free stable and goes perfectly
-
The emupdate always runs right after a boot.
Part of the job is to check the integrity of the installed avast version.
In case it got infected or otherwise crippled, it will try to "repair" avast.
As I've already stated, a repair did nothing. It's not protecting the system.
The fix button still fixes nothing.
is among other bob3160 is not even easy to uninstall avast without avast cleaner because with the excuse that continues to ask you to restart your PC never starts uninstalling, I solved by turning off the updates and then uninstalling the beta version, now I have the free stable and goes perfectly
Download Link for Avastclear: http://files.avast.com/beta9x/avastclear.exe
-
I had no problems uninstalling the beta. I didn't need avast.clear.exe
After removing it through Programs and Features, I re-installed the last stable version without problems.
I'm again protected.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450463992031-32430.png)
I'm however not using the Beta version.
-
MajorGeeks has this as a Download for the Free Version. Why the silence from Avast?
-
.2246
No Protection. Can't start to get the protection to work.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450457820814-37948.png)
I got to know now that this is a KNOWN BUG, so why are they releasing this BETA anyway? ::)
Hi guys,
there is no intention for this. If you still have some log files, could you send logs from
- c:\ProgramData\AVAST Software\Avast\log\
- c:\ProgramData\AVAST Software\Persistent Data\Avast\
to vanek at avast.com
There is really no intention to release wrong beta.
-
There is really no intention to release wrong beta.
Sorry, not sure what you mean..!?
So, is this an official beta, or not..?
If so, how about a changelog, to start with... ;)
-
Just updated and...now I just see 'You are unprotected' message, user settings were not preserved and I can't even change them. Tried to use Avast repair with no luck
Hmm...It was released in 1970 ;D
-
There is really no intention to release wrong beta.
Sorry, not sure what you mean..!?
So, is this an official beta, or not..?
If so, how about a changelog, to start with... ;)
+1
-
This is getting to be a real circus. Does anyone from Avast know what is going on???????????????????
-
To Avast and hectic-mmv :)
I understand there is no intention to release a wrong Beta.
But when it happens ( and I think it has here ) you should inform, and make that clear to your Beta testers !
Greetz, Red.
-
Was just forced to update via the 'Avast needs to restart your system' notice. I have not uninstalled/reinstalled for a long time - still on a Beta install started long ago.
Only bug - that brought me here tonight was the Restart window timer (setting to tomorrow, or anytime does not work, it shows the window again in minutes) - though found a post stating it is now known and will be fixed.
So - I restarted manually - noted some Windows 10 updates also, and upon reboot - Avast Install is complete usual pop-up was shown.
Opening Avast and clicking the Gear showing the normal option window and picking About shows version 11.1.2246.
(http://Avast11.1.2246.jpg)
Mouse-over icon states 'You are Protected'.
Not sure about Full Scan though - not the same issue others are having, I question whether there is not a flaw in this build:
Selecting Scan, Full scan, appears to be working, maybe, albeit very slow - still at 0% in 30+ minutes, and
it appeared to be going through files but now is stuck on SVC:Winsock > ? ? ? for 20+ minutes. During this time, Task manager shows 12% CPU for AvastSvc.exe with varying memory usage 29k to 32k - what is SVC:Winsock and should it take this long?
Maybe this is normal.
Cancelled after 25 minutes and
started a Quick Scan - percentages increased over 15 minutes to completion, with memory usage varying from 40k to 83k.
Warning unable to scan files... Files found in C:\Windows.~BT\Sources\SafeOS.Mount\Windows\... these folders should be ignored, I believe they are used by Windows 10 update and recovery.
I attached a screenshot of my about window.
So - not sure why 2246 is not working for some - basic protection and Quick Scan appears to be working for me.
General comments:
Dislike the spinning circle arcs - prefer stacked progress bars, top for total scan % and bottom for file scan progress continual movement - from a distance much easier to see than circles.
Oh, just noticed - geez, did not even notice inner orange on black full progress I guess - yuck - can hardly see at all. Make the orange fill the width of the black circle line changing from black to orange, and the inner blue arcs - replace with spinning pie chart 0 to 100% toggling collors - keep percent on white box within - at least it would be noticeable.
-
To Avast and hectic-mmv :)
I understand there is no intention to release a wrong Beta.
But when it happens ( and I think it has here ) you should inform, and make that clear to your Beta testers !
Greetz, Red.
You are right Red, we should inform. It looks to be problem in grimefighter/cleanup module. Did you have Cleanup/grimefighter installed?
-
Hello Michal,
I've already answered via email but I'll duplicate my reply here.
No, I don't have Avast CleanUp Installed. Also when I tried to reset settings I got this error message (see attached files)
-
after i got the 'unprotected' bug i had avast completely deinstalled whith the avastclear.exe file. Then i reinstalled this beta (offline installer) and it worked.
Problem was after i got to the main ui i got an error:
Failed to load languaga dll language path: 1033\UIlangRes.dll
Normaly my UI is in dutch but now it is reberted back to english.
EDIT: After like 20 minutes ofter the succesfull install avast is not working enymore. Background service isnt running according to avast and my settings keep resetting. Off to the last rtm release
-
I also didn't have the CleanUp module installed.
The removal and change to a stable version was fairly simple on my 32 bit systems.
It was a genuine pain in the rear on my 64 bit systems.
There is a problem with this release. Fix it or remove it before others wind up with headaches.
-
It looks to be problem in grimefighter/cleanup module. Did you have Cleanup/grimefighter installed?
Nope. It was never installed here.
-
One thing is sure, the GUI says a beta update is available.
Not downloading until avast addresses this/these issues
-
To Avast and hectic-mmv :)
I understand there is no intention to release a wrong Beta.
But when it happens ( and I think it has here ) you should inform, and make that clear to your Beta testers !
Greetz, Red.
You are right Red, we should inform. It looks to be problem in grimefighter/cleanup module. Did you have Cleanup/grimefighter installed?
Neither here... Cleanup is not installed !! 8)
-
After the hrs. of fixing I've just gone through, I will not be doing any more beta testing till Avast comes up with a fix or a new version
that addresses these problems.
Sorry :'(
-
There are always risks when beta testing, that's why it's call "beta" and I think most realize this when they "willingly" enter a beta test.
That being said, imo It's the lack of response that is frustrating.
I personally have exited/ceased using the 'beta channel' by staying with 'Final Release version' over a year ago for the specific reason that "consistent interaction" from developers/Avast is/was/has been essentially non-existent.
Over the months, I've read post after post by users testing beta versions that never receive a response from Avast.
This certainly does not inspire confidence in, or loyalty to beta testing.
-
I think Michal is very busy, he found the root of this issue:
Yes, this is the problem. Not installed Cleanup but its loading in Avast service. We will push quick fix on this next week.
We are really sorry for this inconvinience. We dont want this crashes, it can appear in beta program.
I don't see any problems and I agree with schmidthouse, that's why it's a beta version
-
I think Michal is very busy, he found the root of this issue:
Yes, this is the problem. Not installed Cleanup but its loading in Avast service. We will push quick fix on this next week.
We are really sorry for this inconvinience. We dont want this crashes, it can appear in beta program.
I don't see any problems and I agree with schmidthouse, that's why it's a beta version
The thing that I didn't like about the beta function was that it constantly switched the program updates to Auto Update, so the first you knew about it was 'the computer needs to be restarted' message.
I always had the old default 'Notify if a new update is available' that way I at least have some control over what I download and what is installed, when and when to restart. Once you get to that point there is no means to back out of the update as the update has already occurred.
-
I don't see any problems and I agree with schmidthouse, that's why it's a beta version
Well, the problem is, that we still didn't get any kind of changelog... ::)
-
I think Michal is very busy, he found the root of this issue:
Yes, this is the problem. Not installed Cleanup but its loading in Avast service. We will push quick fix on this next week.
We are really sorry for this inconvinience. We dont want this crashes, it can appear in beta program.
I don't see any problems and I agree with schmidthouse, that's why it's a beta version
Even betas are tested before being released and usually have known problems reported before the release.
This isn't an Alpha.
This beta couldn't have been tested to any extent before being released.
-
The thing that I didn't like about the beta function was that it constantly switched the program updates to Auto Update, so the first you knew about it was 'the computer needs to be restarted' message.
Hi David, on my laptop it's not switching the program updates to Auto and even I participated in beta testing I manually updated to the latest beta version after I see the the popup about new version available
I don't see any problems and I agree with schmidthouse, that's why it's a beta version
Well, the problem is, that we still didn't get any kind of changelog... ::)
Yep, it's the only problem ;)
Even betas are tested before being released and usually have known problems reported before the release.
This isn't an Alpha.
This beta couldn't have been tested to any extent before being released.
I think it was tested when all components were installed (including Avast CleanUp) that's why they didn't encounter this bug.
-
Bob, before each release, there is a huge block of automated tests which checks the functionality. There is a test for update, unfortunately not for a combiniation, update without CleanUp.
As MartinZ wrote in his post, we are going to release new beta version every Thursday. The changelog will be shorter.
- https://forum.avast.com/index.php?topic=179943.0
Main changes in the current build:
- Passwords - Correct timestamp for password history.
- Uninstall - conditional deleting more files during uninstalling sandbox
- Passwords - performance login issues
- Streaming updates - fixed race-condition deadlock
-
Finally... Thanks.
-
Bob, before each release, there is a huge block of automated tests which checks the functionality. There is a test for update, unfortunately not for a combiniation, update without CleanUp.
As MartinZ wrote in his post, we are going to release new beta version every Thursday. The changelog will be shorter.
- https://forum.avast.com/index.php?topic=179943.0 (https://forum.avast.com/index.php?topic=179943.0)
Main changes in the current build:
- Passwords - Correct timestamp for password history.
- Uninstall - conditional deleting more files during uninstalling sandbox
- Passwords - performance login issues
- Streaming updates - fixed race-condition deadlock
Of all the add-ons in Avast, Cleanup is probably the one least related to protection and the one most avoided.
I'm not a programmer so don't know why omitting an add-on would cause such a complete disaster.
At the moment, I'm back on a stable build on the 5 computer affected in my home.
(Lesson learned, only update one of the systems and wait for the effects. :) )
-
Bob, before each release, there is a huge block of automated tests which checks the functionality. There is a test for update, unfortunately not for a combiniation, update without CleanUp.
As MartinZ wrote in his post, we are going to release new beta version every Thursday. The changelog will be shorter.
- https://forum.avast.com/index.php?topic=179943.0
Main changes in the current build:
- Passwords - Correct timestamp for password history.
- Uninstall - conditional deleting more files during uninstalling sandbox
- Passwords - performance login issues
- Streaming updates - fixed race-condition deadlock
just to know, is this a new process or has been used in the past? ::) ... just wondering whether this issue with .2246 is due to an unproperly tested version automatically pushed through... was it there any kind of non-automated testing in the past that has been removed? Which is the actual test coverage for betas?
-
To Avast and hectic-mmv :)
I understand there is no intention to release a wrong Beta.
But when it happens ( and I think it has here ) you should inform, and make that clear to your Beta testers !
Greetz, Red.
You are right Red, we should inform. It looks to be problem in grimefighter/cleanup module. Did you have Cleanup/grimefighter installed?
No, because of this topic I didn't install the Beta, but that is not the point.
I am just asking for a better response/feedback to your Beta testers.
Greetz, Red.
-
Bob, before each release, there is a huge block of automated tests which checks the functionality. There is a test for update, unfortunately not for a combiniation, update without CleanUp.
As MartinZ wrote in his post, we are going to release new beta version every Thursday. The changelog will be shorter.
- https://forum.avast.com/index.php?topic=179943.0
Main changes in the current build:
- Passwords - Correct timestamp for password history.
- Uninstall - conditional deleting more files during uninstalling sandbox
- Passwords - performance login issues
- Streaming updates - fixed race-condition deadlock
It would be nice to know the build number of the Beta in his post.
-
Bob, before each release, there is a huge block of automated tests which checks the functionality. There is a test for update, unfortunately not for a combiniation, update without CleanUp.
As MartinZ wrote in his post, we are going to release new beta version every Thursday. The changelog will be shorter.
- https://forum.avast.com/index.php?topic=179943.0
Main changes in the current build:
- Passwords - Correct timestamp for password history.
- Uninstall - conditional deleting more files during uninstalling sandbox
- Passwords - performance login issues
- Streaming updates - fixed race-condition deadlock
It would be nice to know the build number of the Beta in his post.
Essentially it is in the topic title .2246 an extension of the current 11.1.2245 regular release version.
-
New beta with fix for crashing Avast Service released now.
enjoy it and merry christmas!
-
New beta with fix for crashing Avast Service released now.
enjoy it and merry christmas!
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450878372492-69245.png)
Thank You and a Merry Christmas to you and the rest of the crew. :)
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450878678474-5676.png)
-
New beta with fix for crashing Avast Service released now.
enjoy it and merry christmas!
Great! But where's the changelog? ???
-
New beta with fix for crashing Avast Service released now.
enjoy it and merry christmas!
Great! But where's the changelog? ???
The fix for the crashing Service IS the changelog :)
-
... I guess I'll pass the beta this time! 8)
(it's Xmas and got no time ;D )
-
New beta with fix for crashing Avast Service released now.
enjoy it and merry christmas!
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450878372492-69245.png)
Thank You and a Merry Christmas to you and the rest of the crew. :)
(http://www.screencast-o-matic.com/screenshots/u/Lh/1450878678474-5676.png)
still no dedicated topic for the .2246/7 beta release? :o
-
still no dedicated topic for the .2246/7 beta release? :o
That is what I don't understand either :-\
Greetz, Red.
-
New beta Avast 2015 SP2 beta3 has been released, build number 2016.11.1.2248.
Main changes:
- updated SafeZone Browser with multiple security fixes
- fixed possible deadlock in file-system shield and during streaming updates
- fixed missing registration information after program update
- improved security of avast components in memory
-
New beta Avast 2015 SP2 beta3 has been released, build number 2016.11.1.2248.
Main changes:
- updated SafeZone Browser with multiple security fixes
- fixed possible deadlock in file-system shield and during streaming updates
- fixed missing registration information after program update
- improved security of avast components in memory
Will we see improvements in HIPS and other security related parts for R2?
Or is that postponed again?
-
Something you should fix after the Upgrades: http://prntscr.com/9n9eku
Firewall doesnt start after reboot from BSOD.
-
Something you should fix after the Upgrades: http://prntscr.com/9n9eku
Firewall doesnt start after reboot from BSOD.
Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle
-
New beta Avast 2015 SP2 beta3 has been released, build number 2016.11.1.2248.
Main changes:
- updated SafeZone Browser with multiple security fixes
- fixed possible deadlock in file-system shield and during streaming updates
- fixed missing registration information after program update
- improved security of avast components in memory
Does the BETA fixes avast passwords slow interface bug (5-10 min of loading until passwords list is shown)? ;)
-
Does the BETA fixes avast passwords slow interface bug (5-10 min of loading until passwords list is shown)? ;)
Already has been fixed in 2246, see: https://forum.avast.com/index.php?msg=1277993
-
New beta Avast 2015 SP2 beta3 has been released, build number 2016.11.1.2248.
Main changes:
- updated SafeZone Browser with multiple security fixes
- fixed possible deadlock in file-system shield and during streaming updates
- fixed missing registration information after program update
- improved security of avast components in memory
Hi hectic-mmv :)
This is not the way Beta-testing should go.
As an Avast Moderator you should have made a new topic.
Now it looks almost like some Alpha for insiders :-\
Greetz, Red.
-
+1
New release whether it be a beta or otherwise should have a new topic.
My GUI shows v2248 is out but no new topic.
In the future please start a new topic with each release beta or otherwise.
-
... it feels like "something" happened within Avast with these Betas: almost a month and still no new topic, never really clear about what happened with .2246 and small details on the following ones. + now my Streaming Updates went off first and after reactivating they still show 0 (I currently have .2245).
;D well, I guess I will have to continue wonder about these...
-
+1
Considering this topic was started by an avast user 'irongod' querying an unannounced beta that also failed and stuffed up lots of beta testers systems.
The fact there was no original .2246 beta topic, so no change log as to what was in it. Then a new .2247 beta release tagged on to this topic and still no change log.
It is important that all beta releases/updates should have their own new topic, how else would beta testers comment on that beta build, etc. How would others trying to follow the beta testing extract any information on issues, etc. from what is now a pretty big and confused topic.
-
+1
+Clean the whole Beta section and allow further posts only in the corresponding beta topics. With regular weekly releases there is no need for separate posts for each bug, the forum isn't a bug tracker anyway.
-
Yes I have to agree with the 'common sense' posts by long time users/beta testers here.
An explanation or clarification of the changed process would I'm sure be appreciated. :)
-
It seems that the Avast Beta Team is in Winter hibernation :-\
Or they spend too much time at the Wine Bar near Charles Bridge in Prague :P
Greetz, Red.
-
It seems that the Avast Beta Team is in Winter hibernation :-\
Or they spend too much time at the Wine Bar near Charles Bridge in Prague :P
Greetz, Red.
+1
moreover, according to the beta process posted by Avast, by this time it should be out a new beta or RC or Release... I am currently sticking with .2245, but I belileve that after the last beta was out something like 15 days ago (.2248, if I am not mistaken!)