Kitz Forum

Computer Software => Security => Topic started by: oldfogy on September 20, 2006, 03:10:46 AM

Title: Ad-Aware, Corrupt Definitions file
Post by: oldfogy on September 20, 2006, 03:10:46 AM
Ad-Aware

"New definition file Build SE1R24 19.09.2006 to 19.09.2006"

This file is "POSSIBLY CORRUPT or INFECTED"

(I think it's infected as some of my passwords are now not being recognised).
(Although non of my scanners find any thing)

So make sure you save a copy of your old Def file, don't just delete it as recomended.

After re-ghosting my PC ad-aware runs okay.
But after downloading the latest update it shows as being corrupt.

I have now done this twice, so I don't see how it could not be other-wise.
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: mr_chris on September 20, 2006, 11:05:35 AM
I've just updated adaware this morning, and it seems ok. Maybe they fixed whatever the issue was?
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: oldfogy on September 20, 2006, 03:28:31 PM
Yes, it looks like they have rolled back because the update is now:
SE1R23 14.09.2006

Yesterday it was:
SE1R24 19.09.2006

I did contact Lavasoft yesterday and have received a reply today thanking me for bringing it to their attention.

There is a "Add-on" that can be DL from the Lavasoft home page to notify of a corrupt or infected definition file.
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: kitz on September 20, 2006, 04:43:08 PM
Thanks for the heads up phil :)
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: mr_chris on September 20, 2006, 05:24:28 PM
Ah, right... I haven't got that add-on - presumed mine was OK.

Sorry about that. Does this mean I'm stuck with the corrupt defs file? (without manually downloading the one from lavasoft's site of course)
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: oldfogy on September 20, 2006, 08:22:38 PM
Chris:
If you go to the Lavasoft folder in programs, the previous file will still be there and marked as.

defs.ref.old

First remove the new/current file "defs.ref"
Then remove the .old extension from the other stored file, then re-start Ad-aware.

I have also checked the latest update, and contrary to my last warning it now appears that the new/latest file is still being marked as the old faulty file.

Personally, I would be inclined to wait until the next upgrade is labelled differently from "19.09.2006"
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: mr_chris on September 20, 2006, 11:46:22 PM
Cheers for that OF - I never considered that it would make a backup of the old file, so I never looked. Pretty good idea considering :)

It's not a major problem to me as I only run ad-aware when I suspect there's a problem.. and *touch wood* there isn't at the moment :)
Title: Re: Ad-Aware, Corrupt Definitions file
Post by: oldfogy on September 21, 2006, 12:58:26 AM
Chris and all:

It's starting to look as if this may not be faulty after all.
Although some doubt still exists.

http://www.lavasoftsupport.com/index.php?showtopic=3513

Also, I now can't find any reference to the "AAWAC.EXE" Ad-aware file checker, which also may have been a "Beta" version "as mentioned in one topic".

It is also being said the the last alarm in July was also a "False Alarm"