Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on April 11, 2008, 12:08:19 AM
-
The update has now been officially released as v4.8.1195. Thanks to everyone who helped testing.
Hi *,
here I'm again. A service update for avast Home/Pro is coming soon (my guess is in about 1-2 weeks) and as usual, it's my pleasure to announce the availability of a pre-release version of this update.
How to install it:
In case you already have avast 4.7/4.8 installed on your system:
1. NEW! go to avast settings, and on the Troubleshooting page, disable the avast self-defense module (this is NECESSARY for the update to complete successfully)
2. download and run the following program: LINK REMOVED
3. after it completes, re-enable self-defense module (disabled in step 1.)
That's about all it takes (provided you have a previous version of avast Home/Pro already installed, of course).
If you don't have the previous version installed, or would prefer to do a clean install (which, in some more serious cases, may be necessary), we have also prepared the full installation packages (setup files). These can be downloaded from the following locations:
LINK REMOVED (Home Edition, English version) ~21MB
LINK REMOVED (Professional Edition, English version) ~21MB
LINK REMOVED (Home Edition, all languages) ~59MB
LINK REMOVED (Professional Edition, all languages) ~59MB
If your current installation of avast stopped working (and/or cannot be uninstalled), we recommend the following procedure to install this new build from scratch:
1. boot into Windows Safe Mode
2. use aswClear.exe (http://www.avast.com/eng/avast-uninstall-utility.html) to remove any existing avast installation (or remaints of it)
3. boot back into normal Windows mode and use the above mentioned setup packages to install the new version
There is a number of fixes in this release. Here's an (incomplete) list:
- solved incompatibility of the avast self protection module and the System Restore feature (Windows XP/Vista)
- solved keyboard/mouse lags in some games (e.g. World of Warcraft)
- "Quick" scan now quick again (in the previous version, it was usually slower than "Normal" scan)
- fixed deleting of infected files in some nested archives
- shell extension: under Windows Vista, shortcut targets are now correctly scanned
- boot-time scanner now correctly displays warning messages about corrupted archives
- improved scanning speed in the Simple user interface
- improved handling of scan exceptions
- self protection: improved detection of changes in the INI file
- start of the "avast! Mail Scanner" service should now be fast again
- fixed a problem with avast being installed in a directory with name containing non-Latin characters
- fixed entering of the license key (didn't work in certain configurations)
- improved detection/healing of MBR rootkits
- avast can now correctly handle the case when the INI file is missing/corrupted
- the "Disable startup rootkit scan" option on the Troubleshooting page now effective (in the previous version, it was ignored)
- messages from Internet Mail (on e-mails being sent/received) should now correctly decode the most common character encodings
- fixed possible boot-time scanner crash at the end of the scan
- fixed problems with the boot-time scanner on FAT[32] partitions
- Standard and Thorough scan in the Simple User Interface should now scan System Volume Information folder again, provided it's started from an Administrator account
- fixed the message announcing the license key going to expire soon
- added support for Azureus Vuze and Qtrax in P2P Shield
- small improvements in some unpackers (WinExec, RAR, CHM)
edit May 7: the program has now been updated to build 4.8.1192.
Any comments on this release are welcome and appreciated!
Thanks
Vlk
-
Title should be 4.8, isn't it?
Also, the user must disable the self-defense module before.
-
The necessity to turn off self-defense prior to running aswBeta.exe is clearly stated in my original post.
BTW thanks for the notice about the version number. ;)
-
The necessity to turn off self-defense prior to running aswBeta.exe is clearly stated in my original post.
You are quite right but this is a deviation from standard procedure for beta testing and can easily be missed in the rush to get down to the fix list. May I suggest it would help to make this requirement at least in bold and preferably in color in your post?
-
The necessity to turn off self-defense prior to running aswBeta.exe is clearly stated in my original post.
Too many posts... too few reading carefully. Sorry.
-
The necessity to turn off self-defense prior to running aswBeta.exe is clearly stated in my original post.
You are quite right but this is a deviation from standard procedure for beta testing and can easily be missed in the rush to get down to the fix list. May I suggest it would help to make this requirement at least in bold and preferably in color in your post?
He He, which is exactly what I did ;D but as soon as it happened I knew I had to disable it.
Vlk, if that is an incomplete list you guys at Alwil have ben busy, thanks very much.
-
Thanks Vlk
And all the developement team for a quick answer, but I would like to download the all install package, I like the clean installations ;)
Kindly Regards ;D
MiguelAngelXP
-
Agree with Miguel.
It would be nice if the new beta version could be downloaded as a standalone installer file, because I still could not update through proxy.
Keep a good job, Vlk 8)
-
Great news--looking forward to testing this out!
But before doing so, I was wondering, is this essentially the same as other betas? It pretty much looks like it to me except for the bit of tweaking you have to do for the self-protection feature. Can we also still normally update to the final release when it's available, or is it slightly different in design?
Other than that, thanks a lot for the hard work on this. :)
-
It would be nice if the new beta version could be downloaded as a standalone installer file, because I still could not update through proxy.
I have updated my original post. ;)
But before doing so, I was wondering, is this essentially the same as other betas? It pretty much looks like it to me except for the bit of tweaking you have to do for the self-protection feature. Can we also still normally update to the final release when it's available, or is it slightly different in design?
Yes, you will be able to seemlessly update to the official version once it's available.
BTW moving forward, it will always be necessary to temporarily disable the self-defense module before running aswBeta.exe. This is because we don't want to have any backdoors in it, not even for our own tools...
Cheers
Vlk
-
BTW moving forward, it will always be necessary to temporarily disable the self-defense module before running aswBeta.exe. This is because we don't want to have any backdoors in it, not even for our own tools...
Not at all unreasonable ... but to follow your recent logic in the aswclear.exe discussion and given that the vast majority of beta participants will always be existing avast users ... .should not a brand new aswbeta.exe module simply prompt the user by asking:
"Have you remembered to disable the avast self defense module via avast Program settings > Troubleshooting? Y/N"
before proceeding?
-
BTW moving forward, it will always be necessary to temporarily disable the self-defense module before running aswBeta.exe. This is because we don't want to have any backdoors in it, not even for our own tools...
Not at all unreasonable ... but to follow your recent logic in the aswclear.exe discussion and given that the vast majority of beta participants will always be existing avast users ... .should not a brand new aswbeta.exe module simply prompt the user by asking:
"Have you remembered to disable the avast self defense module via avast Program settings > Troubleshooting? Y/N"
before proceeding?
Yes, this is planned. Well, in fact, instead of asking like this, it will detect if self-defense is on, and if it is, instruct the user to disable it.
-
Very nice! The professionalism of your team is always several steps ahead.
-
- fixed entering of the license key (didn't work in certain configurations)
- avast can now correctly handle the case when the INI file is missing/corrupted
- the "Disable startup rootkit scan" option on the Troubleshooting page now effective (in the previous version, it was ignored)
Any comments on this release are welcome and appreciated!
Thanks
Vlk
A certain, perverse, happiness here! After all the times that the key wasn't accepted, perhaps it wasn't just me :)
Perhaps the .ini file matter was a combination of this needing fixing and my set-up.
Also, thought I was in trouble again re. rootkit scan not holding off, so pleased that I didn't bother to pursue it.
Many thanks for this update.
-
So, Giraffe, does this build work on your system? Remember than it's a pre-release build, so we don't actually guarantee that all the issues on the list are really solved. :)
-
I think so Vlk, thank you, but of course there are many things that might no be used immediately.
Until the re-installation a few days ago, some prefs. wouldn't hold. I prefer the interface unskinned and that now works; also wanted to turn off sound but got to like the somewhat cheesy voice :D
Now going to try turning off rootkit scan at start-up, as somewhere there's an extra 10s on the boot.
-
I installed the lastest Beta of Avast and so far so good. It fixed my issue with Comodo Firewall 3.0 and thanks Avast. :)
-
I can confirm that this version at least fixed the mouse and keyboard lag I had in Team Fortress 2.
EDIT: My computer:
AMD Athlon 64 3700+
1gb RAM
ATi Radeon HD2600XT
Windows XP
-
Successfully installed 4.8.1178 with no notable problems so far.
I can confirm that the shortcut scanning on Vista now works as it should, however the fix regarding the quick start of the mail scanner may or may not have been fully fixed as I still see the slower response time in the 5th and 6th providers being started as listed in this older thread in the beta section: http://forum.avast.com/index.php?topic=34173.0 (it's issue #2 listed there). Not sure if that's a legitimate problem though or just the new way avast! behaves now on my system for whatever reason.
I'll keep testing things out for now although I haven't had much issues with 4.8.1169 except an odd sound driver error where the sound completely failed and repeated itself over and over with static for any application that tried to play sound (I cannot confirm if this is a conflict with avast! and the C-Media drivers I use, or if the new C-Media driver I'm using isn't stable with Vista for some reason). That problem has only happened 3 times so far (I was only able to disable avast!'s on access protection during one of the times to see if it was the cause, but it didn't affect the sound errors) and I'm not entirely sure how to reproduce it, although I'm hoping its fixed. I guess we'll have to see, although everything's looking good so far. :)
-
Mouse and keyboard lag I had in World of Warcraft seems fixed ;)
--lee
-
I am still experiencing the mouse and keyboard lag in World of Warcraft after installing the Beta. It is different now (the mouse disappears but the keyboard responds a bit better, although there are still issues) but the problem definitely is still there.
AMD Athlon 64 FX-55 Processor 2.6
ATI Radeon HD 2600 XT
2.0 GB RAM
Windows XP
All drivers and Windows current with Updates
Ill keep an eye on thsi thread for any more updates.
-
So far no problems with this build :)
Greetz, Red.
-
Found a possible bug with the self-protect module.
I'm running this pre-release on Win XP SP2 Pro, and I went into Services and try to stop the avast! service, and do get a warning. With this pre-release I noticed that the "No" buttons has an auto countdown, and decided to leave it and see what happens ... It was not what I expected, it counted down, disappeared and allowed the avast! service to stop. :-\
Might be something you would want to look into.
-- Sauron
Please see: http://forum.avast.com/index.php?topic=34663.0
-
So, Giraffe, does this build work on your system? Remember than it's a pre-release build, so we don't actually guarantee that all the issues on the list are really solved. :)
First of all : I couldn't stand it, I downloaded the Beta (aswbeta.exe) and installed, I knew that I couldn't wait till the final build
Well I know this is a beta, and I can stand it's glitches , so I downloaded the aswbeta.exe and installed 4.8.1178 Beta (I followed all the instructions posted by Vlk) but at startup my machine froze up, so I rebooted manually it and all went fine. But when after performing the CHKDSK at startup the 5 minutes delays still appears, in fact it's my only problem with this version. I want to make it clear . But as I said it I know this is a beta, and I'm going to stick with it, I can stand the 5 minutes delay in part because I'm testing this Beta and besides that I perform the CHKDSK 3 times a week, so please take this as a feedback. I'm using Avast for nearly a half year, and I like it. It doesn't matter to me , if the scan takes me 3 hours (average time) to scan my HDD), I use the deep scanning mode. And I'm not going to change of vendor, for free, is a complete suite. So my congratulations despite the glitches to the developement team (I know that they do their best with a lot of heart, a lot of mugs of coffe, sandwiches and in less grade cigarrettes ;) etc , thanks to the moderators of this forum and all my peers. ;D ;D ;D ;D ;D
Thanks very much for an excellent antivirus
Regards
MiguelAngelXP ;D
-
Hi
After installing this new beta there is no more spinning ball (blue icon). A deinstall and new install does not help. I'm asking me if my PC is protected?
Regards
housi
-
Found a possible bug with the self-protect module.
I'm running this pre-release on Win XP SP2 Pro, and I went into Services and try to stop the avast! service, and do get a warning. With this pre-release I noticed that the "No" buttons has an auto countdown, and decided to leave it and see what happens ... It was not what I expected, it counted down, disappeared and allowed the avast! service to stop. :-\
<snip>
Are you sure it actually stopped, does the Task Manager still show ashServ.exe as running and this is the service you tried to stop ?
Is the avast ' a ' icon still there and nothing superimposed over it ?
Does avast still appear to be working, scanning (ashQuick), etc.
Edit: Perhaps you should create a new topic for this so as not to take this off-topic and answer the questions there.
-
Found a possible bug with the self-protect module.
I'm running this pre-release on Win XP SP2 Pro, and I went into Services and try to stop the avast! service, and do get a warning. With this pre-release I noticed that the "No" buttons has an auto countdown, and decided to leave it and see what happens ... It was not what I expected, it counted down, disappeared and allowed the avast! service to stop. :-\
<snip>
Are you sure it actually stopped, does the Task Manager still show ashServ.exe as running and this is the service you tried to stop ?
Is the avast ' a ' icon still there and nothing superimposed over it ?
Does avast still appear to be working, scanning (ashQuick), etc.
Edit: Perhaps you should create a new topic for this so as not to take this off-topic and answer the questions there.
Done: http://forum.avast.com/index.php?topic=34663.0
-
I am still recieving major keystroke lags in counter strike source even after install this pre-release version.
This has something to do with older ATI agp cards, like my 9800pro imo.
-
Please keep this topic clear and post this in either its own new topic or add to the WoW topic.
Edit: I see you have done that but with out the reference to the graphics card.
Yep the pre-release seemed to fix the problem at first but after a while the lags came back and they last alot longer.
If you tried the tests that Vlk or Igor suggested earlier before the 4.8.1178 beta release if you can also post those results.
-
Installed 4.8.1178 pre-release just now.
Rootkit scan still eats 100% cpu for 15 minutes, but now it can be turned off, so I'm happy :)
Thank you.
-
Rootkit scan still eats 100% cpu for 15 minutes, but now it can be turned off, so I'm happy :)
Hmmm... seems strange... what other security programs are you running?
I can't even notice that rootkit scanning is being performed at boot time...
-
besides that I perform the CHKDSK 3 times a week
Really? Why do you want (or need) to do so? Seems a lot...
-
Ever since i started using NTFS i performed like only 3 CHKDSK checks because i suspected something went wrong with disk (nothing was wrong though). FAT32 is another story...
-
Hmmm... seems strange... what other security programs are you running?
No other security software except Kerio Personal Firewall 2.15 (which really a "plain" firewall - no ad blocking, no spyware detection, etc). I even tried to turn it off.
I uploaded an userdump, so I expect avast team will eventually fix the problem.
If there is another way I can contribute, just let me know.
If you want more details about the issue, here is the original thread:
http://forum.avast.com/index.php?topic=34308.0 (http://forum.avast.com/index.php?topic=34308.0)
-
Hi
After installing this new beta there is no more spinning ball (blue icon). A deinstall and new install does not help. I'm asking me if my PC is protected?
Regards
housi
Hi housi:
The spinning ball is the icon for VRDB "Virus Recovery Database" as it states in the help section and to solve your problem I copy the help excerpt :
SETTINGS
The settings of VRDB can be changed by clicking on the icon in the system tray "a" icon with the right mouse button. There are three options:
Generate VRDB when computer is idle. avast! will create its database only when the computer is idle, i.e. when it is not being used.
Generate VRDB only when screen-saver is running. avast! will create its database during the time screen-saver is running. It may be any screen-saver, not only the one included in avast!
Disable VRDB generation. avast! will neither create, nor update the database. If you select this option, it will not be possible to repair virus infected files in the future!
I hope you can solve the issue
Kindly regards
MiguelAngelXP
-
besides that I perform the CHKDSK 3 times a week
Really? Why do you want (or need) to do so? Seems a lot...
Hi Tech:
Yes, you're right is a lot but my iisues with v 1169 was triggered when I perform the CHKDSK and in this week I was testing v 1169 and v 1178, but for now, I'm quite satisfied, I perform my weekly antivirus scan without problems ;D
Thanks for your concern
Kindly Regards
MiguelAngelXP
-
Hi MiguelAngelXP
Thanks for answering.
The spinning ball is the icon for VRDB "Virus Recovery Database" as it states in the help section and to solve your problem I copy the help excerpt :
I know that, I would say the avast-icon (blue icon with a), will say I had no avast-icon nor a VRDB-icon.
I think my Outpost Firewall was the reason why. I did deinstall avast and I did deinstall Outpost. After I did reinstall avast and then reinstall Outpost. Now all seems to be ok.
Regards
Housi
-
Your adding to the avast help file information something that isn't there.
SETTINGS
The settings of VRDB can be changed by clicking on the icon in the system tray with the right mouse button. There are three options:
Note: there is no mention of which icon, on installation the VRDB icon ' i ' is separated from the main avast ' a ' icon (which has nothing to do with the VRDB), when the ' a ' icon is rotating it is scanning files.
You right click on the ' i ' icon to access the VRDB settings and the ' i ' icon rotates when then the VRDB is being generated. It is possible to merge both together, in which case right click the avast ' a ' icon, select VRDB and you can then access the settings. Once again when the VRDB is generating the icons split so the ' i ' rotates, once the VRDB generation is complete the icons merge again.
-
since version 4.8 (both final and this beta) i noticed in Pro version sometimes IE7 crash with error related to ahaScr.dll 4, 8, 1169, 0
most intersting on this one it's completely random rare (only what i can say it happens with multi-tabs in use)
also it happens even Avast! is disabled (services are off, none of them or gui component in memory tho i assume the low level driver is still active)
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Description:
Faulting application iexplore.exe, version 7.0.6000.16512, faulting module ahascr.dll, version 4.8.1169.0, fault address 0x000060de.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 69 65 78 ure iex
0018: 70 6c 6f 72 65 2e 65 78 plore.ex
0020: 65 20 37 2e 30 2e 36 30 e 7.0.60
0028: 30 30 2e 31 36 35 31 32 00.16512
0030: 20 69 6e 20 61 68 61 73 in ahas
0038: 63 72 2e 64 6c 6c 20 34 cr.dll 4
0040: 2e 38 2e 31 31 36 39 2e .8.1169.
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 30 set 0000
0058: 36 30 64 65 0d 0a 60de..
-
Your adding to the avast help file information something that isn't there.
SETTINGS
The settings of VRDB can be changed by clicking on the icon in the system tray with the right mouse button. There are three options:
Note: there is no mention of which icon, on installation the VRDB icon ' i ' is separated from the main avast ' a ' icon (which has nothing to do with the VRDB), when the ' a ' icon is rotating it is scanning files.
You right click on the ' i ' icon to access the VRDB settings and the ' i ' icon rotates when then the VRDB is being generated. It is possible to merge both together, in which case right click the avast ' a ' icon, select VRDB and you can then access the settings. Once again when the VRDB is generating the icons split so the ' i ' rotates, once the VRDB generation is complete the icons merge again.
Hmmm its weird because I copied from the help file I will copy all the help related to VRDB
VRDB
VRDB stands for "Virus Recovery Database"; it was known as "Integrity Database" in previous avast! versions. The aim of VRDB is to help when, despite all the security measures, a virus gets inside the computer and the files are infected. With the help of VRDB, it is possible to repair many infected files (return them exactly to their original state). VRDB is announced by an icon with the letter "i" in the system tray (next to the clock). If the icon is animated, the database is being created right now.
VRDB PRINCIPLE
avast! creates an integrity database, i.e. it stores information about the actual state of the files, doing it three versions back for each file. The database creation/maintenance is performed either when the computer is idle, or when the screen-saver is running (any screen-saver, not only the avast! one). This database, once it is created, is updated each three weeks (this value may be changed by editing avast4.ini).
If a file is infected by a virus, it may be possible to repair it using the information stored in VRDB, i.e. turn it to its original state. If there are multiple versions of the file in the database, you can choose which version you want to restore.
SETTINGS
The settings of VRDB can be changed by clicking on the icon in the system tray with the right mouse button. There are three options:
Generate VRDB when computer is idle. avast! will create its database only when the computer is idle, i.e. when it is not being used.
Generate VRDB only when screen-saver is running. avast! will create its database during the time screen-saver is running. It may be any screen-saver, not only the one included in avast!
Disable VRDB generation. avast! will neither create, nor update the database. If you select this option, it will not be possible to repair virus infected files in the future!
Regards
MiguelAngelXP
-
I quoted the relevant part of the help file.
The key point is it doesn't state which icon, just the icon in the system tray, it was your interpretation that this was the ' a ' icon which it isn't by default the avast icons are separated and it is the ' i ' icon that is for the VRDB.
The settings of VRDB can be changed by clicking on the icon in the system tray with the right mouse button. There are three options:
So no mention of which icon, also if you right click the main avast icon there are no three choices for the VRDB, even if you had merged the icons it would only show VRDB, you would then need to expand that before the three selections were visible.
-
ok i'm observing new weird things happening with new beta while avast protection is active even when avast services are not active
randomly some applications refuse to start completely (they in memory but inert)
and if that happen you can't start this application that session until restart
except starting all avast services then terminating that 'freezed' application and starting it again
not experienced such problems prior 4.8
-
ok i'm observing new weird things happening with new beta while avast protection is active even when avast services are not active
As you know, avast providers aren't only the services running. There are low level drivers loaded. If you disable the service, the providers go to "waiting for a subsystem to start" state. The better will be setting the providers to 'pause' or 'terminate' state without messing with the services, imho.
-
Good thing the cpu overreving when virus scanning is fixed. Virus Scanning with 4.8.1169 often has 100% cpu, with 4.8.1178 has >40% cpu.
-
ok i'm observing new weird things happening with new beta while avast protection is active even when avast services are not active
Sorry, this was reported before. avast providers aren't only the services running. There are low level drivers loaded. If you disable the service, the providers go to "waiting for a subsystem to start" state. The better will be setting the providers to 'pause' or 'terminate' state without messing with the services, imho.
tech i know (and You should know i know) it that there are still one or two low level drivers of Avast! and that's exactly the reason why i put that description what IT is ...
and the problem is not with Avast! stuff being inert and hang, which was different type of bug (similar with effect on the process) which btw. i reported in 4.8 beta already
but that one was related to Avast! in memory components and THIS one is related to ANY program (so they different) ...
so please next time before You start with "sorry, this was reported before" ... read twice, think twice ... because such comment is absolute useless on this forum
-
so please next time before You start with "sorry, this was reported before" ... read twice, think twice ... because such comment is absolute useless on this forum
I'll edit my post... maybe I was not happy choosing the words...
-
It wont install for me it keeps saying Cannot write file C:\Program Files\Alwil Software\Avast4\setup\servers.def THEN A error has occured during the update to beta version
can someone help please ?
-
NVM! im so stupid after ticking self-def off i didnt click ok XD DUH anyway hope this works ty!! been putting up with mouse/keyboard lag for a week =[ even formatted comp and everything >_<
P.S sorry for double post
-
It wont install for me it keeps saying Cannot write file C:\Program Files\Alwil Software\Avast4\setup\servers.def THEN A error has occured during the update to beta version
can someone help please ?
Which firewall do you use? Can you manually update your previous avast (official release) installation?
NVM! im so stupid after ticking self-def off i didnt click ok XD DUH anyway hope this works ty!! been putting up with mouse/keyboard lag for a week =[ even formatted comp and everything >_<
P.S sorry for double post
I'm not following you... can you rephrase?
-
NVM! im so stupid after ticking self-def off i didnt click ok XD DUH anyway hope this works ty!! been putting up with mouse/keyboard lag for a week =[ even formatted comp and everything >_<
P.S sorry for double post
I'm not following you... can you rephrase?
She uses many text "emoticons (http://en.wikipedia.org/wiki/Emoticon)" instead of forum-based ones, which makes her sentences hard to read. BTW, In chat abbreviations, NVM means "never mind" while ty is "thank you". Below is the "decrypted" one.
Never mind! I'm so stupid. After ticking off the self-defense module, I didn't click OK. :P Duh. Anyway, hope this works. Thank you!! I've been putting up with mouse/keyboard lag for a week :( and even formatted my computer and everything. :-\
-
Thanks Rumpelstiltskin for the translation ;)
-
it worked =D *very happy*
-
Thank you so much for getting these issues resolved!
-
Thanks for the beta. It seems to have taken care of the keyboard lag issue I was having with Red Orchestra.
-
Dear Vlk,
I have had a troublesome time since this upgrade was floated.
The beta version wouldn't write to wherever it should.
I did a clean install after using the cleanup program, managed to finally find my licence no in the chaos!
The one thing that has remained a bother is the little red disk in the blue disk syndrome.
Starting it on the management Console doesn't cure it for the next start-up.
The program does appear to open normally if I only log-off or restart.
I have run repair on add/remove programs.
I have done all sorts of permutaions with and without safe-mode . I don't have an Internet connection in that mode.
As it only started with this upgrade, I tend to think the answer may be with that, but the forums don't appear to show that its bothering a lot of people.
I may be the only person on your forum with an old 233 Dell (Win 95) upgraded in steps to w2000 and 128 MB of RAM.
I run Zone Alarm for firewall and SpyBot for spyware etc. The SpyBot appears to run only on command and is not "resident" .
My Dell 325SX (Win 3.1) sits nearby to amuse the grandchildren!
Any suggestions would be welcome. Could the official release be a more finished article than the "pre-Release" in this respect?
Slán tamall,
Tom Johnson
Hi *,
here I'm again. A service update for avast Home/Pro is coming soon (my guess is in about 1-2 weeks) and as usual, it's my pleasure to announce the availability of a pre-release version of this update.
How to install it:
In case you already have avast 4.7/4.8 installed on your system:
1. NEW! go to avast settings, and on the Troubleshooting page, disable the avast self-defense module (this is NECESSARY for the update to complete successfully)
2. download and run the following program: http://files.avast.com/files/beta/aswbeta.exe
3. after it completes, re-enable self-defense module (disabled in step 1.)
That's about all it takes (provided you have a previous version of avast Home/Pro already installed, of course).
If you don't have the previous version installed, or would prefer to do a clean install (which, in some more serious cases, may be necessary), we have also prepared the full installation packages (setup files). These can be downloaded from the following locations:
http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupengpro.exe (Professional Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupful.exe (Home Edition, all languages) ~59MB
http://public.avast.com/~vlk/4.8.1178/setupfulpro.exe (Professional Edition, all languages) ~59MB
If your current installation of avast stopped working (and/or cannot be uninstalled), we recommend the following procedure to install this new build from scratch:
1. boot into Windows Safe Mode
2. use aswClear.exe (http://www.avast.com/eng/avast-uninstall-utility.html) to remove any existing avast installation (or remaints of it)
3. boot back into normal Windows mode and use the above mentioned setup packages to install the new version
There is a number of fixes in this release. Here's an (incomplete) list:
- solved incompatibility of the avast self protection module and the System Restore feature (Windows XP/Vista)
- solved keyboard/mouse lags in some games (e.g. World of Warcraft)
- "Quick" scan now quick again (in the previous version, it was usually slower than "Normal" scan)
- fixed deleting of infected files in some nested archives
- shell extension: under Windows Vista, shortcut targets are now correctly scanned
- boot-time scanner now correctly displays warning messages about corrupted archives
- improved scanning speed in the Simple user interface
- improved handling of scan exceptions
- self protection: improved detection of changes in the INI file
- start of the "avast! Mail Scanner" service should now be fast again
- fixed a problem with avast being installed in a directory with name containing non-Latin characters
- fixed entering of the license key (didn't work in certain configurations)
- improved detection/healing of MBR rootkits
- avast can now correctly handle the case when the INI file is missing/corrupted
- the "Disable startup rootkit scan" option on the Troubleshooting page now effective (in the previous version, it was ignored)
Any comments on this release are welcome and appreciated!
Thanks
Vlk
-
hi guys !
I have win xp pack 2
I would always click the green window which pops up whenever an update is available, to update my avast.
must I know follow the procedures above or I can update without following them?
thanks in advance
-
Hi NourinE!
If you want to install the latest BETA, you should follow the above instructions, but if you want to download the standart version, you'll have to wait till it come out, and then, follow the green message window.
-
Hi all
Every so often I take the latest VpsUpd.exe in USB stick, to a friend with no regular internet access.
When doing so today I discovered that 080424-0 will not work on avast! 4.7.
No problem I thought, I'll just upgrade to 4.8. Now the only 4.8 version I had on the stick was 1178 beta which in my experience, is pretty much as good as a GA, so I upgraded using that.
Problem is that after a successful upgrade I was still unable to run VpsUpd.exe - see attached .jpg. :o (...frustration slowly subsiding)
-
Hmm, it seems that VPSupd doesn't "know" about the latest beta. Should be an easy fix, I hope...
Edit:
OK, it's not... I was told that VpsUpd.exe is bound to a particular servers.def (i.e. there would have to be a separate VpsUpd.exe for beta releases)... :-\
-
Thanks for the quick reply igor. I figured I'd have to get a copy of 1169 and take it over anyway.
On a different issue, I posted http://forum.avast.com/index.php?topic=34998.0 in the wrong place.
I've since tried the same thing on another 95OSR2 PC with Home 4.7.1098 and there's no problem (see attachment).
-
I've seen the post... I tried to reproduce it, but it doesn't behave like this for me (well, at least it doesn't freeze). Also, I'm not aware of any changes in that part of the code... but I'll try some more things.
-
The pre-release version has now been updated to 4.8.1185. It contains many fixes. The only thing that we wanted to implement but weren't able to get into this version was having the self-defense module report to the user when there's something blocked (e.g. in MSCONFIG).
Thanks
Vlk
-
since version 4.8 (both final and this beta) i noticed in Pro version sometimes IE7 crash with error related to ahaScr.dll 4, 8, 1169, 0
most intersting on this one it's completely random rare (only what i can say it happens with multi-tabs in use)
also it happens even Avast! is disabled (services are off, none of them or gui component in memory tho i assume the low level driver is still active)
Dwarden, can you please watch for any improvements?
Even though nothing has changed in Script Blocker for quite a long time (so maybe the problems are more connected to some recent IE updates that avast! version?), we've put some additional checks into the code now... so it might help.
-
I've since tried the same thing on another 95OSR2 PC with Home 4.7.1098 and there's no problem
I've now upgraded 4.7.1098 to 4.8.1178 on this machine and still no problem.
Could it be hardware/driver related? The PC that froze has a 1MB PCI video card. I'll try and reproduce it on an old MediaGX Win98 laptop.
-
The necessity to turn off self-defense prior to running aswBeta.exe is clearly stated in my original post.
I am unable to turn this off as I use Windows 98 S.E
I originally downloaded Avast using this link http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
So am I best to wait for program updates only? and is this a beta that I am currently running? as it performed the manual update from 1178 to 1185 without any hiccups.
-
I'll try and reproduce it on an old MediaGX Win98 laptop.
Result: see attachment. No message - but no freeze either.
-
This is with 4.8.1185?
-
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.
-
Even though nothing has changed in Script Blocker for quite a long time
Does Script Blocker work on Vista and IE Protected Mode?
I can't see the splash screen whatever I do...
-
since version 4.8 (both final and this beta) i noticed in Pro version sometimes IE7 crash with error related to ahaScr.dll 4, 8, 1169, 0
most intersting on this one it's completely random rare (only what i can say it happens with multi-tabs in use)
also it happens even Avast! is disabled (services are off, none of them or gui component in memory tho i assume the low level driver is still active)
Dwarden, can you please watch for any improvements?
Even though nothing has changed in Script Blocker for quite a long time (so maybe the problems are more connected to some recent IE updates that avast! version?), we've put some additional checks into the code now... so it might help.
i will , for sure ... i got lot of people to care about who use Avast! so it's more like 'I MUST' :) less bugs in Avast! less headache and late night calls lol
-
I just update to 4.8.1185 without downloading and running the program, it updated from the Avast program itself and installed and running fine. I didn't know you could do that.
-
Hi *,
here I'm again. A service update for avast Home/Pro is coming soon (my guess is in about 1-2 weeks) and as usual, it's my pleasure to announce the availability of a pre-release version of this update.
How to install it:
In case you already have avast 4.7/4.8 installed on your system:
1. NEW! go to avast settings, and on the Troubleshooting page, disable the avast self-defense module (this is NECESSARY for the update to complete successfully)
2. download and run the following program: http://files.avast.com/files/beta/aswbeta.exe
3. after it completes, re-enable self-defense module (disabled in step 1.)
That's about all it takes (provided you have a previous version of avast Home/Pro already installed, of course).
If you don't have the previous version installed, or would prefer to do a clean install (which, in some more serious cases, may be necessary), we have also prepared the full installation packages (setup files). These can be downloaded from the following locations:
http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupengpro.exe (Professional Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupful.exe (Home Edition, all languages) ~59MB
http://public.avast.com/~vlk/4.8.1178/setupfulpro.exe (Professional Edition, all languages) ~59MB
If your current installation of avast stopped working (and/or cannot be uninstalled), we recommend the following procedure to install this new build from scratch:
1. boot into Windows Safe Mode
2. use aswClear.exe (http://www.avast.com/eng/avast-uninstall-utility.html) to remove any existing avast installation (or remaints of it)
3. boot back into normal Windows mode and use the above mentioned setup packages to install the new version
There is a number of fixes in this release. Here's an (incomplete) list:
- solved incompatibility of the avast self protection module and the System Restore feature (Windows XP/Vista)
- solved keyboard/mouse lags in some games (e.g. World of Warcraft)
- "Quick" scan now quick again (in the previous version, it was usually slower than "Normal" scan)
- fixed deleting of infected files in some nested archives
- shell extension: under Windows Vista, shortcut targets are now correctly scanned
- boot-time scanner now correctly displays warning messages about corrupted archives
- improved scanning speed in the Simple user interface
- improved handling of scan exceptions
- self protection: improved detection of changes in the INI file
- start of the "avast! Mail Scanner" service should now be fast again
- fixed a problem with avast being installed in a directory with name containing non-Latin characters
- fixed entering of the license key (didn't work in certain configurations)
- improved detection/healing of MBR rootkits
- avast can now correctly handle the case when the INI file is missing/corrupted
- the "Disable startup rootkit scan" option on the Troubleshooting page now effective (in the previous version, it was ignored)
edit 04/25: the program has now been updated to build 4.8.1185.
Any comments on this release are welcome and appreciated!
Thanks
Vlk
What about Windows ME. ?? No self defence to disable ??. Just down load and go ???Thanks Avast/Home (free)
-
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?
-
The pre-release version has now been updated to 4.8.1185. It contains many fixes. The only thing that we wanted to implement but weren't able to get into this version was having the self-defense module report to the user when there's something blocked (e.g. in MSCONFIG).
Thanks
Vlk
Vlk,
What about users of ME and 98 S.E that are unable to disable the self defence module that want to perhaps try a new beta program?
I started off by using the home version link on your pre-release page, and I am led to believe that this included the aswbeta.exe files too. So would that mean that I indeed have and using the beta program right now?
I manually upgraded the 1178 to 1185 and it appeared to work without using any aswbeta.exe although I would be worried as I don't have access to the self defence module to disable it.
I really just want to know how to upgrade with the 1185 that I currently have at the moment.
Hope to hear from you.
-
Hi *,
here I'm again. A service update for avast Home/Pro is coming soon (my guess is in about 1-2 weeks) and as usual, it's my pleasure to announce the availability of a pre-release version of this update.
How to install it:
In case you already have avast 4.7/4.8 installed on your system:
1. NEW! go to avast settings, and on the Troubleshooting page, disable the avast self-defense module (this is NECESSARY for the update to complete successfully)
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?
-
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
-
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?
-
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, 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?
-
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.
-
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?
-
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...
-
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
-
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.
-
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.
-
@ 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.
-
Yes, so would I always be using the beta stream?
-
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.
-
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.
-
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!
-
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.
-
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
-
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 (http://avast.com/eng/avast-4-home_pro-revision-history.html). 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.
-
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.
-
Can we please get the links updated for v4.8.1185?
Thanks...
-
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.
-
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
-
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.
-
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 (http://avast.com/eng/avast-4-home_pro-revision-history.html). 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 ??
-
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).
(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 (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
-
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 ??
It doesn't matter. You can update either manually or automatically.
(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 (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
Tech, I think hines232 doesn't want to have beta version. I am not sure which version he/she is using but even if he/she is using a beta version, he/she will get the official version sooner or later anyway. Whether he sets it manually or automatically doesn't matter as long as he/she updates when the official version is released. Hence the answer.
-
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).
(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 (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
"Self defence module" (not in windows ME Avast ver.) I stand corrected Thanks. I think I have the answer.
-
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 ??
It doesn't matter. You can update either manually or automatically.
(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 (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
Tech, I think hines232 doesn't want to have beta version. I am not sure which version he/she is using but even if he/she is using a beta version, he/she will get the official version sooner or later anyway. Whether he sets it manually or automatically doesn't matter as long as he/she updates when the official version is released. Hence the answer.
;DHence the answer is correct. Thanks. (just needed to know if I had to do any thing special for windows ME.)
-
The beta has now been updated to v4.8.1187. To get this version from 1178 or 1185, simply invoke the Program Update feature from within the avast GUI (you don't need to run aswBeta.exe again).
Main changes in this release:
- solved the intermittent self-defense process identification issue (resulting e.g. in random INI modification consent dialogs)
- attempt to solve a synchronization problem in the AV engine initialization
- changed the way INI modification consent dialog is shown. Now, it is shown only if notepad.exe is trying to access the file
Thanks
Vlk
-
(you need to run aswBeta.exe again).
(The italic by me)
Shouldn't these be "don't need to"?
- solved the intermittent self-defense process identification issue (resulting e.g. in random INI modification consent dialogs)
We'd gotten the consent dialog first time when Avast! was attempting update from 4.8.1185 to 4.8.1187 (Means, we haven't had this message with any VPS update). Although I confirmed the dialog, Avast! told me that it didn't have enough privilege to continue the operation. Despite of this, strangely, Avast! prompted me to restart the computer and I followed the instruction. ???
The procedure felt odd but, after the restart, the version number says 4.8.1187. Hopefully, this will be the end of the bad behavior by the "drunk" self-defense module. ;D
-
Vlk, any chance for "Pidgin" support? GAIM used to be supported but that client is now long gone and avast! doesn't support it anymore.
-
The beta has now been updated to v4.8.1187.
<snip>
Main changes in this release:
<snip>
- changed the way INI modification consent dialog is shown. Now, it is shown only if notepad.exe is trying to access the file
See this post, http://forum.avast.com/index.php?topic=35060.msg295103#msg295103 (http://forum.avast.com/index.php?topic=35060.msg295103#msg295103) for the inadvertent consequence of the above quoted change made in the update, not being able to edit avast4.ini with anything other than notepad.
-
Just thought to say I have upgraded to version beta 1187 no problems experienced so far.
98 S.E
:)
-
I have not any problems with the latest update but for inrormation only I should report about new EventId records appered during update.
There are 4 new records, all have Source Service Contorol Manager and Event Id 7006
The ScRegSetValueExW call failed for Type with the following error:
Access is denied.
Corresponding setup.log records are:
...
19:35:41 vrb/sys Service avast! Antivirus dependency aswMon2;RpcSS;
19:35:41 vrb/reg Set registry: SYSTEM\CurrentControlSet\Services\avast! Antivirus\Description=Управляет и осуществляет сервисами avast! антивирус на этом компьютере. Включает резидентную защиту, вирусное хранилище и планировщик.
19:35:41 min/sys Service avast! Antivirus NOT updated, error code: 0x00000005
19:35:41 vrb/sys Service aswUpdSv dependency (null)
19:35:41 vrb/reg Set registry: SYSTEM\CurrentControlSet\Services\aswUpdSv\Description=Обеспечивает автоматическое обновление avast! антивирус.
19:35:41 min/sys Service aswUpdSv NOT updated, error code: 0x00000005
19:35:41 vrb/sys Reboot set by changed resident H:\WINDOWS\system32\drivers\aavmker4.sys
...
19:35:42 vrb/sys Service avast! Mail Scanner dependency avast! Antivirus
19:35:42 vrb/reg Set registry: SYSTEM\CurrentControlSet\Services\avast! Mail Scanner\Description=Инструменты сканирования почты для avast! antivirus.
19:35:42 min/sys Service avast! Mail Scanner NOT updated, error code: 0x00000005
19:35:42 vrb/sys Starting service avast! Mail Scanner
19:35:42 vrb/sys Service avast! Mail Scanner started, errcode: 0x00000420
19:35:42 vrb/sys Reboot set by changed resident H:\WINDOWS\system32\drivers\aswTdi.sys
...
19:35:42 vrb/sys Service avast! Web Scanner dependency avast! Antivirus
19:35:42 vrb/reg Set registry: SYSTEM\CurrentControlSet\Services\avast! Web Scanner\Description=Инструменты сканирования вэб (HTTP) для avast! antivirus.
19:35:42 min/sys Service avast! Web Scanner NOT updated, error code: 0x00000005
19:35:42 vrb/sys Starting service avast! Web Scanner
19:35:42 vrb/sys Service avast! Web Scanner started, errcode: 0x00000420
19:35:42 vrb/sys Driver file copied: H:\WINDOWS\system32\drivers\aswRdr.sys
...
-
hmm this happens also with manual invoke update with when avast! self protection is disabled?
-
Vlk, any chance for "Pidgin" support? GAIM used to be supported but that client is now long gone and avast! doesn't support it anymore.
I second this... I'm using Pidgin ;)
-
Can someone tell me whay pidgin is please?
-
My friend google could tell you more ;D it is an IM program.
Just one of the google hits, so if you want to know something google it.
http://en.wikipedia.org/wiki/Pidgin_(software) (http://en.wikipedia.org/wiki/Pidgin_(software))
-
Any new guess as to when the beta will become an official release?
-
From another topic.
Before the final release, i.e. in a few days.
-
Haven't found any problems with 1187, seems pretty solid.
Nice job!!
-
Will this build fix all the problem reported by other users using Avast 4.8(1169) such as slow systems and systems begins locked up. Also when will the final build get released.
-
When I shut down my machine with the latest version and having had used my Outlook email, I'm getting a "Waiting for Application to Close" window for OUTLOOK.EXE when I shut down.
Is there a know email module bug?
Eric
-
When I shut down my machine with the latest version and having had used my Outlook email, I'm getting a "Waiting for Application to Close" window for OUTLOOK.EXE when I shut down.
Did you have any other antivirus in this computer in the past?
Any other Outlook plugin that could be interacting with avast?
-
I've had a number of other antiviruses in the past including recent release of antivir Premium. All left over entries removed prior to avast installation...
Trying it again today....
E
-
Thanks for the pre-release version, I have installed it in my computer without any problems and it is working good.
My question is, what will happen when the real version comes? will this real version remove the beta one?
I have used AVAST for almost a year and this is the only antivirus that have convinced me and I always recomend it to my friends in Mexico... they're all changing to AVAST since they have seen just like me that its protection is unique.
rm
-
The auto update will deal with the conversion to the regular version or you can do a manual program update, right click the avast 'a' icon, select Updating, Program Update.
If you monitor the forums you will see here when the regular program update is available.
-
It's working fine for me, however I have disabled the rootkit scan at startup
Kindly regards
MiguelAngelXP ;D
-
It's working fine for me, however I have disabled the rootkit scan at startup
Just for info but if you find a problem/s with start up rootkit scan, you can set the start time of it through the ini file (http://forum.avast.com/index.php?&topic=1647.msg21553#msg21553).
-
It's working fine for me, however I have disabled the rootkit scan at startup
Just for info but if you find a problem/s with start up rootkit scan, you can set the start time of it through the ini file (http://forum.avast.com/index.php?&topic=1647.msg21553#msg21553).
Weird issue, I can't find that entry
As appear in the link you gave me
[AntiRootkit]
WaitOnStart 120
So I will leave as it is by now, thanks a lot
Kindly Regards
MiguelAngelXP ;D
-
Weird issue, I can't find that entry
I've answered you here: http://forum.avast.com/index.php?topic=1647.msg295799#msg295799
-
And also answered.
A) don't have blank lines in the sections.
B) you need the = equals sign between the parameter name and the value, without spaces.
e.g.
[AntiRootkit]
WaitOnStart=120
-
Hi, I am having major problems with a laptop and this release.
I used the AWClear to remove all residue and installed the full program from the link on the 1st page of this post. The program installs ok, but upon re-start it hangs after 15 to 20 seconds or so. I am unable to do anything, it completely locks.
I have tried booting into safe mode and disabling the self defence and root kit scan, but to no avail.
If I remove Avast completely it works fine.
It had been running 4.7 without any issue.
Please could you advise me on what further info you would like to resolve this?
Kind regards
Iain
-
I used the AWClear to remove all residue and installed the full program from the link on the 1st page of this post.
First you should have used the Control Panel...
1. Uninstall avast from Control Panel first.
2. Boot.
3. Download the latest version of Avast Uninstall (http://www.avast.com/eng/avast-uninstall-utility.html) and use it for complete uninstallation.
4. Boot.
5. Install again the latest avast! (http://www.avast.com/eng/programs.html) version.
6. Boot.
7. Check and post the results.
Or use the latest beta:
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it or go here (http://forum.avast.com/index.php?topic=34612.msg290254#msg290254) for more information.
-
It's working fine for me, however I have disabled the rootkit scan at startup
Just for info but if you find a problem/s with start up rootkit scan, you can set the start time of it through the ini file (http://forum.avast.com/index.php?&topic=1647.msg21553#msg21553).
Weird issue, I can't find that entry
As appear in the link you gave me
[AntiRootkit]
WaitOnStart 120
So I will leave as it is by now, thanks a lot
Kindly Regards
MiguelAngelXP ;D
Thanks for your concern, but for the time being I will leave the Scan rootkit at Startup disabled
Kindly regards
Miguel Angel ;D
-
Thanks for your concern, but for the time being I will leave the Scan rootkit at Startup disabled
Why? Is it a problem?
-
Hi Tech,
I have followed your instructions to the letter. (Again and again)
I get to put the login password in and as the startup items (MSCONFIG items) are running after about 30 seconds it hangs (Again)
If I boot to safe mode and disable Self Defence, Root Kit scan and Start Services after others it still hangs (Again!!)
If I stop the avast services and boot, it comes up everytime...
I have tried to persevere with 4.8 but I starting to lose confidence. This particular machine running XP had 4.7 installed originally, so it has been working with Avast on for a couple of months without issue. Nothing new has been installed.
We purchase/recommend a lot of Avast products for our clients and for this particular client we convinced them to move away from McAfee and they have 20 machines we have to install Avast later this month when their current AV contract expires....or maybe not.
The user of the this laptop has now been without his laptop for over a week, as he roams and doesn't want to use his laptop without an AV product running.
Is there a location I can get hold of 4.7 again until these issues are sorted?
Kind regards
Iain
-
Please try to generate a memory dump at the moment the machine is frozen. The description how to do it is here (http://forum.avast.com/index.php?topic=2850.msg20171#msg20171).
-
Iain,
If you want to get avast-4.7, you can download it from Filehippo (http://filehippo.com/download_avast_antivirus). You'll see a list of older versions in the green panel on the right. Version 4.7.1098 is the first one listed there.
Hope this helps.
-
Hi Rick,
Thanks for the pointer.
VLK would love to be able to give you a memory dump, but the laptop has a cut down keybaord - so only one CTRL key.
I have made the changes and tried it, but no joy.
It is a Belinea s.book - but is running full XP SP2 - not a cut down version.
Kind regards
Iain
-
Hi Rick,
Thanks for the pointer.
VLK would love to be able to give you a memory dump, but the laptop has a cut down keybaord - so only one CTRL key.
I have made the changes and tried it, but no joy.
It is a Belinea s.book - but is running full XP SP2 - not a cut down version.
Kind regards
Iain
Try using the FN button
-
Thanks for your concern, but for the time being I will leave the Scan rootkit at Startup disabled
Why? Is it a problem?
Hmmm, for me it's like a chasing spirit, :P it haunts me. I tried the avast4.ini edit solution and I was didn't worrk for me. So I left it disabled.
Kindly regards
MiguelAngel ;D
-
Hi Tried the FN key and even plugging an external USB keyboard in - still no joy.
Am rolling back to 4.7.
If I get any issues with the other 19 machines I need to put this on I'll post back.
Thanks for trying.
Iain
-
I tried the avast4.ini edit solution and I was didn't worrk for me.
What do you mean? Can't you edit the file?
-
Hi Vlk.
I have tried to download a copy of 4.8.1187 however the link to public.avast does not seem to be active???
Baz
-
Hi Vlk.
I have tried to download a copy of 4.8.1187 however the link to public.avast does not seem to be active???
Baz
Why don't you update to beta in the conventional way?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it.
-
Hi Vlk.
I have tried to download a copy of 4.8.1187 however the link to public.avast does not seem to be active???
Baz
Why don't you update to beta in the conventional way?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it.
Hi Tech
Simple answer. Because of a recent problem with SR and Avast which I have used for a long time I removed and
tried other AV software to be sure the problem was in Avast.
I wanted to do a complete new install of the Beta - not upgrade 4.7.
Why bother with a link to 4.8.1187 if the link does not work!!!
Guess I will forget about it until the "official" release.
Baz
-
Hi Vlk.
I have tried to download a copy of 4.8.1187 however the link to public.avast does not seem to be active???
Baz
Why don't you update to beta in the conventional way?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it.
Hi Tech
Simple answer. Because of a recent problem with SR and Avast which I have used for a long time I removed and
tried other AV software to be sure the problem was in Avast.
I wanted to do a complete new install of the Beta - not upgrade 4.7.
Why bother with a link to 4.8.1187 if the link does not work!!!
Guess I will forget about it until the "official" release.
Baz
why does the link not work?! - if you have an older Avast!-edition installed it upgrades to the actual version...
but if you want an other link just go to the first side of this topic:
http://forum.avast.com/index.php?topic=34612.0 (http://forum.avast.com/index.php?topic=34612.0)
EDIT: The links on the first side are for the whole program...
-
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.
Re: Freezing and missing message when 'Push iAVS' checked in Home version, 95OSR2
Upgraded (finally) from 1185 to 1187 today. All good, no freeze, message appears. :)
-
I tried the avast4.ini edit solution and I was didn't worrk for me.
What do you mean? Can't you edit the file?
I edited the avast4.ini file as the tutorial says but it didn't work, and well , I will let it go, avast 4.8 is working fine just the way I like it like the song
Thanks Tech :)
Kindly regards
MiguelAngelXP ;D
-
I wanted to do a complete new install of the Beta - not upgrade 4.7.
You can download version 4.8 (not 4.7) and then upgrade to beta.
It won't make a difference at all.
-
i noticed that when i use quickscan (4.8 last beta) on xGB folder with various video file formats (wmv, avi, mpg, mpeg, flv, mkv)
then it takes avast very very long time to complete the task (similar with other scans on same files)...
it seems Avast! read the whole file from start to end and it's also slow (approx 2-3 times slower than disk read speed)
reason?
-
I assume you mean ashQuick.exe with is the most thorough of that scans as the Quick (on-demand, simple user interface) scan I don't think scans many of the file types you mentioned by default ?
So if you are using ashQuick.ex in lieu of a scheduled scan that wasn't something it was designed to do the bulk scanning of files, folders, partitions or drives. You could exclude your media folders for on-demand scans, which includes the ashquick.exe scan (Program Settings, Exclusions).
-
yes it's only on the thorough scan style the standard scan goes quite fast (18s for 15+ GB)
-
The beta has now been updated to v4.8.1192. To get this version from any of the previous beta builds, simply invoke the Program Update feature from within the avast GUI (you don't need to run aswBeta.exe again).
This is very likely the last beta build before the product goes gold.
Thanks
Vlk
-
The beta has now been updated to v4.8.1192. To get this version from any of the previous beta builds, simply invoke the Program Update feature from within the avast GUI (you don't need to run aswBeta.exe again).
This is very likely the last beta build before the product goes gold.
Thanks
Vlk
Good to hear Vlk, although this issue (http://forum.avast.com/index.php?topic=35143.0) immediately popped up again after the update. Think there's a bit more tweaking involved before it does hit gold. :-X
-
Using Avast 4.8.1192
Picture is self explanatory.
So what does that scanner pop up message mean? Is everything ok?
???(http://i98.photobucket.com/albums/l277/deadlyskull1977/Avast.jpg) ???
-
Avast 4.8.1192
When opening Outlook.
What is this????
(http://oisteinr.homeftp.net/Files/Diverse/AvastMessage.jpg)
-
I saw the same error during a windows update
i can't screen him but they look like to smokeyjoe's warning
-
Hi!
I also got the message like smokeyjoe when I opened MS Outlook!
But I don't think, that this is an error message - it seems as if it would be an info from the self-defense-module or something...
yours
onlysomeone
-
I hope that the message onlysomeone is seeing is the same as that posted by OisteinR.
That error message (which I did not see with releases before 1192) seems to be at exactly the time the avast plugin for Outlook is activated. It occurs (for me) whether the Outlook plugin is started or not in avast. It does not occur if the avast plugin is deactivated in Outlook. It also occurs concurrently with enabling the avast plugin in avast.
-
The avast registry keys are also protected (or are supposed to be).
It's no magic, really. Just a filter driver (in kernel mode).
Thanks
Vlk
probably thats the reason why this messages appear...
-
I have the same problem (MS Outlook). Anyway I can receive/send e-mails and the scan issue appears to be gone
http://forum.avast.com/index.php?topic=35277.msg296665#msg296665 (http://forum.avast.com/index.php?topic=35277.msg296665#msg296665)
Kindly Regards
MiguelAngelXP ;D
-
Avast 4.8.1192
When opening Outlook.
What is this????
(http://oisteinr.homeftp.net/Files/Diverse/AvastMessage.jpg)
Updating to XP SP3 gives houndreds of this type of warnings while updating.
It was something with Registry though...
Really annoying......
-
I believe this particular file (URLs.txt) is an omission and could be fixed somehow... but yes, I believe if you are updating to SP3 (or similar operations), it may request some write access to avast! registry keys...
-
I believe this particular file (URLs.txt) is an omission and could be fixed somehow... but yes, I believe if you are updating to SP3 (or similar operations), it may request some write access to avast! registry keys...
Why weren't I asked to disable avast while updating to SP3 ???
-
By whom?
And I don't think it's necessary anyway, I was just trying to explain the messages from avast! self-defense.
-
In the KB article that relates to SP3, it was recommended to disable your AV.
-
By whom?
By Windows trying to manage avast files/registry keys, by Windows Update while updating...
I've read some users are being asked to disable the antivirus (http://forum.avast.com/index.php?topic=34934.msg296882#msg296882). I wasn't asked to do so.
-
In the KB article that relates to SP3, it was recommended to disable your AV.
They all say this crap in ANY installer. This kinda defeats the purpose of antivirus if it's disabled while installing something.
Installers may look nice on the outside, but may contain bad code on the inside...
-
Using Avast 4.8.1192
Picture is self explanatory.
So what does that scanner pop up message mean? Is everything ok?
???(http://i98.photobucket.com/albums/l277/deadlyskull1977/Avast.jpg) ???
Got a similar bunch of messages that happened immediately after today's VPS update. I wasn't running anything else at that moment which confuses me a bit. No errors appear to exist in Windows' Event Viewer or Avast's logs that seem relevant to this issue.
EDIT: Also was able to reproduce these errors everytime I tried doing a registry scan using Ace Utilities.
-
Thanks for your concern, but for the time being I will leave the Scan rootkit at Startup disabled
Why? Is it a problem?
Hmmm, for me it's like a chasing spirit, :P it haunts me. I tried the avast4.ini edit solution and I was didn't worrk for me. So I left it disabled.
Kindly regards
MiguelAngel ;D
Hi everyone :
Well , I want to recover my piece of mind. So I discovered to manage the Antirootkit Startup Scanner, the solution was so awkwardly easy that I didn't realize it before. :-[
When I'm using my PC in a routine mode I enable it
When I'm performing a maitenance task, I just have to disabled it (especially if I have to reboot my PC)
Well thanks for reading me, now I settled this issue with my beloved avast antivirus ;D
Kindly Regards
MiguelAngelXP ;D
-
Why 4.8.1192 is asking for booting?
I'm already up-to-date and have boot this morning?
-
No reboot requests here with 4.8.1192, perhaps time to go hunting the reboot.txt file, etc.
-
Using Avast 4.8.1192
Picture is self explanatory.
So what does that scanner pop up message mean? Is everything ok?
???(http://i98.photobucket.com/albums/l277/deadlyskull1977/Avast.jpg) ???
Got a similar bunch of messages that happened immediately after today's VPS update. I wasn't running anything else at that moment which confuses me a bit. No errors appear to exist in Windows' Event Viewer or Avast's logs that seem relevant to this issue.
EDIT: Also was able to reproduce these errors everytime I tried doing a registry scan using Ace Utilities.
got it with CFP
-
got it with CFP
I get the same thing with a-squared HiJackFree.
-
got it with CFP
I get the same thing with a-squared HiJackFree.
i guess anything that plays around with avast files...
-
???(http://i98.photobucket.com/albums/l277/deadlyskull1977/Avast.jpg) ???
Using Avast 4.8.1192 and sp3
i had i thing like that while unistalling lavasoft adaware
-
I don't have the beta and if I am going to have to deal with all those popups, access denied messages, etc., all the time then I have no desire to have it or the official release either. Hopefully it will be straightened out soon.
-
i guess anything that plays around with avast files...
Agreed. It is just the self defense module seems to be doing it's job, or, protecting its files/registries.
I don't have the beta and if I am going to have to deal with all those popups, access denied messages, etc., all the time then I have no desire to have it or the official release either. Hopefully it will be straightened out soon.
To "convince" Avast! not to interfere with installation/uninstallation of your trusted applications, you don't need to disable Avast! itself but only the self-defense module. Go to avast settings, and on the Troubleshooting page, check "disable the avast self-defense module." Of course, don't forget to uncheck the option after installation. I installed XPSP3 in this way and have had no problem.
Alwil team may come up with better ideas such as white-listing/interactive messages in the future. However, the pop-ups must scare off the many users who don't know the existence of the self-defense module and/or don't have even the vaguest idea on what it is doing.
-
I was aware of the self-defense module and how to disable it, but I really don't want something else I have to remember to disable every time I want to install a program. Besides, if I understand some of the earlier posts by others, avast is throwing the pop-ups concerning access denials just from users opening programs they already have on their systems. I certainly don't want to have to disable self-defense every time I want to run a program.
If the access denials are just informational and don't interfere with other programs installation and operation then I won't want to see continued pop-ups concerning them. If the denials will interfere with other programs' normal operations, then hopefully avast will find a way to deal with it. Right now I am running the last release (version 4.8.1169) which has the self-defense module and I never see those pop-ups, so I assume (hope) it is a bug in how self-defense is working in the beta and that it will be dealt with before another official release. I guess if nothing else I could just permanently disable the self-defense, if it works in the next official release in the same way it seems to work in the newest beta. Not what I would really want to do but...
-
the only thing new in the beta are the actual pop-ups, which will now prob be disabled b/c of all the confusion its causing
-
I was aware of the self-defense module and how to disable it, but I really don't want something else I have to remember to disable every time I want to install a program. Besides, if I understand some of the earlier posts by others, avast is throwing the pop-ups concerning access denials just from users opening programs they already have on their systems. I certainly don't want to have to disable self-defense every time I want to run a program.
I was mentioning only SP3 update, which cannot be so frequent. Now I wonder if these pop-ups with more common applications are related with the update to SP3 (and the subsequent change of the system integrity), to the current beta or with even both updates. Under our environment (XPSP3), there are no such pop-ups yet.
-
The SP3 update was extreme (believe me). While an update like SP3 will not be a common type of change it has yet to become the mainstream update for XP users in their millions.
If avast management feels brave and is willing to risk a PR disaster on their hands then I invite them to go to production with the current popups and let's see what the user community and the press makes of the popups as they install SP3 in their hordes.
Even for the rest - we have seen the AOL response and it is still the case that every start of Outlook is going to cause a popup (unless it is fixed) and btw the Outlook popup is completely unrelated to SP3.
Surely most users of an antivirus product are really looking for a "set it and forget it" product; not one that tells them they are being saved from every bit of sloppy coding in every other product they use (or even in the antivirus itself). The fact that AOL or the SP3 update is badly written is almost totally irrelevant ... it is avast that is now thrusting errors before the user that the user can do nothing about, that represent no real threat to the user and the users will be right to ask why avast is thrusting their system into a situation that is non-threatening and often beyond their comprehension.
I have to believe that the best option for avast and the user community as whole is to make these popup displays optional but agree with friend Tech in another thread that they should be logged so that there is some evidence of what happened. There will be plenty of opportunity to review such a decision at a later date - but concurrent with a major operating system update is far from the best time for this innovation in avast.
-
the only thing new in the beta are the actual pop-ups, which will now prob be disabled b/c of all the confusion its causing
Yes, I think Vlk or Igor said it in another related topic and the consideration to remove the display of the notifications so as not to scare the horses so to speak. So we will have to see what the decision is.
I like Alan believe this simply can't be let loose as it is going to cause undue concern amongst users.
-
Not only will the pop-ups possibly cause alarm amongst many users, but as has been said already, if they are nothing that a user can do anything about and are only informational, then they will be seen as a nuisance.
What I really want to know is this...does the self-defense module need to be disabled while installing new programs? Can it interfere with installations? I would hope it doesn't need to be disabled since the time you are installing new code is probably one of the times when avast has the most need to protect itself.
However, if the self-defense module is recommended to be disabled during installs, then it would be nice to have a right click option on the avast icon in the system tray to disable and to re-enable it. At least then a user could perform the operation as painlessly as possible.
-
It shouldn't as the self-defence is for the avast application only, not other programs.
-
Not only will the pop-ups possibly cause alarm amongst many users, but as has been said already, if they are nothing that a user can do anything about and are only informational, then they will be seen as a nuisance.
It seems that Alwil team is already thinking how to deal with the notification in "another thread".
What I really want to know is this...does the self-defense module need to be disabled while installing new programs? Can it interfere with installations?
As David said, you don't need to do so. As you can see it from the notifications, all the files and registries are related with Avast! only. I thought XPSP3's dynamic overhaul could require such changes but, according to alanrf's comment above, it's more of the problem of XPSP3 setup. The same thing is said about the AOL app: They shouldn't require such changes if they were well written.
The issue seems to be about communication. Self-defense module is properly working except that it scares users with DOS window like black screen in a rather non-human-friendly manner. ;) I, myself, has no talent of programming and rely heavily on "documentations" when it comes to computers.
-
Mysterious messages yellow&green are appearing from time to time after boot.
The HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services key is being access blocked to write.
I don't know which application is trying to access, neither there is anything in logs...
Can anyone explain what is going on? ???
Note: they are not from CurrentControlSet like shown here:
http://i45.photobucket.com/albums/f66/jahnjahn/AvastMessage.jpg
Besides, they have yellow color.
I've found selfdef.txt log. Which application is trying to access?
12/05/2008 15:11:24 Write access to registry key \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\aswMonFlt\Enum denied. [PID 4]
12/05/2008 15:11:24 Write access to registry key \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\aswUpdSv denied. [PID 4]
12/05/2008 15:11:24 Write access to registry key \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\aswUpdSv\Enum denied. [PID 4]
12/05/2008 15:11:24 Write access to registry key \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\avast! Antivirus denied. [PID 4]
12/05/2008 15:11:24 Write access to registry key \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\avast! Antivirus\Enum denied. [PID 4]
-
Hi,
I decided to try the beta update on my Vista Ultimate x64 P820D 3Gb system yesterday. In the last ~24 hours I've probably had 5 or so BSOD, and the systems' only been used for ~6 hours.
I'll dig out the debugging info, I believe each time was a STOP 0x0000003B SYSTEM_SERVICE_EXCEPTION.
I'm going to de-install, and re-install avast back to the production version, so will see if that resolves the issue.
-
I'll dig out the debugging info, I believe each time was a STOP 0x0000003B SYSTEM_SERVICE_EXCEPTION.
Please, go to folder \windows\minidump and send the newest (recent) .mdmp files for analysis.
Better if you can compress (zip) them and add some information about the BSOD and the link for this thread. ;)
Upload to the any of these anonymous ftp servers:
ftp://ftp.asw.cz/incoming
ftp://www2.asw.cz/incoming
-
The update has now been officially released as v4.8.1195. Thanks to everyone who helped testing.
To get v4.8.1195, simply invoke the Program Update feature from within the avast GUI (this will work no matter what version you have already installed).
Thanks
Vlk