NEW Avast! 7 Released

Virus & Spyware

Virus & Spyware
Perspectives on PC security, including antivirus, anti-spyware and firewall solutions.

NEW Avast! 7 Released

  • Hernan,

    Glad to hear that some of the issues seem to have cleared up for you... and that they will be coming out with another ("minor") update that will hopefully address some of the remaining problems.

    Nonetheless, I would still advise everyone to wait a while... play it safe... be sure [most of] the problems have been fixed... before accepting the update.   I don't see them terminating support for v6 any time soon.

    There are some friends and [extended] family members using avast at my suggestion... many are out-of-town... and I can't risk getting "panic calls" from distant states...

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • Avast! released a corrupted vps ( virus defintion version ) yesterday ( 26 th ) that might hung Avast! and no letting it to update or even uninstall if so require.

    Today Avast! realeased a fixup tool. For more info:

    http://forum.avast.com/index.php?topic=94514.0

    After all the problems I had at the beginning. My installation has been working like a Swiss clock after VPS 120227-0 was installed. BTW I was not affected by the corrupt vps file.

    Hernan.

    Dim9200/XPS 410.C2D 2.40GHz.2GB RAM.XP Pro_86 SPk3.IE8 & FF29

    Avast!Free 9.0.2018. CIS 5.12(FW/D+). MBAM Premium. MCShield. WinPatrol +. WOT. OpenDNS. SAS(o/d)

    "We are all ignorant, but we don't all ignore the same things..." Albert Einstein

     "When you've excluded the impossible, whatever remains, however improbable, must be the truth..." Sherlock Holmes.

  • As it happens, my Nod32 came up for renewal today. It occured to me that it had never detected any threats in all the years I had used it. (Very few false positives, and no grief whatsoever over that time, for that matter).

    So I chose the free option, rather than pay. Unfortunately, as ky331 mentioned and this thread illustrates, avast v7 is not quite ready for "prime time". I chose MSE 2.0 instead.

    As we have pointed out many times in this forum, changing AVs is not a trivial process. However, in my case uninstalling NOD32 was a snap using Control Panel/Add or Remove Programs. No need for any specialised uninstall tool. Likewise, installing MSE was trouble-free.  The whole AV change process took maybe 10 minutes, including one re-boot, using XP.

    I only mention this to illustrate how simple changing an AV should be. I still intend to try Avast 7 on my portable, once they work the kinks out.

    _________________________________________

    Dell Forum Member since 2,000

    WOT Web of Trust    Use OpenDNS   MalwareBytes' Anti-Malware Free

    (Mostly) Free Security Software- A Primer

    Windows 7 Home Premium (64- Bit), Panda Cloud AV Free, OpenDNS, SpywareBlaster, MVPS Hosts file, WinPatrol PLUS, IE11, HitmanPro (on-demand 2nd opinion AV scanner), Windows software firewall, MBAM Premium, CryptoPrevent, Zemana Antilogger Free, Secunia PSI, WOT, Sandboxie, CCleaner Free.

  • From Avast! (via Facebook):

    Greetings from Prague. We would like to thank you for all your feedback on avast! v.7. Both: positive and critical comments are valuable to us. Thanks to it our developers improve avast! Antivirus and soon we will deliver to you a new program update. We will keep you posted about its availability.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • Avast has a BETA release update available, avast! 7 R2 beta candidate (build 7.0.1412).

    We normally don't bother to mention BETA programs here.   I would strongly advocate that avast 6 users stick to their existing avast 6 program for the time being, rather than "toying" with avast 7 (regular or BETA).   While it seems that some issues may have been fixed, others have not.

    People who are already "suffering" with avast 7 (regular) can read the following thread, and then decide whether they want to "gamble" on the BETA update.

     http://forum.avast.com/index.php?topic=94790.0

    EDIT:   I see there's now another beta candidate (build 7.0.1414), and initial reports here seem to be looking better.   Nonetheless, I will continue to wait.   I don't have a "spare" system to be their guinea pig.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • Avast has now released its first (non-beta) update since the infamous start of avast 7.   Just letting everyone know... I have NOT yet had the time to read-up on what's happening with it (but hope to report back later)... those interested now can learn more at http://forum.avast.com/index.php?topic=95170.0

    Avast 7.0.1426   (2012-03-07)

    • Improved File system speed
    • Improved AutoSandbox stability
    • Improved AutoSandbox controls
    • Improved gadgets
    • Compatibility with Win 8 Consumer Preview
    • Greater stability of Outlook plugins
    • Fixed a compatibility issue with offline files
    • Other security and stability-related improvements

    EDIT:   It may be early... but the only problem I see reported in the avast thread cited above is that the password protection feature, if enabled, can be defeated Tongue Tied .   Certainly not desirable, but nothing on the order of the "serious" problems reported in the original build.   I intend to keep monitoring the avast forum, and if things seem to remain calm, I might try testing avast over the weekend, when I'll have more time to focus on it.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • Linking this thread to Hernan's post elsewhere in these forums:  

    BEWARE [several] FW NOT working with Avast!7 under W7

    en.community.dell.com/.../19440270.aspx

    EDIT:   Suffice it to say, this --- along with the multitude of other issues being reported at the avast forum --- has nullified my desire to test avast7 this weekend.   Current avast6 users have a good-quality stable program, which is continuing to get multiple daily updates.   I expect it to be supported for several more months.   Therefore, I maintain my recommendation that avast6 users, who haven't already "upgraded" to avast 7, should stick with what they have:   Set its PROGRAM updates to MANUAL (and do NOT accept avast7 if offered) [but keep the Virus Definitions set on Automatic].

     

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • ky331

    Linking this thread to Hernan's post elsewhere in these forums:  

    BEWARE [several] FW NOT working with Avast!7 under W7

    en.community.dell.com/.../19440270.aspx

    Thank you David.

    I thought It would be better to open a topic of its own outside this thread that is getting very long.

    What I did not explain in my other thread was that almost two weeks ago there was only one Avast! member reporting this issue, and it took him a while for other members, mods, and devs to pay attentionto him. Be it that most Avast! members use AIS that do not require a third party FW or running XP or Vista. It is really ashamed this is happening because if malware builders get to know how Avast! web shield works they can find a big hole in those FW. What it is also a pitty is that already they are blaming each other. Avast! says they only changed a driver and it is the FW that is not reading or coping with the redirection of the web shield and Comodo ( I have not read other FW forum yet ) that is Avast! fault to create a code that other FW can not read.

    Well this saga will continue and I have not doubt it will be fixed. Already Lukor, Mayor Avast! Dev, says he is willing to sit with Comodo an explain how Avast! web shield works. However, he did not like certain comments done in the Comodo forum by a moderator. Lack of diplomacy....?

    Hernan.

    Dim9200/XPS 410.C2D 2.40GHz.2GB RAM.XP Pro_86 SPk3.IE8 & FF29

    Avast!Free 9.0.2018. CIS 5.12(FW/D+). MBAM Premium. MCShield. WinPatrol +. WOT. OpenDNS. SAS(o/d)

    "We are all ignorant, but we don't all ignore the same things..." Albert Einstein

     "When you've excluded the impossible, whatever remains, however improbable, must be the truth..." Sherlock Holmes.

  • I have no idea whose fault it is... but playing "the blame game" is typical when multiple-parties are involved:   If brand X's printer isn't working properly on brand Y's computer running under brand Z's operating system, each one can try to blame the other.

    People just don't realize how complex computer coding can be... especially when it requires [or assumes] interaction between diverse parties.   It's really amazing we don't have more such conflicts.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • I finally "bit-the-bullet", and updated Avast from 6.0.1367 to 7.0.1426, via the internal updater [on my XP/SP3 laptop].  After downloading and installing the necessary files, I was prompted for a reboot, which of course I accepted. While it was in the midst of the shutdown sequence, Scotty (WinPatrol) presented me with a popup to approve something, which unfortunately, I had insufficient time to read (and to react) before the shutdown was implemented :-(

    Upon rebooting, I was presented with a screen saying it was about to complete the upgrade process. At the bottom of this screen, in tiny writing, were two PRE-CHECKED options to install Google Chrome, and set it to be the default browser. Fortunately, since I was specifically looking for this, I caught it, and deselected these unwanted options.

    Looking into WinPatrol's history, I found that it had apparently allowed execution of some "Run-Once" item related to Avast... so I breathed a sigh of relief on that point. Memory [RAM] usage seems to be about the same as it had been under V6. And perhaps it's just my imagination, but CPU usage "feels" quieter now than it had been.

    The new V7 cloud-based services --- Streaming Updates, and File Reputation --- were showing as being enabled, and [successfully] connected.

    It appears that most, if not all, of the settings that I had set/customized in V6 were successfully transferred to V7.

    A full system scan (16.1 Gig, consisting of 71,750 files / 3915 folder) took 24.2 minutes.   EDIT:  A second scan, with Avast's "persistent cache" enabled, dropped to 19.4 minutes.

    FWIW, my wife has also updated her XP/SP3 desktop from V6 to V7, without encountering any problems either.

    Notes:   1) I have yet to test out (or interact with) the V7 auto-sandbox... I am eagerly looking forward to that opportunity.

    2) I *HAVE* encountered an "overly aggressive" V7 Behavior Shield --- which I had set to ASK; I believe the default was "auto-decide".   That's the only thing I think I really have to investigate/test further.   Aside from that, I am happy to summarize my v7 experience as:   so far, so good.   EDIT:   I have adjusted the behavior shield setting --- keeping it set to ASK ---  but UNchecking the box to "Monitor the system for unauthorised modifications" .

    3) Avast 7 allows the user to save/import their customized settings, via SETTINGS / MAINTENANCE / SETTINGS BACKUP.   Click-on Back Up Settings, see that everything is checked [unless there's something you'd actually like to exclude], then CONTINUE to SAVE the file.

    4) Finally, I'd like to stress that my latest test/use of avast v7 was done under XP/SP3, using the built-in Windows Firewall.   I am hoping that Iroc9555, who has been using v7 for over a month now --- and who has been active in the Avast forums --- will comment on his understanding of issues (if any), in terms of using avast v7 with a) Comodo Firewall under XP,  b) ANY firewall under Win7, and  c) any other problems he believes still exist, that v6 users should be aware of prior to updating to v7.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • Ky331 I am glad your expirience in upgrading Avast! was uneventful.

     

    ky331

    Upon rebooting, I was presented with a screen saying it was about to compete the upgrade process. At the bottom of this screen, in tiny writing, were two PRE-CHECKED options to install Google Chrome, and set it to be the default browser. Fortunately, since I was specifically looking for this, I caught it, and deselected these unwanted options.

    Yes this was a point very much discussed in Avast! Forums. Unfortunately most complains that Google Chrome was installed without permission, but as you saw it the window offering GC is there, small and some say a sneaky move by Avast!, but is there. There has been talk to make it bigger and even uncheck for the next Avast! version. We'll see.

     

    ky331

    The new V7 cloud-based services --- Streaming Updates, and File Reputation --- were showing as being enabled, and [successfully] connected.

    Streaming Updates and File Reputacion work for the most part flawlessly. Avast! will push even 12 updates that are not noticed unless you look for them in Avast! folders. This way Avast! keeps your system protected from the latest malware without waiting for the next mayor update. This updates files will be replaced by Avast! regular vps when doing the automatic updates.

     

    ky331

    A full system scan (16.1 Gig, consisting of 71,750 files / 3915 folder) took 24 minutes.

     
    This numbers will decrease with time. If your first full system scan was done with " Store data in persistence cache " Avast! will not scan the same files unless they have been modified one way or another making the subsequent scans to speed up, and if choosing a quick scan and using the persistance cache to speed it up the scan just last about 8 mins. I want to say that with Avast! File System Shield and Behavior Shield constantly checking files Full scans are over rated. A quick scan every week or so is more than enough to have peace of mind. I forgot to mention that Avast! will look for rootkits 8 mins after the computer is booted.
     
     
     
    ky331

    Notes:   1) I have yet to test out (or interact with) the V7 auto-sandbox... I am eagerly looking forward to that opportunity.

     
    I do not use Avast! Autosanbox but it is my opinion that it would be better if set to " ask " so that it will give you the opportunity to choose if you want a program run in sandbox. Also be aware that there is no list but a criteria for the programs to be snadboxed
     
     
     
     
    ky331

    I *HAVE* encountered an "overly aggressive" V7 Behavior Shield --- which I had set to ASK; I believe the default was "auto-decide".   That's the only thing I think I really have to investigate/test further.   Aside from that, I am happy to summarize my v7 experience as:   so far, so good.   EDIT:   I have adjusted the behavior shield setting [back] to AUTO-DECIDE.

     
    Yes, default setting for BhS is auto-decide. It was reported to be more aggressive than in version 6. I, particularly, don't feel it is, then again because I used it in conjuction to Comodo D+ and alerts do not bother me. However, Auto-decide sometimes is smarter than the user so if the user wants a quiter Avast! it is better to set BhS in Auto-decide.
     
     
     
    ky331

    4) Finally, I'd like to stress that my latest test/use of avast v7 was done under XP/SP3, using the built-in Windows Firewall.   I am hoping that Iroc9555, who has been using v7 for over a month now --- and who has been active in the Avast forums --- will comment on his understanding of issues (if any), in terms of using avast v7 with a) Comodo Firewall under XP,  b) ANY firewall under Win7, and  c) any other problems he believes still exist, that v6 users should be aware of prior to updating to v7.

     
    This is an issue bastly discussed in Avast! and Comodo Forum. It affects only Windows 7 ( 32 & 64 bit ) and Windows Firewall and Comodo firewall where trusted/white listed programs can not be blocked ( outgoing ) by either firewall because Avast! Web Shield. The three companies, Microsoft, Avast!, and Comodo, are aware of this issue and working on it. BugBatter may shine a little light this way if this issue was discussed in San Francisco in the Microsoft summit last week or so.
     
     
     
     
    As I have commented to Ky331 Avast! 7 may have started with some troubles but it has worked out most if not all its bugs. We Avast! users are awaiting for AV tests that beggins this month or next to see how version 7 comes out.
     
    A word of advise though if you intent to try Avast! 7 and you have a different AV installed be sure to use its uninstall utility before installing Avast!. Avast! 7 does not like other AVs and you can suffer from no connectivity to the web to Avast! hangs during installment.

     

    Hernan.

    Dim9200/XPS 410.C2D 2.40GHz.2GB RAM.XP Pro_86 SPk3.IE8 & FF29

    Avast!Free 9.0.2018. CIS 5.12(FW/D+). MBAM Premium. MCShield. WinPatrol +. WOT. OpenDNS. SAS(o/d)

    "We are all ignorant, but we don't all ignore the same things..." Albert Einstein

     "When you've excluded the impossible, whatever remains, however improbable, must be the truth..." Sherlock Holmes.

  •  

    Summary of my experience with --- and decision about --- the Behavior Shield:

    Since I prefer to have "hands-on" control of my system --- specifically, to avoid automatic quarantining of a False Positive --- I choose to set all of avast's shields to ASK me what to do whenever it encounters an issue.   As I keep my system clean, it rarely ever "talks" to me... except in the case of a F/P --- which I can investigate and report back to them.   The following comments are addressed to anyone who feels/does the same.   [So if you're among the people who prefer/allow your anti-virus to do everything automatically, without your interaction/approval, you should skip the rest of this post.]

    In v6, the auto-sandbox would (understandably) "kick-in" for one or two specialized/technical (=UNknown) programs that I happen to have on my system.   It was properly doing its job, and I have whitelisted that program from future sandboxing.   The v6 behavior shield also questioned "a few" programs, which I likewise "solved" by whitelisting them.

    When I upgraded to v7, it's behavior shield defaulted to "auto-decide", which, for the "control" reason I just cited, I did not want to use.   So I changed it to ASK, just like the way I set all of its other shields.   However, it was immediately apparent that this was not tenable, as it was questioning just about every program I was running.   I realize a behavior shield is a type of "HIPS program", but in my limited experience with it, it was imposing itself in situations that it shouldn't --- specifically, questioning core Windows files, and popular browsers.   I took a little time to test things, and came up with a list of programs/processes which, if whitelisted under the behavior shield, seemed to be sufficient to quiet things down.

    After concluding the testing phase, I saw three possible options from which to choose (BhS=Behavior Shield):
    1) Leave BhS on ASK, and add the many programs/processes to be trusted/whitelisted.
    2) Leave BhS on ASK, but UNcheck the box "monitor unauthorized modifications" [A setting suggested by someone in the avast forum]
    3) Switch BhS back to the default "auto-decide"

    After careful deliberation, I have decided on option (2), for the following reasons, respectively:
    1) Something is very wrong with their triggering-criteria if I have to add Windows processes (like svchost and explorer) and major browsers (IE and FF) to a whitelist.   Moreover, by whitelisting them, will that in fact allow real malware to tamper with these processes (since they will no longer be monitored by the BhS)??
    2) Even with "unauthorized modifications" UNchecked, they BhS will still be monitoring EVERYTHING --- including Windows processes and the browsers --- for low-level rootkits and malware-like behavior.   I consider this an important usage of behavioral analysis in an a-v.   
    3) The "avast forum consensus" seems to be that auto-decide has never stopped anything.   If so, it's really worthless --- the same as "allow" everything.

    As for anything that might "slip through" by UNchecking "unauthorized modifications", I trust that I can rely on WinPatrol (and/or my other layers of protection) to catch anything serious.

    Bottom line:   For those of you trying/upgrading avast 7, who prefer to have control over your behavior shield (i.e., want to set it to ASK), I would suggest you try it out that way --- cautiously --- to see how it reacts to your system (i.e., see just how "chatty" it is for you).   If it turns out that my experience is the exception --- i.e., if you find the behavior shield is quiet enough for you to work with --- then just leave it alone (set to ASK, with no modifications).   But if it turns out that yours is "overly chatty", I think the best [and simplest] solution is to follow option (2)  [UNcheck the box "monitor unauthorized modifications"].   The alternative, option (1) is to determine a list of programs/processes to whitelist on your particular system (which conceivably can differ for each user/system). 

    Please stress that, in following any of the above options, you're only impacting the behavior shield, leaving the other shields intact.   For example, the File Shield will continue to analyze files as you open/run them.

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]

  • anti virus avast for dell windows 7 profissional

  • After getting tired of the nag screens asking for renewal, updated to the free version 7 yesterday, spotting the very small pre-checked browser boxes that David warned us about. The upgrade was trouble free and the program seems to work well with Online Armor firewall which I recently switched back to.

  • Dale, glad you had no problems with your update from v6 to v7.   Hopefully, most of the issues people will encounter (e.g., the tiny pre-checked chrome browser offer) will have been discussed somewhere in this thread, so that users have been warned/informed.

    For the past two or three days, the standard "Your virus definitions have been updated" popup has been augmented to include a free offer to protect your mobile android phone.   There's a tiny box in the lower left-hand corner that you can check for "don't show this again".

    Free Internet Security - WOT Web of Trust       Use OpenDNS       MalwareBytes Anti-Malware

    Windows 7 Pro SP1 (64-bit), avast! v2014 Free, MBAM Pro, Windows Firewall, OpenDNS Family Shield, SpywareBlaster, MVPS HOSTS file, EMET+MBAE, MCShield, WinPatrol PLUS, SAS (on-demand scanner), Zemana AntiLogger Free, IE11 & Firefox (both using WOT [IE set to WARN, FF set to BLOCK]), CryptoPrevent, Secunia PSI.

    [I believe computer-users who sandbox (Sandboxie) are acting prudently.]