Author Topic: * NEW PRE-RELEASE UPDATE 5.1.884 NOW AVAILABLE * (Read 89389 times)

scjr · « **Reply #30 on:** January 10, 2011, 05:27:33 PM »

Pre-release .884 (free) is running great here. Windows 7 Ultimate (all updates) and Windows XP SP3 (all updates) are now booting quicker with this release.

Thank you Avast!

scjr

DavidR · « **Reply #31 on:** January 10, 2011, 05:27:45 PM »

Quote from: Brandonn2010 on January 10, 2011, 04:30:04 PM

I'm still using 5.0.677 right now because I had problems with 5.1.864. Will I be able to directly update to 5.1.884 when it's available, or will I have to install the other two updates first, or should I just uninstall Avast! and clean install 5.1.884?

Personally if I had problems with 5.1.864, I would have first tried 5.1.874 to see if that resolved the problem with .864 and give feedback to the developers one way or another on what the problem was and if it was resolved or not. If not I would have then tried 5.1.884, but fortunately I didn't have any issues with 5.1.864.

That is the whole point of using the pre-release versions to see if it fixed your problem and even then you should only have been using the pre-release build if you had problems with 5.1.864, then you should have stuck with it if at all possible.

You don't have to install the interim pre-release builds.

essexboy · « **Reply #32 on:** January 10, 2011, 05:30:17 PM »

Win 7 64bit - no problems as usual

EBPDev · « **Reply #33 on:** January 10, 2011, 05:31:50 PM »

Pre-release update 5.1.884 fix issue from thread http://forum.avast.com/index.php?topic=68805.0 for me.

Thanks

Shoonay · « **Reply #34 on:** January 10, 2011, 05:39:17 PM »

Works fine

CraigB · « **Reply #35 on:** January 10, 2011, 05:39:47 PM »

No problem with this build, is all good for me

GaAs · « **Reply #36 on:** January 10, 2011, 06:17:32 PM »

Hi All.
Hi Avast Team.
We did not! No good!
Explorer freezes when I try to access a folder containing the EXE file.
Exe files are made with QB64 compiler (see http://www.qb64.net), which compiles the source code with "MinGW GCC compiler (see http://www.mingw.org/).
In practice with 5.1.884 I can no longer access the folder.
I am forced to remove the explorer process from task manager.
Explorer goes to reboot and the icons are reloaded (bad).
I tried uninstalling and reinstalling from scratch, but nothing to do!.
I uninstalled the BS, but nothing to do.
Removing avast back to have access to the folder. Install avast and again the problem.
I am forced to reinstall 5.1.874. Let's hope so.
Help me avast team.
Tell me what I do and I have to send.
Now reboot and you do know what happened (reinstall 5.1.874 from scratch).
:'(

GaAs · « **Reply #37 on:** January 10, 2011, 06:36:28 PM »

Quote from: GaAs on January 10, 2011, 06:17:32 PM

Hi All.
Hi Avast Team.
We did not! No good!
Explorer freezes when I try to access a folder containing the EXE file.
Exe files are made with QB64 compiler (see http://www.qb64.net), which compiles the source code with "MinGW GCC compiler (see http://www.mingw.org/).
In practice with 5.1.884 I can no longer access the folder.
I am forced to remove the explorer process from task manager.
Explorer goes to reboot and the icons are reloaded (bad).
I tried uninstalling and reinstalling from scratch, but nothing to do!.
I uninstalled the BS, but nothing to do.
Removing avast back to have access to the folder. Install avast and again the problem.
I am forced to reinstall 5.1.874. Let's hope so.
Help me avast team.
Tell me what I do and I have to send.
Now reboot and you do know what happened (reinstall 5.1.874 from scratch).
:'(

With 5.1.874 Same problem!!
Help! Help!
I try with 5.1.864

igor · « **Reply #38 on:** January 10, 2011, 06:38:08 PM »

Do you mean 5.1.874, or 5.1.884?

GaAs · « **Reply #39 on:** January 10, 2011, 06:43:24 PM »

Quote from: igor on January 10, 2011, 06:38:08 PM

Do you mean 5.1.874, or 5.1.884?

I Igor.
Both, I'm trying them all.
Now I groped with the 664. I do this?

igor · « **Reply #40 on:** January 10, 2011, 06:49:47 PM »

Well, can you pack a few of those executables (with avast! disabled) and upload them to ftp://ftp.avast.com/incoming ?

Also, it may be useful to have a dump of the frozen Explorer.exe - if you could do that. A tool to create the dump is here (the problem is old and unrelated, in your case we'd be interested in Explorer.exe)

jk · « **Reply #41 on:** January 10, 2011, 06:53:11 PM »

AIS 5.1.884 works absolutely fine @ my Win7x64 machine!

well done!

GaAs · « **Reply #42 on:** January 10, 2011, 07:16:06 PM »

Quote from: igor on January 10, 2011, 06:49:47 PM

Well, can you pack a few of those executables (with avast! disabled) and upload them to ftp://ftp.avast.com/incoming ?

Also, it may be useful to have a dump of the frozen Explorer.exe - if you could do that. A tool to create the dump is here (the problem is old and unrelated, in your case we'd be interested in Explorer.exe)

Eureka!! News for You Igor.
I found the cause of the problem.
When the transient cache is active (and persistent cache turned off) the problem occurs.
I then disabled the transient cache and the problem disappeared.
Then I reinstalled the 5.1.884. .... everything ok.
So I guess the problem is really a kind of conflict caused by the transient cache management module (at least on my PC).
The same problem occurred with the jpg image and now I remember that the transient cache was enabled.
This I had reported previously on this forum (File.jpg).
As regards the sending of file.exe, surely I can send them there if you want it.
My collaboration to you is total.
Just give me some specific statements regarding the generation of the dump explorer.(ok ok i see the link...sorry

Thank you very much.

NON · « **Reply #43 on:** January 10, 2011, 07:19:03 PM »

Updated over 5.1.874, no problems so far.

Good build, thanks!

P.S.
I found that compatibility problems (?) with Windows Family Safety seems solved with this build.
Is Web shield's redirect port changed? Now I can't see "localhost:12080" with netstat nor Comodo FW

Kid Shamrock · « **Reply #44 on:** January 10, 2011, 07:23:41 PM »

Confirming 0xC0000005 error I was seeing with Behavior Shield is now fixed!!