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

[nightshade]

@Tech post:80

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]

@nightshade post:81

@Tech post:80

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]

@Tech post:82

@nightshade post:81

@Tech post:80

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]

@Tech post:82

@nightshade post:81

@Tech post:80

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]

@nightshade post:84

@Tech post:82

@nightshade post:81

@Tech post:80

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

@Vlk post:76

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]

@nightshade post:87

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]

@Tech post:88

@nightshade post:87

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.

[system]

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!

[Lisandro]

@nightshade post:89

I think this was because the link I used included the beta release.

Yes, this is the first time we have a standalone download for the beta setup.exe file.

[system]

@nightshade post:73

hines232 ,

When you say just download and go, are you referring to upgrading the program manually, I take it that you had Avast previously installed?

Yes. Latest version Avast Home/Free (updated today twice) I do not want to upgrade to “beta”, Just waiting for it to come down the pipe line for normal use !!. Should I Let it “Auto” install or "manually install it ?. (Windows ME) Thanks

[system]

@hines232 post:92

Yes. Latest version Avast Home/Free (updated today twice) I do not want to upgrade to “beta”, Just waiting for it to come down the pipe line for normal use !!. Should I Let it “Auto” install or "manually install it ?. (Windows ME) Thanks

If you’d like to know what version you are using, check your version number. The current official version is 4.8.1169 as you can see at the version history page. So, a version number any larger than 4.8.1169 means beta versions. Whether you manually/automatically update, as long as you are using official versions, it won’t download beta versions.

[Vladimyr]

@Vladimyr post:68

Good point! I’ll find out.

No it’s 1169. I’ll upgrade to 1185 (it’s dialup only at the moment for that PC) and let you know tomorrow.

igor
Upgraded to 1185 today, result same as 1169.

[system]

Can we please get the links updated for v4.8.1185?

Thanks…

[alanrf]

No sure I understand the “link” request.

As the start of the thread makes clear. The standard way to enter the beta program is to download and run “aswbeta.exe”. That puts you into the beta program and will download the current beta version of avast (in this case build 1185).

In fact, given discussions elsewhere I think it is most unfortunate for there to be any formal links to beta releases of avast that unsuspecting users might use and enter a beta program without being aware that they are doing so. I am not suggesting that (in special cases) avast may not need to publish them but having them highlighted - as at the start of this thread - is not a great idea.

I would suggest to Vlk that consideration of removing the links might well be in order.

[Vlk]

@alanrf post:96

No sure I understand the “link” request.

As the start of the thread makes clear. The standard way to enter the beta program is to download and run “aswbeta.exe”. That puts you into the beta program and will download the current beta version of avast (in this case build 1185).

In fact, given discussions elsewhere I think it is most unfortunate for there to be any formal links to beta releases of avast that unsuspecting users might use and enter a beta program without being aware that they are doing so. I am not suggesting that (in special cases) avast may not need to publish them but having them highlighted - as at the start of this thread - is not a great idea.

I would suggest to Vlk that consideration of removing the links might well be in order.

The direct links were useful primarily for those for which the official build didn’t work at all.
I understand that links may be distributed without our control, but, it’s not such a problem IMHO as

1. as soon as the update is officially released, we’ll put them offline
2. as soon as the update is officially released, those who have already installed the program using them (or will install it using the downloaded setup exe) will be automatically transferred to the “release stream” as soon as the avast updater is run for the first time (e.g. while updating the virus definitions).

Cheers
Vlk

[system]

Hmm…I was inclined to agree with alanrf on this one. However, thinking of it, the pre-release version seems to be quite stable and people seem to have more problem with that it is technically still beta rather than that they actually find problems with it. So, I just take it that the team is quite confident with the quality of the “pre-release” version.

[system]

@Rumpelstiltskin post:93

@hines232 post:92

Yes. Latest version Avast Home/Free (updated today twice) I do not want to upgrade to “beta”, Just waiting for it to come down the pipe line for normal use !!. Should I Let it “Auto” install or "manually install it ?. (Windows ME) Thanks

If you’d like to know what version you are using, check your version number. The current official version is 4.8.1169 as you can see at the version history page. So, a version number any larger than 4.8.1169 means beta versions. Whether you manually/automatically update, as long as you are using official versions, it won’t download beta versions.

Original Post !!! I am using latest Avast, system is ME, do not have Protection shield with ME, (which you are to bring down with new install, of newest version of Avast). How do we using ME install ???. And do we let it auto install or manually install ??

[Lisandro]

@hines232 post:99

do not have Protection shield with ME

There isn’t a shield called Protection.
Maybe you’re talking about the self defense module (or feature).

@hines232 post:99

(which you are to bring down with new install, of newest version of Avast). How do we using ME install ???. And do we let it auto install or manually install ??

Do you want to install the beta?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here for more information.