.2246 new beta?

[Andrey,pro]

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 

[irongod]

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

[REDACTED]

This is getting to be a real circus. Does anyone from Avast know what is going on?

[Rednose]

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.

[REDACTED]

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.

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.

[hectic-mmv]

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?

[Andrey,pro]

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)

[REDACTED]

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

[bob3160]

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.

[Asyn]

It looks to be problem in grimefighter/cleanup module. Did you have Cleanup/grimefighter installed?

Nope. It was never installed here.

[Para-Noid]

One thing is sure, the GUI says a beta update is available.
Not downloading until avast addresses this/these issues

[irongod]

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 !! 

[bob3160]

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 

[schmidthouse]

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.

[Andrey,pro]

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