knight-gkla

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About knight-gkla

  • Rank
    Member
  1. Sorry Calam, work around for update crash didn't work for me. Gon back to 7.0.2.5 again
  2. Have tried the third version of 7.0.2.6 (what a system!) but it's no help. Still using 7.0.2.5 OK
  3. Assuming your version of 7.0.2.5 updates definition files OK stick with it and don't take the software update until (at least) 7.0.2.7. 7.0.2.6 seems to have been a rouge update for many people.
  4. Try returning to 7.0.2.5 ( if you updated the software) It works fine for me on Vista Home Basic, I only get problems with 7.0.2.6 Then don't take the software update.
  5. If that's so why use ad-aware ? There are plenty of simple cookie managers out there. I use Cookie Wall ( as well as Ad-Aware 2007) on Vista and at present it's much more reliable. http://www.analogx.com/contents/download/network/cookie.htm
  6. I got it here http://www.soft32.com/download_497.html It's working fine
  7. OK I found it on the internet. I'm back in business again.
  8. where can i get free version 7.0.2.5 from until the problems of 7.0.2.6 are resolved. At least that didn't crash for me.
  9. Completed instructions. Ok except there was no .aw file anyway. When i saved the button went "dim" and file was created, save button never became available again. Restarted AAW (save button still unavailable) pressed "update " and service crashed just as before. No change that I could see. Hope this is useful.
  10. Antivirus is AVG and is active Firewall is Vista's and is active Registry Medic, Supercleaner and SpyBot installed but not active (not monitoring real-time) By monitoring services.msc the AAW service status goes blank then "starting" then "started" automatically again after 10sec (?) Updating again then produces the same symptoms.
  11. I think the update manager crashes first with a compatibility problem. here's the report Problem signature Problem Event Name: PCA2 Problem Signature 01: lsupdatemanager.exe Problem Signature 02: 7.0.2.6 Problem Signature 03: unknown Problem Signature 04: Update Manager Problem Signature 05: Lavasoft AB Problem Signature 06: 200 Problem Signature 07: -1 OS Version: 6.0.6000.2.0.0.768.3 Locale ID: 2057 Files that help describe the problem (some files may no longer be available) appcompat.txt Tab5DF0.tmp have attached first of these files appcompat.txt
  12. I have now proved this is NOT the same problem ( or at least it has different symptoms). The service crashes before downloading updates and I have to download and apply updates manually. The dump file does not seem to be available to me, the problem is reported through the Vista error handling. The only detail when the service crashes is Problem signature Problem Event Name: APPCRASH Application Name: aawservice.exe Application Version: 7.0.2.6 Application Timestamp: 477e25e9 Fault Module Name: StackHash_c87d Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000096 Exception Offset: 045636ee OS Version: 6.0.6000.2.0.0.768.3 Locale ID: 2057 Additional Information 1: c87d Additional Information 2: 4c371c328236cf95146e9a192322788e Additional Information 3: 19c8 Additional Information 4: e7fa8442378c037fc2d333150e48b10d Extra information about the problem Bucket ID: 629253363
  13. I'm not convinced this is the same error since I do not get that error message. Before update everything was fine. Since update if I ask for a definitions update I get a message saying "getting information for definitions update" then I get a Vista message which says "AdAware 2007 service stopped working and was closed". AdAware then won't work until it is forced to close manually and then restarted. I think the crash dump was handled by Vista and was sent to MS.
  14. Updated free edition to 7.0.2.6 using vista os. scan works but update crashes service then you have to close program manually. Crash report is being handled through vista problem reporting.
  15. Thanks, the command prompt was succesful but had no effect, however excluding ad-aware2007 from DEP solved the problem, although you have to do it AFTER installation of course because it doesn't exist otherwise. This would seem to be an obvious installation bug. Thanks for the help.