IDNetters Forums

Technical News & Discussion => Windows News & Discussion => Topic started by: Noreen on Dec 03, 2009, 10:43:15

Title: Avast! bad update 12.02.2009
Post by: Noreen on Dec 03, 2009, 10:43:15
From another forum. Apparently it doesn't affect all machines.
QuoteDSL Reports Security forum is full of problem reports with the latest avast! update. It appears to be flagging numerous files as infected.

The avast! forum is nearly unreachable due to heavy demand.
Title: Re: Avast! bad update 12.02.2009
Post by: Rik on Dec 03, 2009, 10:48:10
Thanks, Noreen. I wonder if it's related to the 'black screen' problem?
Title: Re: Avast! bad update 12.02.2009
Post by: Gary on Dec 03, 2009, 11:11:35
Quote from: Rik on Dec 03, 2009, 10:48:10
Thanks, Noreen. I wonder if it's related to the 'black screen' problem?
Is this black screen thing still going on, Rik?
Title: Re: Avast! bad update 12.02.2009
Post by: Rik on Dec 03, 2009, 11:16:28
I've not seen any fresh reports, Gary.
Title: Re: Avast! bad update 12.02.2009
Post by: Gary on Dec 03, 2009, 11:30:42
Quote from: Rik on Dec 03, 2009, 11:16:28
I've not seen any fresh reports, Gary.
Thats good news, still very odd though, i would like to know what Prevx's fix actually did  :dunno:
Title: Re: Avast! bad update 12.02.2009
Post by: kinmel on Dec 03, 2009, 12:22:57
Quote from: Gary on Dec 03, 2009, 11:30:42
Thats good news, still very odd though, i would like to know what Prevx's fix actually did  :dunno:

Apparently nothing................. according to today's Telegraph         

  The company that initially highlighted the fault, Prevx, said that Microsoft's own security updates – code-named KB976098 and KB915597 – were probably responsible for the issue, but has since admitted that they were mistaken, and issued an apology.
Title: Re: Avast! bad update 12.02.2009
Post by: Gary on Dec 03, 2009, 13:59:25
Quote from: kinmel on Dec 03, 2009, 12:22:57
Apparently nothing................. according to today's Telegraph         

The company that initially highlighted the fault, Prevx, said that Microsoft's own security updates – code-named KB976098 and KB915597 – were probably responsible for the issue, but has since admitted that they were mistaken, and issued an apology.
So they released a fix that was a placebo? Can't see Prevx doing that, they are a pretty good security company and Prevx works pretty well on Windows, that would really tarnish here reputation  :dunno:
Title: Re: Avast! bad update 12.02.2009
Post by: Noreen on Dec 03, 2009, 17:16:24
Avast problem fixed. http://forum.avast.com/index.php?topic=51647.0
Title: Re: Avast! bad update 12.02.2009
Post by: Rik on Dec 03, 2009, 17:22:12
Thanks.  :thumb:
Title: Re: Avast! bad update 12.02.2009
Post by: john on Dec 03, 2009, 18:07:00
Thanks Noreen, I was affected by the update but I think everythings been restored okay now  :thumb:
Title: Re: Avast! bad update 12.02.2009
Post by: Glenn on Dec 03, 2009, 18:16:46
My P, with Avast, seems to update its virus database at least 3 or 4 times a day.
Title: Re: Avast! bad update 12.02.2009
Post by: bobleslie on Dec 03, 2009, 20:11:02
Quote from: Gary on Dec 03, 2009, 13:59:25
So they released a fix that was a placebo? Can't see Prevx doing that, they are a pretty good security company and Prevx works pretty well on Windows, that would really tarnish here reputation  :dunno:

It appears as if they're still wriggling (http://www.theregister.co.uk/2009/12/02/black_screen_u_turn/).
Title: Re: Avast! bad update 12.02.2009
Post by: Rik on Dec 04, 2009, 10:57:13
Wouldn't you if MS had its hooks in you. Oh wait, we all do. ;D