I have the following def's installed: SE1R51 21.06.2005, and the following core app installed: 1.06r1 Personal. When I try checking for updates it says:
When it tries to retrieve the update, it freezes at 5% and the following message appears:
How could I fix this? Any help is much appreciated.

I had the same problem also.
I just went and got the defs manually Click Here.

Let's hope that there isn't the same problem with the next definitions.

- Rawe

Otherwise you could try:

To delete the defs.ref file from
Default: C:\Program Files\Lavasoft\Ad-Aware SE Personal

and then open Ad-aware SE,

An error will be produced stating that there is no definition file or an error has occured.

Please now try an update!

If you wish not to delete it, you could rename the file:

defs.ref.old or something

Actually Andy, I did try that trick before downloading manually.
Still I got the same error..

- Rawe

Well I didn't try renaming but deleting..

Please let us know how it worked out for you Caine

Thanks to both Andy and Rawe for the suggestions.

I decided to give the renaming a whirl first before I used the manual dl (just like you did yourself Rawe), and I followed Andys advice to rename to defs.ref.old, and after the error message popped up I tried the update and it worked!

One final question however, I looked in C:\Program Files\Lavasoft\Ad-Aware SE Personal to see if the renamed defs.ref.old file was still there, and needed to be deleted. It's gone though , and now the regular defs.ref file is there instead. Was the renamed file overwritten by the current one, and if not have I done something wrong?

I don't know about that,
but it can't do any harm anyways if you have the current defs file in use for Ad-aware.
Usually defs.ref.old still stays at teh C:\Program Files\Lavasoft - folder after getting the latest one but I don't know then.
Maybe Lavasoft just had some problem with them.

- Rawe

I'm glad your problem has been solved.

The defs.ref.old file is normally in C:\Program Files\Lavasoft\Ad-Aware SE Personal



It depends how your Ad-aware is set up.

Nothing wrong on your part.

Since this issue appears to be resolved ... this Topic has been closed. Glad we could help.

If you're the topic starter, and need this topic reopened, please contact a staff member with the address of the thread.

Everyone else please begin a New Topic.