AVAST 2015 R3 RC (2015.10.3.2222)

[schmidthouse]

Will the ‘newly written’ Sandbox and SafeZone be active in the next beta build?
Thank you

[Rednose]

@schmidthouse post:41

Will the ‘newly written’ Sandbox and SafeZone be active in the next beta build?
Thank you

Personally I had expected more functionality, like creating different Sandboxes for different purposes.
So far I don’t see any changes.

Greetz, Red.

[schmidthouse]

@Rednose post:42

@schmidthouse post:41

Will the ‘newly written’ Sandbox and SafeZone be active in the next beta build?
Thank you

Personally I had expected more functionality, like creating different Sandboxes for different purposes.
So far I don’t see any changes.

Greetz, Red.

This beta has more interest in Grimefighter and HIPS then the SafeZone Browser, which for my needs personally is far more important.
But hey I’m just one user.

[Rednose]

@schmidthouse post:43

@Rednose post:42

@schmidthouse post:41

Will the ‘newly written’ Sandbox and SafeZone be active in the next beta build?
Thank you

Personally I had expected more functionality, like creating different Sandboxes for different purposes.
So far I don’t see any changes.

Greetz, Red.

This beta has more interest in Grimefighter and HIPS then the SafeZone Browser, which for my needs personally is far more important.
But hey I’m just one user.

You are right : A flawlessly working SafeZone is even more important.

Greetz, Red.

[system]

@bob3160 post:15

@RejZoR post:14

Why are all these proactive features stuffed under individual shields or even under broad settings? It’s so confusing. Why not create a dedicated proactive shield that has the Hardened mode controls under it, HIPS controls and other global features that are designed for proactive protection?

I don’t se cramming of everything into already crowded settings and there you have the sheild list that is 3/4 empty…

Currently, HIPS settings are hidden underneath File System Shield → Sensitivity submenu which is frankly a bit inconvenient place to have it…

Totally agree. All the extra protection is nice but if you can’t find it, what good is it going to do anyone.
Most users including me believe in “Keep it Simple Stupid”.

+1

[Para-Noid]

Last night when I tried to shut down my system it kept restarting over and over and over again.
This morning same old same old, nothing worked…again.
Back to v2015.10.2.2218.

[RejZoR]

I don’t have any problems with it. I did uncheck “Monitor suspicious activities” in HIPS and enabled max sensitivity. So it only monitors malware like behavor and nothing else.

[schmidthouse]

I’ve uninstalled the beta on xp and reinstalled latest Version until there is a SafeZone component to test that’s functional.

[bruceb]

This morning, Avast said there was an update to 2015.10.3.2219
Updated ok via the UI … not sure why this is not listed as a final
release as yet (seems like it should have been)

[bob3160]

@bruce_b post:49

This morning, Avast said there was an update to 2015.10.3.2219
Updated ok via the UI … not sure why this is not listed as a final
release as yet (seems like it should have been)

It isn’t a final it’s a beta version. If you received an update notice than you’ve been a recent beta tester for Avast.

[Secondmineboy]

Avast Beta and VMWare Workstation (Updating VMWare Tools): http://prntscr.com/7ivtkq

[bruceb]

Didn’t think I was on the beta, as my system had the last Final Release of Avast installed.
Now I have this one 2015.10.3.2219 … So that does mean I am now on the Beta ?
How does it get back to the normal release channel ? ? So far, this new version seems ok.

[system]

@bruce_b post:52

1. Didn’t think I was on the beta, as my system had the last Final Release of Avast installed.
2. Now I have this one 2015.10.3.2219 … So that does mean I am now on the Beta ?
3. How does it get back to the normal release channel ? ? So far, this new version seems ok.

1. Final release was ‘2015.10.2.2218’.
2. That’s R 3, Beta 1.
3. If you have no trouble, let it remain as it is. Otherwise you have to download and install ‘10.2.2218’.
   → https://forum.avast.com/index.php?topic=172470.msg1224510#msg1224510
   
   HDW

[schmidthouse]

@bruce_b post:52

Didn’t think I was on the beta, as my system had the last Final Release of Avast installed.
Now I have this one 2015.10.3.2219 … So that does mean I am now on the Beta ?
How does it get back to the normal release channel ? ? So far, this new version seems ok.

You have to do a “Clean Install” of Version 2015.10.2.2218

[Alikhan]

… What’s going on about the new Safezone/Sandbox?

[schmidthouse]

@Alikhan post:55

… What’s going on about the new Safezone/Sandbox?

Has been asked and not answered :-\

[Rednose]

@Alikhan post:55

… What’s going on about the new Safezone/Sandbox?

We don’t know :-\

I see no difference in Sandbox in the Beta, and SafeZone is not available …

Greetz, Red.

[bruceb]

I might do that when the next final release comes out. I will need to export my exclusions first or else I need to put them all back in. There should be an easier way to get back on the main release channel, maybe in an .ini file or a registry key.

[schmidthouse]

@bruce_b post:58

I might do that when the next final release comes out. I will need to export my exclusions first or else I need to put them all back in. There should be an easier way to get back on the main release channel, maybe in an .ini file or a registry key.

There are “major” differences/added components/different code between the Beta and Version 2015.10.2.2218
I don’t believe you can ‘just alter an .ini file or change a Registry entry’

edit

[bruceb]

I am sure there are changes, but so far the Beta is running just fine. It would just be a bit of work to go back to V2218 … you would think Avast would put an option in program UI to select either the Beta or Release Channels for updates. … Perhaps this idea should be sent on to the Avast Coding Group ? ? ?