Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on September 09, 2006, 12:06:40 AM
-
The update has now been officially released as 4.7.892. You can get it by invoking the "Program Update" feature from within the avast GUI, or downloading the setup packages from www.avast.com. Thanks to everyone who helped testing.
Hi *,
as promised, here's the new (pre-release) version of the upcoming update of avast! Home/Professional. The main feature of this (unofficial) release is added compatibility with Vista RC1.
How to install it: this time, I'm providing direct links to whole setup packages (as for Vista, you need to install it from scratch, as opposed to using the avast program updater; on non-Vista systems, you can use the old aswBeta trick which will give you v4.7.881 as well).
(links removed)
There is a number of fixes in this release. Here's the list of most important changes:
- avast is now compatible with Windows Vista RC1 (but Vista still warns that there are some "compatibility issues" when the main avast scanner is executed - we're working together with MS on removing these warnings; hopefully, by the time the update goes official, we'll have this fixed, too). Also, there are two remaining known problems on Vista: 1) the eicar.com test file is not detected ON EXECUTE (as opposed to on-download, on-open, on-write etc), and 2) avast sounds are not installed
- added back CHM unpacker (and this time, as an added benefit, it should work even in the boot-time scanner)
- fixed a bug that could be causing crash of the scanner on certain UPX packed executable (PLEASE TEST full on-demand scans)
- added a workaround to problems with compatibility with Sunbelt Kerio Personal Firewall (remaints of menus on the screen + seldom hang of avast program on start)
- better detection of ZoneAlarm Pro (to prevent unnecessary WebShield incompatibility warnings)
Any comments on this release are welcome and appreciated!
Thanks
Vlk[/size]
-
Downloading and installing immediatly... 8)
Thanks ;) :)
-
Works fine with Vista RC1 Build 5600.
But the Programm will make a Downgrade when at Autoupdate.
I have Change it to Manuell Check for a New Version of Avast.
Thanks for the great work, I Love Avast.
Sorry for my bad English ;D
-
Are you saying that when you invoke a program update after installing 4.7.881, it downgrades to 4.7.871?
-
I can verify that when the program itself is updated it installs version 4.7.871 and is then blocked due to driver compatibility issues on next reboot.
-
Something's really wrong on my end... I am trying to invoke Beta upgrade on my Windows XP Pro SP2 and all I get is this (spot the version number):
(http://img80.imageshack.us/img80/4715/untitled1rs3.jpg)
And the thing that's even more weird is this:
(http://img235.imageshack.us/img235/6828/untitled2dw0.jpg)
How can it be successfuly updated if it gave me that message about program being up to date just two seconds ago ???
Of course when I restart my PC, after loging into Windows, avast! is still at the same version... no sign of the new one.
-
I finally managed to upgrade it to the new beta version (by downloading the whole package)... but after I manually tried to invoke Program update, this is what happened:
(http://img56.imageshack.us/img56/9618/untitled3tu2.jpg)
It really downgrades... :-\
-
I've got the new one both in XP and Vista without trouble... ::)
I'm not used to be the lucky guy... What do I do when I'm lucky? ;D
Tested:
1. Key addition... perfectly.
2. Introdutory Help dismiss... perfectly.
3. Skins download and apply... perfectly.
4. Boot time scanning... perfectly (just that on Vista it is not as the same 'blue' in background as in XP) ;D
5. Using more than one language... ok.
6.
... Well, except for the 'first' warning message, that I've chosen to 'run' the program and does not warn me more, perfectly 8)
-
Try manually to update avast! and it will go back to the old version.
-
Try manually to update avast! and it will go back to the old version.
No, it just does not update :-\ :'(
-
Just to confirm regarding ashSimpl.exe crashing issue I posted about in this thread:
http://forum.avast.com/index.php?topic=23280.0
I just scanned my whole system, 4 partitions, total of 120 Gb of data scanned, thorough scan method used, and it took approximatelly around 3 and a half hours.
I am happy to confirm that ashSimpl.exe does NOT crash on my system any more. I am just waiting to see if Alwil guys will solve these issues with updates and downgrades.
Great work guys !
-
Good morning,
I can verify that when the program itself is updated it installs version 4.7.871 and is then blocked due to driver compatibility issues on next reboot.
Yeah, sorry, that was my bad - but very easily remedied, all I needed to do is swap the servers.def file on our updating server.
Sorry for the troubles.
Vlk
-
If I am not having problems of any sort, shouldn't I wait until the program updates itself?
It will automatically update when version 4.7.881 is released won't it ???
RoRo 8)
-
No problems testing with Windows Vista RC1.
The only thing that I noticed is that the icon is not animated when a VRDB is generated.
-
Windows Vista 5600x64 RC1:
"Function setifaceUpdatePackages() has failed. Return code is 0x2000000A, dwRes is 2000000A."
-
Good morning,
I can verify that when the program itself is updated it installs version 4.7.871 and is then blocked due to driver compatibility issues on next reboot.
Yeah, sorry, that was my bad - but very easily remedied, all I needed to do is swap the servers.def file on our updating server.
Sorry for the troubles.
Vlk
Just tried upgrading again and it's not fixed. Still 4.7.871 which doesn't work.
-
Just tried upgrading again and it's not fixed. Still 4.7.871 which doesn't work.
Once you have 871, there's no way back to 881.
What was fixed is that once you have 881, it won't go back to 871 anymore.
It IS fixed as far as I can tell...
Hope this helps,
Vlk
-
Function setifaceUpdatePackages() has failed. Return code is 0x2000000A, dwRes is 2000000A."
That can sometimes happen even when using other OS. It means "another instance of the updater is already running" -- meaning, for example, that you invoked a manual update during the execution of an auto-update.
Avast limits concurrency of the update process, i.e. there can be only one instance of the updater running at a time...
Hope this helps,
Vlk
-
Just tried upgrading again and it's not fixed. Still 4.7.871 which doesn't work.
Once you have 871, there's no way back to 881.
What was fixed is that once you have 881, it won't go back to 871 anymore.
It IS fixed as far as I can tell...
Hope this helps,
Vlk
Unfortunatelly that's still not true VLK... it still doesn't work. See my screenshot. There is your reply in the background ad pay attention to the program versions...
(http://img208.imageshack.us/img208/7472/untitled1gg2.jpg)
-
Did you try just now?
-
I will, screenshot I posted was taken few minutes ago... I will try again if that changes anything.
EDIT: Have to reboot first after this downgrade...
-
Did you download the installers again for this installation?
There seems to be a wrong servers.def file in the package (the official one, not the beta one - making to program to go to the official version during the update). It's not really a problem in the program itself, but it certainly should be fixed, of course.
-
I have the same problem, just installed 881 did a manual update and it was back to 871. :-\
I downloaded this today, aprox 2 hrs ago. ???
-
Here is my timeline, I placed a system clock for easier understanding of time line:
(http://img217.imageshack.us/img217/6353/2oh4.jpg)
(http://img235.imageshack.us/img235/834/3fv2.jpg)
(http://img64.imageshack.us/img64/1752/4bq8.jpg)
Quote by Igor:
Did you download the installers again for this installation?
Well, I downloaded it yesterday... I guess I have to do that again ?
-
Igor, I just downloaded whole beta installation again, did an upgrade, rebooted and when I invoked manual program update, it went back to the old version.
-
Good morning,
I can verify that when the program itself is updated it installs version 4.7.871 and is then blocked due to driver compatibility issues on next reboot.
Yeah, sorry, that was my bad - but very easily remedied, all I needed to do is swap the servers.def file on our updating server.
Sorry for the troubles.
Vlk
When this says that Avast will work on RC1, I will install it, not before that. Not with a Virus program.
http://www.avast.com/eng/avast-antivirus-and-windows-vista.html
-
OK, I guess we'll have to wait for Vlk to fix the updating for real.
-
I think that the problem is in the servers.def file in the setup file for Vista.
Probably only download1.avast.com should have been defined in there, whereas now download1 until download71.avast.com are defined.
-
When this says that Avast will work on RC1, I will install it, not before that. Not with a Virus program.
http://www.avast.com/eng/avast-antivirus-and-windows-vista.html
This is beta testing and you have to understand that Vista is not a public release it's just Release Candidate. It's not like it's final gold version. No one forces anyone to try it. Alwil is giving their best to fix this issue, so little patience is always welcome.
Also, avast! is not a Virus program, it is an anti-Virus program. ;)
Oh yes, Welcome to forums Gary66
-
I think that the problem is in the servers.def file in the setup file for Vista.
Probably only download1.avast.com should have been defined in there, whereas now download1 until download71.avast.com are defined.
The problem is that I didn't even try to install avast! for Vista yet. All these problems with downgrading to the previous version after 881 is already installed, occured on Windows XP. See those windows and their style. It's not Vista, it's XP with Royale theme.
But I believe that similar problem happens on Vista too.
-
Hmm, OK, I thought it wouldn't be necessary to regenerate the setup packages, just to replace the servers.def file on the server.
However, it doesn't seem to be the case... this is because the servers.def that's in the setup program forces the updater to immediately get back to the release stream.
Oh well, I'll have to regenerate the whole thing then, this will take about 30 minutes...
I will be back ;)
Cheers
Vlk
-
Thanks Ondrej ! Do not rush, nothing comes good out of rushing things. We have enough time, besides it's weekend, enjoy it a little bit ! ;)
-
The links in my first post should now finally point to the correct setup programs (sorry for the confusion).
Thanks
Vlk
-
Thanks Vlk !
I'm already on it... ;)
-
Confirmed !
Working great this time. I used new Beta installation for avast! Home Edition. Can't check the one for Pro since I don't have it installed, but Home versions works perfect. Once you install new beta 881 there is no going back to previous one by manually updating the program.
Thanks VLK and Alwil !
-
I can verify that it is working with the update function now.
-
Beta 4.7.881 is working great on our old win95 computer. Thanks! :D
-
With Windows Vista RC1, the icon does not animate when a VRDB is generated.
I just mention it again, because I don't see it indicated at the known issues with Vista.
-
Sweet Playa!
This seems to be working for me. Updates and errthing. I need to see if the key will work now.
I'm happy to be back with Avast!
-Jazhawk
-
BSOD at Windows XP SP2+ in VMWare Server.
avast beta version 4.7.881
I had to uninstall in Safe Mode :-[
-
Well I installed this on Vista RC1 5600 and I still get an error that it is not compatible. I clicked ignore and it installed. On the restart it tried to scan my PC and a great many files showed no access errors. When it finally rebooted Avast would not start. I am done with this untill it goes gold, I went back to Trend Micro. It works.
-
Well I installed this on Vista RC1 5600 and I still get an error that it is not compatible. I clicked ignore and it installed.
This worked for me... On VMWare Server (virtual installation).
On the restart it tried to scan my PC and a great many files showed no access errors.
Do you mean boot time scanning?
When it finally rebooted Avast would not start. I am done with this untill it goes gold, I went back to Trend Micro. It works.
Can you check Windows Events or avast logs to see if there are any important info to help debbug this problem? Thanks.
-
BSOD at Windows XP SP2+ in VMWare Server.
avast beta version 4.7.881
I had to uninstall in Safe Mode :-[
Uninstall + aswclear.exe
Installing 4.7.881 (not updating from 4.7.871).
Worked 8)
-
Hi *,
as promised, here's the new (pre-release) version of the upcoming update of avast! Home/Professional. The main feature of this (unofficial) release is added compatibility with Vista RC1.
How to install it: this time, I'm providing direct links to whole setup packages (as for Vista, you need to install it from scratch, as opposed to using the avast program updater; on non-Vista systems, you can use the old aswBeta trick which will give you v4.7.881 as well).
Works just fine here, installed avast! 4.7.881 on Sept 08, no problems at all on Vista 5600. ;D
Avast! Home (English): http://files.avast.com/files/beta/4.7.881/setupeng.exe (~11MB)
Avast! Professional (English): http://files.avast.com/files/beta/4.7.881/setupengpro.exe (~11MB)
Avast! Home (multilingual): http://files.avast.com/files/beta/4.7.881/setupful.exe (~40MB)
Avast! Professional (multilingual): http://files.avast.com/files/beta/4.7.881/setupfulpro.exe (~40MB)
There is a number of fixes in this release. Here's the list of most important changes:
- avast is now compatible with Windows Vista RC1 (but Vista still warns that there are some "compatibility issues" when the main avast scanner is executed - we're working together with MS on removing these warnings; hopefully, by the time the update goes official, we'll have this fixed, too). Also, there are two remaining known problems on Vista: 1) the eicar.com test file is not detected ON EXECUTE (as opposed to on-download, on-open, on-write etc), and 2) avast sounds are not installed
- added back CHM unpacker (and this time, as an added benefit, it should work even in the boot-time scanner)
- fixed a bug that could be causing crash of the scanner on certain UPX packed executable (PLEASE TEST full on-demand scans)
- added a workaround to problems with compatibility with Sunbelt Kerio Personal Firewall (remaints of menus on the screen + seldom hang of avast program on start)
- better detection of ZoneAlarm Pro (to prevent unnecessary WebShield incompatibility warnings)
Any comments on this release are welcome and appreciated!
Thanks
Vlk
Installed on Vista 5600, no problems At ALL!!! ;D
-
BSOD at Windows XP SP2+ in VMWare Server.
avast beta version 4.7.881
This is what happens when the engine DLLs are updated, but the core device driver (AavmKer4.sys) is NOT. I'm aware of the issue - although under normal circumstances, the version mismatch should never happen.
I guess we will add some extra checks to the new version so that the BSOD never happens. The version mismatch is not a fatal problem for avast (i.e. it can work even if in this case, it just needs to know about it).
Cheers
Vlk
-
I guess we will add some extra checks to the new version so that the BSOD never happens. The version mismatch is not a fatal problem for avast (i.e. it can work even if in this case, it just needs to know about it).
Even it's not a fatal problem to avast, it is for Windows... There is nothing to do after the BSOD...
Anyway, installed on Vista 5600, no problems at all 8)
-
Installed on Vista RC1 with no problem whatsoever
Just some awkward things, like the UAC kicking in after you click update on the icon in the system tray and not when you click update now in the program settings. I would expected this behaviour perhaps while accessing the settings screen but not here.
I know this is to get it working on Vista RC1, but still ;D
-
I have to say that Avast is awesome :) and works great on Windows Vista RC1 ;D. I don't think I will go to a different Antivirus program.
-
I am getting indications from Internet Mail and Outlook Exchange that "The provider is waiting for a sub-system to start". Has anyone seen this on Vista RC1? Otherwise Avast appears to be runnnig normally.
-
I am getting indications from Internet Mail and Outlook Exchange that "The provider is waiting for a sub-system to start". Has anyone seen this on Vista RC1? Otherwise Avast appears to be runnnig normally.
Which is your email program?
Here is described these behaviors/situations: http://forum.avast.com/index.php?topic=23460.0
-
Just a quick "THANK YOU!" for this beta update. I installed it on a clean install of Vista RC1, Build 5600 & performed a quick scan & it seems to be working beautifully.
~Dave
-
Just a quick "THANK YOU!" for this beta update. I installed it on a clean install of Vista RC1, Build 5600 & performed a quick scan & it seems to be working beautifully.
Welcome Dave...
Don't stop your 'thanking' only to this post... help the others and get help in the best antivirus forum 8)
-
Any expected release date?
-
I see that the current VPS is 0637-0. At the beta server it is still 0636-3.
Assume that the propagation to the beta server has failed!
-
I see that the current VPS is 0637-0. At the beta server it is still 0636-3.
Assume that the propagation to the beta server has failed!
Seems to be fixed no -- sorry for the inconvenience... :)
-
Any expected release date?
Next week is my estimate. There will be at least one more beta refresh with some more bugs fixed (probably later this week).
-
installt on rc1 5600 x86 german
i can`t change skins.
in the attachment you can see the message.
thx
-
It's a problem with IE7... should be fixed in the next beta refresh.
-
:) thx
-
I did the update and now Avast quit working. Worked great for a week or so on RC1 but it's failing to load. I got that red/white beachball now. Looks like I'm headed back to AVG, kicking and screaming.
I guess since I'm using the free version I shouldn't sound impatent but this isn't mission critical behavior.
-Jazhawk
-
Great software you guys! Please keep up the good work, for ever :)
Nothing but the best...
-
well well wellll...
i had problem with key,now i wana test 881 maybe it fix my problem before install new Winxp
Thank you for everything :)
-
i had problem with key
Which key? Which problem?
-
i had problem with key
If you were using a pirated avast Pro key, it stopped working by intention. During the Friday VPS update, there has been a big ban of MANY pirated keys. ;)
-
Hi guys,
it is my pleasure to annouce that we have now updated the 4.7.881 version to 4.7.883. The 883 build can be reached either by invoking a regular program update in 4.7.881 or by using aswBeta.exe or by downloading the whole setup packages using the links in the first post of this thread (i.e. same URL's as were used for build 881).
Changes from build 881:
- Vista now shouldn't warn about avast not being incompatible
- the VRDB icon should now be working (spinning) under Vista
- the skins should now install correctly (IE7 and/or Vista problem)
- no more bluescreens in case of driver/dll version mismatch (Technical's post above)
- engine startup time was slightly improved in this build
Also, this build includes two new language packs, Swedish and Slovenian! If you want to try these out, update to 883 and go to the Languages page in the program settings (and use the Install new languages option) or (if installing from scratch) use the following URL's to download the localized versions:
Avast! Home (Swedish): http://files.avast.com/files/beta/4.7.881/setupswe.exe (~11MB)
Avast! Professional (Swedish): http://files.avast.com/files/beta/4.7.881/setupswepro.exe (~11MB)
Avast! Home (Slovenian): http://files.avast.com/files/beta/4.7.881/setupslo.exe (~11MB)
Avast! Professional (Slovenian): http://files.avast.com/files/beta/4.7.881/setupslopro.exe (~11MB)
(please note that it is NOT possible to use these setup packages if you already have a previous version (e.g. English) of avast installed - You should either reinstall or use the procedure described above).
Any comments are welcome and appreciated.
Thanks :)
Vlk
-
I can confirm that the following two issues with Windows Vista are now solved:
Vista now shouldn't warn about avast not being incompatible
The VRDB icon should now be working (spinning) under Vista
After the upgrade from 4.7.881 to 4.7.883 I got a BSOD.
The reboot thereafter went ok. I will send the minidump to Vlk.
-
i had problem with key
If you were using a pirated avast Pro key, it stopped working by intention. During the Friday VPS update, there has been a big ban of MANY pirated keys. ;)
Yes i had a Pirate key but now i removed and i wana use 881 or 883 but after update it still don't connect to server: http://www2.avast.com/beta
:-\ what should i do ?
-
Yes i had a Pirate key but now i removed and i wana use 881 or 883 but after update it still don't connect to server: http://www2.avast.com/beta
Well, you need to insert a valid key, of course... ;)
-
If you were using a pirated avast Pro key, it stopped working by intention. During the Friday VPS update, there has been a big ban of MANY pirated keys. ;)
Congratulations. I wish you do this more frequently 8)
-
thanks a lot :) am going to install Vista RC 1 tomorrow. lemme try this beta version of the AV which i always trust :)
-
Just wanted to say thanks to VLK for kicking ass on getting this working for RC1.. I have been trying for 3 days until i read all the way to this page... Excellent work, excellent product... AVAST! Stomps a Mud HOLE in everyone else.... ;) ;D
-
Also, this build includes two new language packs, Swedish
This sounds GREAT! ;D
Can I use this beta on my WinXP-computer, or is it just for Vista?
-
It's for all supported systems, i.e. from Windows 95 till Vista 64 bit ;)
-
??? ???
ashEnhcd.exe of 4.7.883 incompatible?
-
Hi, I am getting event log each boot with 4.7.883. This is a fresh install of Vista 32bit RC1 Build 5600 and Avast Pro downloaded 8 hours ago. I assume it is just a warning that can be ignored?
Log Name: Application
Source: Microsoft-Windows-ApplicationExperienceInfrastructure
Date: 16/09/2006 8:49:10 AM
Event ID: 1
Task Category: None
Level: Warning
Keywords:
User: max\Ian
Computer: max
Description:
The application (avast! Antivirus, from vendor ALWIL Software) has the following problem: avast! Antivirus has a known compatibility issue with this version of Windows. For an update that is compatible with this version of Windows, contact ALWIL Software.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-ApplicationExperienceInfrastructure" Guid="{5ec13d8e-4b3f-422e-a7e7-3121a1d90c7a}" />
<EventID>1</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>2</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2006-09-15T22:49:10.673Z" />
<EventRecordID>330</EventRecordID>
<Correlation />
<Execution ProcessID="1220" ThreadID="3888" />
<Channel>Application</Channel>
<Computer>max</Computer>
<Security UserID="S-1-5-21-727528356-1226156807-2932157471-1000" />
</System>
<EventData>
<Data Name="DBType">15</Data>
<Data Name="AppNameCount">17</Data>
<Data Name="AppName">avast! Antivirus</Data>
<Data Name="VendorNameCount">15</Data>
<Data Name="VendorName">ALWIL Software</Data>
<Data Name="SummaryCount">166</Data>
<Data Name="Summary">avast! Antivirus has a known compatibility issue with this version of Windows. For an update that is compatible with this version of Windows, contact ALWIL Software.</Data>
<Data Name="SessionID">1</Data>
</EventData>
</Event>
-
It's for all supported systems, i.e. from Windows 95 till Vista 64 bit ;)
GREAT...I will test the beta ASAP! :)
-
ashEnhcd.exe of 4.7.883 incompatible?
Any news about this? ::)
-
You can ignore any "not compatible with Vista" prompts, they will not be present in Vista RTM.
-
Sorry guys, I'll dive little off topic, even though Vista topic is off-topic itself ;D (the name of this thread has nothing to do with Vista, so I guess I can ask something regarding XP).
Anyway, after the last avast! update (which was today I believe, at least avast! announced some change and I had to reboot) I'm having some troubles... Comodo Firewall is alarming me about ashServ.exe every single time I reboot my computer and log in to Windows again. I have that checkbox checked all the time (to remember my choice next time) and I really don't have problems with other applications and Comodo not remembering the settings...
(http://img228.imageshack.us/img228/5930/untitled1pk0.jpg)
-
Thats normal I think its because everytime it must be connecting to a different server ;)
Please tell me if I'm wrong.
Al968
-
Well I'm sorry but I don't think this is normal behaviour. For the last 3 years I have never had problem like this, and certainly Comodo should remember my choice if I "told" it to remember. Unless, avast! is constantly changing something in its settings every time you reset your system.
Any thoughts Alwil ?
-
Well I'm sorry but I don't think this is normal behaviour. For the last 3 years I have never had problem like this, and certainly Comodo should remember my choice if I "told" it to remember. Unless, avast! is constantly changing something in its settings every time you reset your system.
]
As a workaround, because I don't know why Comodo is doing that and if avast.setup is being changed in someway, as a workaround, you can make avast.setup as a trusted application in Comodo. If the parent application changes, I mean, if you update from the icon, ashdisp.exe will be the parent, or ashSimpl.exe or ashEnhcd.exe or ashupd.exe ...
-
I don't know why comodo is flagging ashServ.exe as the parent of avast.setup, I thought that ashUpdSv.exe was the calling/initiating program for avast.setup and as such the parent.
I have similar stuff on Outpost Pro (hidden process) when a program launches another and I have to authorise that program.
Perhaps we are seeing a similar issue to ZA where it forgets the permissions, etc. and deletion of the entry for avast.setup followed by a manual update might do the trick.
But, like Tech said the parent could change and on boot seems a strange time to be alerted as at that point there shouldn't have been a change of avast.setup. In theory it shouldn't exist at that time until a connection is established (auto connect broadband, etc.) and ashUpdSv.exe checks for updates and if there avast.setup would need to be created. So I'm just as confused as you are.
-
Hmmm... and funny thing is I have exactly the same program set on my laptop as I do on my desktop machine. Never ever experienced this on my laptop, not a single time, but I've noticed it started to happen on my desktop since yesterday after that last avast! update. Desktop is AMD and laptop is Intel, but that shouldn't make any difference anyway. I just mentioned it for camparision reasons. Comodo latest version on both, and avast! Home Edition with different serial keys on both machines too.
Cheers !
P.S. I will try to completely clean Comodo's permissions for avast! and see what happens.
-
Comodo latest version on both, and avast! Home Edition with different serial keys on both machines too.
Sasha, is your alert level set to High? On both computers?
-
No, it's set to low (on both machines)... I want as less annoying messages as possible.
-
Hi, new to Avast, been a zone Alarm Security Suite person up till now, but as I'm trying out RC1, you were recommended to me.
Using the latest version 4.7.883. (pro)
All installed perfectly and runs OK, but I have one small problem. I'm running Thunderbird mail, and it takes a lot longer to download my emails with Avast running. That I can put up with.
But I subscribe to a few mail groups and I delete a lot of emails a day. With Avast disabled, I can keep clicking the delete button and my emails instantly go to the deleted folder. With Avast running, it takes around 20 secs to delete each email.
I initially tried to think logically and thought maybe because I'm deleting unread emails, Avast is checking each email as when I click on the delete button, the next unread email appears in the message window. But I tried with `read` emails and it still takes forever to delete them.
I have all my protection set to high as I want good protection, but have I set something wrong, is there a bug (I realise this is beta), I cant see why after email has been downloaded (and presumably virus checked) simply deleting an email wound cause so much hassle?
Thanks
Phil
AMD Athlon 64 3400+
Vista RC1 5600 64 bit
Asus K8V MB
2GB Ram
Geforce 6800 GT 256MB
Over 200GB free space (SATA)
X-FI sound card
-
High level is useful if you are suspecting that your computer is not OK, almost all files are scanned and almost all packed files are unpacked, this helps in investigating of potential problems but also consume a lot of resources. Standard level (at least for standard shield) is enough.
In your case is probably unpacked and scanned Thunderbird's mailbox file everytime you delete something in it.
-
Hello for all.
Already they know when will be launched the new version?
The avast is very good.
-
pjo123
I am using the latest avast beta update and Thunderbird 1.5.0.7.
I am experiencing no slowdown in receiving mail or deleting mail.
I would be fairly certain that your problem is with Thunderbird. Thunderbird does not handle file space very well and it requires that its users take care of it.
When you delete a mail message in any avast folder it is not deleted at all, it is simply flagged to be not displayed any more, but it is still there and the folder just gets bigger and bigger. It is also copied to the trash folder (which gets bigger and bigger). So it is important to empty the trash folder too.
The only way to really delete mail messages in Thunderbird and to get control of the space it is using is to regularly compact the folders. (If you check the Thunderbird support forums you will find the folks there giving this advice to many of the problem reports).
It is also not a good idea to keep all you mail messages in the Inbox, if you have a lot there consider moving them to another folder.
There is an option in Thunderbird (Tools > Options > Advanced > Offline & Diskspace tab) to have Thunderbird compact folders. I use an extension called Xpunge which provides a combined trash emptying and compacting function.
Bottom line - I think you will see a considerable improvement if you empty the trash folders and then compact all your folders. If you care to search this forum using the keywords Thunderbird and compact you will find quite a few others have.
-
Thanks all of you.
Have reduced the internet mail and the standard shield to normal, this has solved all my problems,
I'm also using Thunderbird 1.5.07 and have various folders instead of using the inbox. I wasn't aware the files weren't removed from the folders when I delete them (I knew they went into the deleted folder), i did compact my folders every few months but will now do it weekly.
Many thanks
Looks like you have a new customer.
Phil (although I don't like the way that buying it in UK Pounds works out more expensive than buying it in US $ and having my credit card company use current exchange rates)
-
Seems I've missed BETA start... So this time I'll wait for final version... But seems it was one of the interesting BETAS ;D
-
1. This build will be automatically updated from 871?
2. When it will be released?
-
1. Yes, once the beta is over and this is released officially it will be updated through the auto updates, the cycle is between 1 - 7 days to ease server load for program updates.
2. That depends on any issues being ironed out but it was mentioned it might be this week, but that is obviously subject to change as there is no fixed deadline and it is better to get it right than to get it out. Keep monitoring the forums because this is where you will hear about it first.
-
Vista RC1, 32bit on both of my laptops (Thinkpad X60s, Vaio UX17), this has happend two or three times during the last few days:
Faulting application ashDisp.exe, version 5.0.0.0, time stamp 0x4506e844, faulting module browseui.dll, version 6.0.5600.16384, time stamp 0x44f5577a, exception code 0xc0000005, fault offset 0x0003ad5f, process id 0x594, application start time 0x01c6dcccaa6e810d.
-
Another catch from a Vista application event log:
- System
- Provider
[ Name] Microsoft-Windows-Security-Auditing
[ Guid] {54849625-5478-4994-a5ba-3e3b0328c30d}
EventID 5038
Version 0
Level 0
Task 12290
Opcode 0
Keywords 0x8010000000000000
- TimeCreated
[ SystemTime] 2006-09-20T16:13:52.061Z
EventRecordID 2597
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 68
Channel Security
Computer dd-X60s
Security
- EventData
param1 \Device\HarddiskVolume2\Windows\System32\drivers\aswmon2.sys
-
The faulting module is the more important issue here browseui.dll, which isn't a part of avast it just happens that avast happens to be using it. Although I can't understand why ashDisp would want/need to use this module what were you doing at the time ?
http://www.liutilities.com/products/wintaskspro/dlllibrary/browseui/
Description:
browseui.dll is a component that contains functions and resources for browser UI management.
and
Description Browseui.dll is used by windows to talk to shell browser interface.
-
The faulting module is the more important issue here browseui.dll, which isn't a part of avast it just happens that avast happens to be using it. Although I can't understand why ashDisp would want/need to use this module what were you doing at the time ?
http://www.liutilities.com/products/wintaskspro/dlllibrary/browseui/
Description:
browseui.dll is a component that contains functions and resources for browser UI management.
and
Description Browseui.dll is used by windows to talk to shell browser interface.
last time it happend just after having changed some settings in "avast settings..." and pressed the "OK" button. i can easily reproduce his.
-
It may be because the ashDisp.exe uses IE to display the settings window, which is the only reason I can thing of that ashDisp might need to have any interaction with browser interface. That would have to be confirmed by one of the Alwil team but, it still doesn't get past the faulting module was browseui.dll.
-
It may be because the ashDisp.exe uses IE to display the settings window, which is the only reason I can thing of that ashDisp might need to have any interaction with browser interface. That would have to be confirmed by one of the Alwil team but, it still doesn't get past the faulting module was browseui.dll.
as i said, i see this on both of my laptops running vista. it's not a big deal, because you can easily get the gui component back by starting ashDisp.exe from the install directory.
-
The last refresh of the beta has now been released. It has a version number of 4.7.887.
To install it, either invoke a program update from an already installed beta version (4.7.881 or 883) or use the links given in the first post of this thread (the URLs have not changed).
I'd be grateful if you could try to simulate any outstanding issues you have had with builds 871/881/883 and report if this new build has any effect.
If everything goes well, the update will be officially released on Friday.
Cheers
Vlk
-
Nice to hear ;D I think it's not to late to get to the BETA train, as I've read all post, and know what problems were. So, going to download latest, and maybe the last BETA this time. ;)
-
Hello,
I have to problems, and hope that you can help me.. First I have Vista RC1 on my computer and avast 4.7.883. yesterday I got a message that avast antivirus reports that might be out of date.. How I can solve this problem and where I can download 4.7.887 version.
Another problem is my mail on Vista.. I have Thunderbird 1.5.0.5 and I cant receive my mail from servers message is Failed to connect mail server.. I check with my IP and everything is OK.. same is with Gmail.. any solution?
Thanks.
-
I resolve one problem. Update My avast 4.7.887. and it works great.. Thanks..
I have another one with mail mail.. I cant download it from server.. Anybody had a same problem?
-
Can you send email ?
Before trying to faultfind on a problem, the latest version of thunderbird is I believe 1.5.0.7.
-
The last refresh of the beta has now been released. It has a version number of 4.7.887.
To install it, either invoke a program update from an already installed beta version (4.7.881 or 883) or use the links given in the first post of this thread (the URLs have not changed).
...
...
...
Except it still says http://files.avast.com/files/beta/4.7.881/setupeng.exe inside the link name.
Maybe it would be a good idea to change that too because for example...
I have no clue for what reason, but sometimes forum won't inform me about new replies in this thread even though I am subscribed and I'm watching this thread. Sometimes, have not much time to go through all new posts and replies and I just check first page to see if there is something new. Since I don't see anything changed inside those links (on first eye sight) I simply leave this thread.
I also had some troubles with 883 on Vista since this morning. Security center alarmed me that VPS is out of date or my Virus protection is outdated or something like that. I wasn't able to update to new version which is now I see, version 4.7.887. I tried manual update and it wouldn't work, so I thought there is nothing new.
I am downloading this new version to see what happens after. But as I said it would be good to change those link names every time you change update link.
Thanks in advance!
-
The last refresh of the beta has now been released. It has a version number of 4.7.887.
To install it, either invoke a program update from an already installed beta version (4.7.881 or 883) or use the links given in the first post of this thread (the URLs have not changed).
I'd be grateful if you could try to simulate any outstanding issues you have had with builds 871/881/883 and report if this new build has any effect.
If everything goes well, the update will be officially released on Friday.
Cheers
Vlk
If my Avast isn't a beta one, the update won't work, that's it?
With official version released the update will upgrade to RC1 compatible version by itself?
-
If my Avast isn't a beta one, the update won't work, that's it?
Yes. You need to download the beta in this case.
With official version released the update will upgrade to RC1 compatible version by itself?
It should.
Right now, you can't upgrade to beta or you can use the ashbeta.exe tool to go from the official to beta. It won't work for Vista because you need to install from the scratch.
-
Just one issue: my Avast, due to incompatibility with Windows Vista RC1, apparently is not updating automaticaly. I right-clicked the "a" logo at taskbar, then "Updating", then "Program Update" but an error message appeared and the program couldn't update... How the compatible version of Avast will then be installed?
-
Just one issue: my Avast, due to incompatibility with Windows Vista RC1, apparently is not updating automaticaly. I right-clicked the "a" logo at taskbar, then "Updating", then "Program Update" but an error message appeared and the program couldn't update... How the compatible version of Avast will then be installed?
What version do you have of Avast? You can update to the latest beta (thru the update-feature in Avast) .887 if you already have beta .881 or .883 installed, otherwise, you must install the beta from scratch.
What does the error message say?
The latest official version of Avast is 4.7.871, and you can't update to the beta with the update-feature in Avast, if you have 4.7.871 installed.
-
I got v4.7.871... Do I need to install the beta version anyway? My current version do not upgrade to compatible version?
If positive, do I need to uninstall this version and install the beta one or could I install over current version?
Could you please send to me the download link?
-
By the way, I do not need beta version, I prefer the official release... So, my current 871 version will be updated to new final version or even to final one I need to install first one beta version?
-
By the way, I do not need beta version, I prefer the official release... So, my current 871 version will be updated to new final version or even to final one I need to install first one beta version?
I also prefer the official release, so I don't install the beta, I will wait for the next official release. 4.7.871 is working just fine here, so I will stick to this version some more days.
When the new official version is released, you can use the update-feature in Avast and update to the latest version.
I think we will have a new release really soon.
Edit: I was interested to install the beta as it has the swedish language, I wanted to test that as swedish is my native language, but I will wait for the official release.
-
Yes, that's also my idea...
-
Just one issue: my Avast, due to incompatibility with Windows Vista RC1, apparently is not updating automaticaly. I right-clicked the "a" logo at taskbar, then "Updating", then "Program Update" but an error message appeared and the program couldn't update... How the compatible version of Avast will then be installed?
It's not a problem of this avast version or of this beta.
Vista handles updates/access rights differently than XP.
Final avast verstion for Vista will have this (or improved) feature ;)
I got v4.7.871... Do I need to install the beta version anyway? My current version do not upgrade to compatible version?
Install the last beta and the compatibility issues will be gone. Remember, this was generated by Vista RC1 and NOT avast.
The beta is a workaround to solve Vista problems. The new Vista version, probably, will have this issue corrected.
If positive, do I need to uninstall this version and install the beta one or could I install over current version?
Do not upgrade or reinstall.
Better and safer is download the last beta, uninstall, boot, install the last beta, boot :)
Could you please send to me the download link?
http://forum.avast.com/index.php?topic=23424.msg193183#msg193183 (disregard the version numbers as the new exe files was overwritten by the last beta version).
By the way, I do not need beta version, I prefer the official release... So, my current 871 version will be updated to new final version or even to final one I need to install first one beta version?
You don't need to use or install the beta to get the last official release.
-
Vlk,
You guys rock! Thanks.
Steve
--using Vista (build 5600) and Avast (4.7.887)
-
Any news about the official version (not beta) for WinVista RC1?
-
Any news about the official version (not beta) for WinVista RC1?
Well, the point is not a new official avast (not beta) for Vista but, on contrary, a new Vista.
There won't be an official release of avast to Vista RC1 5600. Vista has the incompatibility problem.
There is a new Vista (5728.16387.060917-1430) and it has other problems with avast (http://forum.avast.com/index.php?topic=23758.msg195724#msg195724) :P
-
The message from forum that you sent says "The new (Vista-compatible) avast is JUST being released so it's not really a beta anymore." so will or will not there an official release? What do I do? Install the 887? Wait a few more for the official release?
-
Wait a few more for the official release?
You ALREADY can update to the new version (4.7.892).
-
As some of you already pointed out, the update has now been official released. The version number of the official build is 4.7.892.
Thanks to everyone who helped testing!