tomkieffer

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tomkieffer

  • Rank
    Newbie
  1. Final clarification:[b]After REBOOTING[/b] From the Ad-Aware window click on Ad_Watch > Settings > click Processes Protection > click OK Now all is working fine with ver 9.5 I'm running XP Home Edition SP3
  2. I should clarify : Ad_Watch Live [b]PROCESSES[/b] is not on as it was in rel 9.0.7
  3. [quote name='CeciliaB' post='129027' date='Aug 26 2011, 02:33 PM']Hi tom kieffer, I'm not sure if you downloaded the installation file on the web page that was displayed. Due to major changes in the program you have to download 9.5 manually and start the installation yourself.[/quote] It is ver 9.5 downloaded from CNET. I had to manually remove 9.0.7 thru Control Panel > Add/Remove Programs and then install. It does a long 72mb update and runs fine. Only oddity is now Ad-Watch Live doesn't engage the "real time protection" like it has before. Tried the option settings but can't get it to come on. Perhaps that has been removed from the FREE version. Hmmmmm
  4. all of a sudden today Ad-Aware 9.0.7 tells me it's out of date and has another update now screen. WTF is going on. This update while it looks like an update still shows as being ver 9.0.7 (About). There must be a new programmer on staff this week. This really isn't a great way to promote the product and expect folks to upgrade to Ad-Aware Pro.
  5. tomkieffer

    web update

    Good news!!! Apparently the connection problem is fixed and was the server and not the users. I also noticed that the updates are once again fully catching up a user with ALL the available updates and not one at a time as I was noticing since upgrading to ver 9.
  6. [quote name='CeciliaB' post='128243' date='Jul 14 2011, 12:47 PM']Hi tom kieffer, Are you sure that everything from Windows Update is installed? This behaviour has been observed when the Windows certificates are out of date and the latest Lavasoft certificate is only a few months old. Please, visit Windows Update with Internet Explorer.[/quote] Well I'll be darned ..... had seven (7) optional updates available so I selected them all and voila, problem solved. I will post the link for others who like me probably only have "critical" updates automatically applied. This also solved another minor screen problem (certificate related) I have had with another piece of software. Thanks ever so much!!! MS update link: [url="http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us"]http://www.update.microsoft.com/microsoftu...t.aspx?ln=en-us[/url]
  7. [size=3]I am having the same problem with Thorax.aaw that has been described and fixes and work-arounds also put out here. Not working for me either. Runing XP SP3, Ad-Aware 9.0.7. AVG anti-virus. I've shutdown AVG, tried the "Exit Ad-Aware, run update from Start/Lavasoft/Ad-Aware/Ad-Aware Update ...... No luck .... Thorax.aaw flashes and then dies. Also tried the process immediately after reboot, no luck. Uninstalled and reinstalled a few times and manually downloaded core.aawdef and still no luck. I've got plenty of time to help debug or whatever is required to resolve this issue. I'm sure others have it and are just ignoring it until it's fixed ...... well, that doesn't seem to be forthcoming. [/size]
  8. [quote name='maps3333' post='128191' date='Jul 12 2011, 09:23 PM']i have 9.07 running on Windows XP64 and does the same thing. I did notice that the update starts then AAW closes/crashes after the update gets to thorax.aaw.[/quote] I am having the same problem with Thorax.aaw that has been described and fixes and work-arounds also put out here. Not working for me either. Runing XP SP3, Ad-Aware 9.0.7. AVG anti-virus. I've shutdown AVG, tried the "Exit Ad-Aware, run update from Start/Lavasoft/Ad-Aware/Ad-Aware Update ...... No luck .... Thorax.aaw flashes and then dies. Also tried the process immediately after reboot, no luck. My last good update was 7/5/11. I've got plenty of time to help debug or whatever is required to resolve this issue. I'm sure others have it and are just ignoring it until it's fixed ...... well, that doesn't seem to be forthcoming.