** INTRODUCING **: pre-release version of upcoming avast update (now 4.8.1192)

[Vlk]

nightshade, the self-defense module (as with most NEW avast features) is for Windows 2000+ only. This is why it cannot be disabled (well, in fact, it cannot be enabled )

rdmaloyjr, why would that be a flaw in the self-defense system? To get from 1178 to 1185 you don't even have to run aswBeta.exe. Simply invoking the program update would actually do the trick. That's because you're now using the beta stream; the beta stream is always valid for all beta refreshes, and once the product is released officially, it is merged to the release stream.

Hope this helps,
Vlk

[nightshade]

I was able to manually update from 4.8.1178 to 4.8.1185 without disabling avast self-defense module.  Does this mean there is a flaw in the avast self-defense module?

Was it because the radio button was grey out for the self defence module therefore you were unable to disable it?

[rdmaloyjr]

nightshade,

Actually I forgot to disable it.


vlk,

I guess I misunderstood your instructions about disabling the self-defense module before updating.

Thank you for clearing it up.

[nightshade]

nightshade, the self-defense module (as with most NEW avast features) is for Windows 2000+ only. This is why it cannot be disabled (well, in fact, it cannot be enabled )

rdmaloyjr, why would that be a flaw in the self-defense system? To get from 1178 to 1185 you don't even have to run aswBeta.exe. Simply invoking the program update would actually do the trick. That's because you're now using the beta stream; the beta stream is always valid for all beta refreshes, and once the product is released officially, it is merged to the release stream.

Hope this helps,
Vlk

Hi Vlk,

Thanks for your kind reply,

I first installed Avast Free Home 4.8.1178 from the home user link http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB that apparently is the beta, although I didn't know that at the time that it was a beta.

I upgraded to 1185 by invoking the program update from 1178, so can I keep doing this for all time when there is either a program update and or beta refresh? due to the fact that I am unable to disable the self defense module? or can I only keep doing it this way for beta refreshes?

[Lisandro]

Can I keep doing this for all time when there is either a program update and or beta refresh?

Yes.

due to the fact that I am unable to disable the self defense module?

Once in beta program, you will update it with or without self defense module on.

[nightshade]

Once in beta program, you will update it with or without self defense module on.

And what about when it goes out of beta to an official release?

[Lisandro]

Once in beta program, you will update it with or without self defense module on.

And what about when it goes out of beta to an official release?

You're asking the same in two different threads...
The answer is the same...

[nightshade]

Once in beta program, you will update it with or without self defense module on.

And what about when it goes out of beta to an official release?

You're asking the same in two different threads...
The answer is the same...

I need an answer to this please.

http://forum.avast.com/index.php?topic=35043.msg294435#msg294435

[nightshade]

Once in beta program, you will update it with or without self defense module on.

And what about when it goes out of beta to an official release?

You're asking the same in two different threads...
The answer is the same...

You still havent answered my question on that post.

[Lisandro]

Once in beta program, you will update it with or without self defense module on.

And what about when it goes out of beta to an official release?

You're asking the same in two different threads...
The answer is the same...

You still havent answered my question on that post.

Keep there or here... choose.

[DavidR]

@ nightshade
Your questions was answered by what Vlk said to rdmaloyjr

nightshade, the self-defense module (as with most NEW avast features) is for Windows 2000+ only. This is why it cannot be disabled (well, in fact, it cannot be enabled )

rdmaloyjr, why would that be a flaw in the self-defense system? To get from 1178 to 1185 you don't even have to run aswBeta.exe. Simply invoking the program update would actually do the trick. That's because you're now using the beta stream; the beta stream is always valid for all beta refreshes, and once the product is released officially, it is merged to the release stream.

[nightshade]

Yes, so would I always be using the beta stream?

[Lisandro]

Yes, so would I always be using the beta stream?

Until you update to official release.
To enter a subsequent beta program you'll need to manually run aswbeta.exe again.

[nightshade]

Yes, so would I always be using the beta stream?

Until you update to official release.
To enter a subsequent beta program you'll need to manually run aswbeta.exe again.

ok, and this is what confused me you see, because I never ran the aswbeta.exe in the first place, and yet I have a beta, I think this was because the link I used included the beta release.

[Solemn]

Pleased to report that the issue regarding this:

2.) This may be related to the first issue, but I've noticed that avast!'s providers take considerably longer than usual to all activate/run.  Upon reboot, it used to say 4 providers running for a very short moment before instantly changing to 6 providers running (the outlook/mail provider is off of course).  This great performance was witnessed in 4.7 and even still in the early 4.8 beta versions.  Now it's different, where avast! reports that 4 providers are running for a long time.  Then after a while, 5 providers are running, and it stays like that for a long time as well.  After quite a bit of time after that, the 6th provider finally starts and the process is complete, but I can tell you the overall time for this to full setup on my relatively high performance rig is a lot longer than I'd expect (especially compared to the earlier versions of avast! that didn't exhibit this behaviour).  I can also note that the 6th provider takes the longest to start compared to the 5th and the rest in general.

...is solved! Looks like the providers speedily start up like they used to now in 4.7 after the update to 4.8.1185   Great work on this update!