here I’m again. An avast Home/Pro update is coming soon (1st half of the next week - before part of the team leaves for the US) and now it’s my pleasure to announce the availability of a pre-release version of this update. This build is a very good approximation of what the final update will look like (we don’t plan making any changes yet - except for respective bug fixes).
How to install it (for starters - most people already know this trick anyway :)): simply download and run the following program: http://files.avast.com/files/beta/aswbeta.exe . That’s about all it takes.
The fixes in this release include
detection of ZA and partial disable of WebShield (sorry guys)
detection/removal of certain conflicting LSP’s
improved scanning of archives (including handling of corrupted archives)
lots of minor bugfixes
and other.
Please make sure to post your respective comments about this release either directly to this thread or (even better) by starting a new one.
Nice work on the tutorial – I agree. However, regarding the “Local Area Network (LAN) Settings”… is this a fix applicable for broadband users only? What about those on dialup?
Thanks again to all the members of the Avast team (and volunteers) for keeping up the good work in troubleshooting this problem. 8)
Regards,
Churchmouse
P.S. Lately I’m beginning to feel like “troubleshooting” = computer + gun → shoot computer = no more trouble.
P.P.S. Never mind previous question – I got the new program update and so far all is working well for the first time in nearly 2 months!! ;D Keeps fingers crossed
We’ll add a tutorial for dial-up users before the update is released.
The procedure is basically the same as in the case of broadband/LAN connections except that instead of using the “LAN Settings” button, you’d select the dial-up connection you’re using from the list in that “Connections” dialog, and click Settings. A new dialog box appears, with the ability to enter the proxy details.
My sister (and perhaps some others we know) will be needing this update also; but she’s never gotten a pre-release… I myself wasn’t notified via the auto-update feature of Avast; but just happened to check my program settings (update configuration) and noticed the advisory… Is this because I downloaded the previous beta version (639)?
Yes, if you were already using the beta update stream, you’d simply do a program update from within the avast GUI (no need to run aswBeta.exe). As soon as we officially release the update, all pre-release users will be automatically redirected to the release stream.
Lastest build seems to be working mostly good for me, however i seem to lose my manually added blocked file extensions in Standard Shield > customize > Blocker.
Ill have to double check this by installing the newest pre-release on the win98 machine downstairs.
I am very disappointed to see that, after installing 4.6.647, all support for the recently provided registry override for temporary file placement has been removed.
No, it was not a deliberate action.
I know that there were some changes that might (if done incorrectly) cause this, but I have tried to change the temporary file folder using the registry value and it seemed to work as expected. How exactly did you set the temporary folder? I will re-check on Monday…
Program: Already up to date
(current version 4.6.647)
Vps: Already up to date
(current version 0515-5)
I still get red box. I have to update manually. Does anyone know how to open this screen again? how to turn web shield transparent proxy mode off and in future we need to turn it on, how to turn it on? LAN does not apply to dial-up. What should I do? Is there a video for dial-up user?
I have been using the registry override provided for temporary Avast writes since you announced it with 4.6.623. I have not changed it since then.
I’m sure that you know … but just to review:
With release 4.6.623 the Webshield did not conform to use of the override and persisted in using the system defined Windows temporary files directory.
With 4.6.635 the Webshield did conform to the use of the registry override. However, it used either the system defined Windows temporary directory or the directory specified in the registry override directly and did not use the avast sub-directory.
It is clear that there were some changes in the temporary file handling between 4.6.639 and 4.6.467.
My system logs confirm that (at least for my system - Win XP Pro SP2) the changes in the handling of Avast temporary files occurred following the system restart required by the installation of Avast 4.6.467. All temporary file writes following the installation are to the avast sub-directory of the system defined Windows temporary directory.
I have reverted my system to 4.6.639 to confirm some information.
In 4.6.639:
The Webshlock.txt file was created in the system defined Windows temporary directory or, if the registry override (Avast4TempFolder) was present, in the directory specified by the registry override. The sub-directory avast was not used for the Webshlock.txt file.
There were still inconsistencies in the use of the avast sub-directory. This subdirectory was not used by Webshield, its temporary files were written to the directory defined in (1) above.
In 4.6.647:
The Webshlock.txt file is created in a sub-directory avast of the system defined Windows temporary directory. If the registry override (Avast4TempFolder) is present it is ignored.
The Webshield is now consistent in the use of the avast sub-directory. Its temporary files are now written to the avast sub-directory of the system defined Windows temporary directory.
