Hello, after many years of Adaware use and recently of SEplus, for the first time I am encountering difficulties updating the defs.ref file.
I've tried all prescribed in the "resolved issues" : checked the host file, manually updated, renamed the 17.07 to"old" and copying the manually dwnlded .ref file, deleted the old one, replaced it with the new and still:
Upon opening Adaware, it still shows the loaded definitions file as 17.07 instead of the current 18.07.
Any suggestions aside from an uninstall and re-install which I am loathe to do?

"I want my adaware"

Thanks,

ogun

I don't think it is a problem with your program. Others are having problems getting the 18th update,
AdAware update for 7-18-06
http://www.dslreports.com/forum/remark,16525170

It appears to be only slightly different from the 17th, so maybe some minor adjustment was needed. It may be a problem at the server so I notified the appropriate people to check on this.

Jane,

That was fast. Thank you very much.

ogun

You're welcome.

Hi Calamity Jane,

There have been problems updating to the new definition files recently. When updating, adaware will say there are no available definitions for update but when checking the adaware site, it would show there is a new update ready.

This has been going on since last month and there are quite a few of my friends encountering this problem. I know that there is a sticky on this subject asking us to delete or rename the defs.ref file then update but how long can we do this? Seems like lately the auto update does not work and I always have to do a manual update.

It was mentioned on the sitcky topic that it might be due to malaware or spyware infection on the system but I had adaware for a few years on my system and why was I infected if that was the job which was adaware was supposed to do anyway?

Hope we can get an answer on this and most importantly why the auto updates do not work. Find it hard to beleive that it might be a user system issue due to the number of people affected.

Yours sounds like a different issue if it has been going on for a month. Ogun's topic here refers to a glitch in the update for the 18th posted, but showing unavailable. - that update following the successful download of the update released on the 17th.

zman, do you have the latest version (build) of Adaware? See the note:
http://www.lavasoftsupport.com/index.php?showtopic=1163

Adaware is an Antispyware Product. It is not an Antivirus/AntiTrojan product. Therefore, yes, malware infections can interefere with it's proper functioning. Also, some folks download Adaware onto an already infected system and have problems - in that case an existing infection can interfere. That is why the sticky topic addresses that aspect. We have to cover a wide range of possible scenarios on all operating systems, so not all may apply to your case.

ogun,

The problem with the 18th updates has been fixed. LS Stoffe states:

I have tried to download the updates twice using the Ad Aware updater. Both times, the authenticity checker alerted that the definition file had been compromised. I just now downloaded it direct from Lavasoft in a zip file and installed it. Now I get the same message from the authenticity checker. I am somehwhat sure I don't have a trojan on my PC, at least Ewido, A-Squared, Pest Patrol and Windows Defender don't find one. Is there something wrong with the update package itself?

LS SteveJ could answer any questions better than I regarding the Authenticity Check, however, since the program is still in Beta, I expect bugs have not all been ironed out.

The details of the latest update reference file is:

Definitions File Loaded:
Reference Number : SE1R115 18.07.2006
Internal build : 138
File location : C:\Program Files\Lavasoft\Ad-Aware SE Personal\defs.ref
File size : 727672 Bytes
Total size : 2367049 Bytes
Signature data size : 2318729 Bytes
Reference data size : 47808 Bytes
Signatures total : 64731
CSI Fingerprints total : 3319
CSI data size : 122786 Bytes
Target categories : 15
Target families : 951

MD5: 69BE756EBA6665E9C698D859082BB0E7
SHA1: 89D3EEA96F6D2D735833BB25A75C07A8DC34A0E9
CRC-32: C11E17FF

You can file bug reports on the Authenticity Check in this thread:
http://www.lavasoftsupport.com/index.php?showtopic=74

I am also having this same problem with the Authenticity Check which did not happen until the 138 build of the def 115. sly

Hello, sly

Others are reporting the same problem. It's a beta program (which means it isn't finished yet). Please click on this link:
http://www.lavasoftsupport.com/index.php?showtopic=74
And file your report in that thread

Can you still use Ad-Aware even if you are getting this error about your definitions being compromised? I believe they are still good because I just downloaded them and reopened the program when I get the error. sly

Today I deleted the defs.ref and updated to R115 build 138 and with the Authenticity Checker installed DID NOT get the message that my files had been compromised. Everything is great now. I did the same thing yesterday and it did not work, guess I was getting a corrupted file or something. sly

Glad to hear you got it resolved, Sly

Just remember that the authenticity checker is still in Beta and any problems encountered should be reported in the forum here:
http://www.lavasoftsupport.com/index.php?showforum=58

There you will also find if others are reporting similar issues