New Beta version 18.1.2325

[DavidR]

@NON post:20

My beta avast unknowingly turned into stable build, what happened? I tried to update to this version and found it want to update to stable one… :o

I wouldn’t be surprised if Avast hadn’t released it, we have seen this before, a new beta released followed a day later being released as stable update (and worse still with the same build number, causing further confusion). Though I haven’t seen it in my About Avast or Update UI screens as I have Program updates set to Manual.

[bob3160]

Just tried updating my regular version but there aren’t any updates beyond 17.9.2322

[BeSecure]

@bob3160 post:22

Just tried updating my regular version but there aren’t any updates beyond 17.9.2322

Same here.

[NON]

Well, I meant the beta build (18.1.2324) was (or would be) updated to stable one (17.9.2322), not the opposite.

[bob3160]

@NON post:24

Well, I meant the beta build (18.1.2324) was (or would be) updated to stable one (17.9.2322), not the opposite.

Did you do the update via the UI ???

[DavidR]

@NON post:24

Well, I meant the beta build (18.1.2324) was (or would be) updated to stable one (17.9.2322), not the opposite.

That would be strange, if you are on the beta stream (e.g. a beta version installed) then you should be offered beta stream updates, not the regular update stream. Since your beta build has a higher build number it shouldn’t go backwards to a lower regular update stream.

Effectively you should have got beta build 18.1.2325 if you had 18.1.2324.

[sedlacek]

@NON post:20

My beta avast unknowingly turned into stable build, what happened? I tried to update to this version and found it want to update to stable one… :o

This might happen when servers.def gets corrupted or otherwise is not available. Avast then downloads new servers.def from hardcoded fallback URL which points to release one. That in fact switches update channel to release one.

[sedlacek]

@DavidR post:21

I wouldn’t be surprised if Avast hadn’t released it, we have seen this before, a new beta released followed a day later being released as stable update (and worse still with the same build number, causing further confusion)

For couple of years we publish release builds to beta channel and then when no new critical issues are found (or we have micro updates for them) we publish them to release channel. Exactly same build, exactly same binaries, exactly same build numbers. This way we are publishing to release channel only what we have tested and you have helped us to validate.

[RejZoR]

Keeping same build for BETA and RELEASE at that point also kinda makes sense so BETA users after they finish the BETA cycle actually have the RELEASE version till new BETA is actually posted on their channel again. This way they are cycling beta and release versions, making testing in a way more extensive than if they’d constantly be rocking just beta builds that are always different than the public versions.

[jan.svoboda]

@Asyn post:9

@jan.svoboda post:1

Shell extension scan (scan option in mouse right click menu) is not showing progress in UI correctly sometimes - We would really appreciate your feedback with exact reproduction steps. Thank you.

Please elaborate how we should test this exactly…

Some possible scenarios for example:

1. You have Avast UI opened and select some file/folder to be scanned from shell extension menu
2. You have Avast UI closed and select some file/folder to be scanned from shell extension menu

You can try the same file/folder once/more times, try different files/folders for each attempt.

Is the progress of the scan displayed every time? Are there results of the scan available? Is the scan even finished for each file/folder?

Etc.

[bob3160]

@jan.svoboda post:30

@Asyn post:9

@jan.svoboda post:1

Shell extension scan (scan option in mouse right click menu) is not showing progress in UI correctly sometimes - We would really appreciate your feedback with exact reproduction steps. Thank you.

Please elaborate how we should test this exactly…

Some possible scenarios for example:

1. You have Avast UI opened and select some file/folder to be scanned from shell extension menu
2. You have Avast UI closed and select some file/folder to be scanned from shell extension menu

You can try the same file/folder once/more times, try different files/folders for each attempt.

Is the progress of the scan displayed every time? Are there results of the scan available? Is the scan even finished for each file/folder?

Etc.

I don’t see any problem: https://screencast-o-matic.com/watch/cFnhX8oB4H

[Asyn]

@jan.svoboda post:30

Some possible scenarios for example:

1. You have Avast UI opened and select some file/folder to be scanned from shell extension menu
2. You have Avast UI closed and select some file/folder to be scanned from shell extension menu

You can try the same file/folder once/more times, try different files/folders for each attempt.

Is the progress of the scan displayed every time? Are there results of the scan available? Is the scan even finished for each file/folder?

Etc.

OK Jan, tested it as suggested above…
Result: It sometimes works and sometimes it won’t.
Couldn’t find any obvious pattern, sorry.

[NON]

@jaromir post:27

@NON post:20

My beta avast unknowingly turned into stable build, what happened? I tried to update to this version and found it want to update to stable one… :o

This might happen when servers.def gets corrupted or otherwise is not available. Avast then downloads new servers.def from hardcoded fallback URL which points to release one. That in fact switches update channel to release one.

OK, thanks for the answer. I reinstalled beta on it and back to beta stream.

[Pako7]

am not a Beta user but am so exisited about the beta version…hope to see the update on avast premire soon…

was wondering if scanning item on virus chest …would it work again??or it has been dismissed??

[Asyn]

@Pako7 post:34

was wondering if scanning item on virus chest …would it work again??

Yes.