Another problem with Avast

Discussion in 'ProcessGuard' started by JimTheMuso, Dec 22, 2005.

Thread Status:
Not open for further replies.
  1. JimTheMuso

    JimTheMuso Registered Member

    Joined:
    Mar 14, 2005
    Posts:
    25
    Location:
    Ashford Kent UK
    A few minutes ago I had a failed update messge from Avast. When I checked the alerts in PG I had:
    avast.setup was allowed to start
    8 seconds later avast.setup was blocked from starting and setup.ovr was blocked from starting. Both these have almost everything allowed in PG and an update has already been successful today with nothing changed since. Any ideas please?
    Jim.
    P.S A manual update just gave the same result. I haven't queried this with anyone on the Avast forum as PG said it blocked it so thought I should start here.
    P.P.S. Wife is using laptop at same time and update was fine there only a couple of minutes later.
     
  2. WSFuser

    WSFuser Registered Member

    Joined:
    Oct 7, 2004
    Posts:
    10,632
    go to wherever those files are located and manually create a fake avast.setup file (just rename a text file or something). add it to pg's protetion list and give it whatever rights it needs. then just delete the fake file and try updating avast
     
  3. vlk

    vlk AV Expert

    Joined:
    Dec 26, 2002
    Posts:
    618
    It's just worth adding that this is a "program update" - instead of a much more common "virus database update".

    A "program update" roughly consists in avast.setup connecting to the Internet, downloading a new version of the setup, killing itself and running the new avast.setup just downloaded (i.e. MD5 checksum) changes and consequently downloading other packages and applying them to the existing installation...

    In other words, if PG is checking MD5 of the file, it will detect a change...
     
  4. JimTheMuso

    JimTheMuso Registered Member

    Joined:
    Mar 14, 2005
    Posts:
    25
    Location:
    Ashford Kent UK
    So, if I get a red failure again, then put PG into learning mode and update Avast manually, it should solve the problem as the new program will have been allowed to start?
     
Thread Status:
Not open for further replies.