Windows Live OneCare and Ad-Aware 2007 incompatibility issue

There are unhappy users of Windows Live OneCare because they received a "At risk" status report by OneCare due to incompatibility of WLOC with Ad-Aware 2007 (free or paid editions).  The post by winchester73 over at Lavasoft forums has a screenshot. 

Member DHoppus over at OneCare forums posted the below information when he clicks the link from OneCare alert: "Why un-install Ad-Aware 2007?"

Ad-Aware 2007 (free version) is a 'manually selected' scanner for adware. It has identified-and-removed adware which was undetected by WLOC and Windows-KB890830-V1.37.exe

Note that Windows-KB890830-V1.37.exe is the free Windows Malicious Software Removal Tool by Microsoft.

I'm using Windows Live OneCare on XP Pro.  The system has the following antispyware modules or programs:

  1. Ad-Aware 2007 Free
  2. Spybot Search & Destroy
  3. WinPatrol 2007

The version of Live OneCare on the said system is v2.0.2500.22:  OC

I installed Outpost Firewall Pro v4 in XP to replace OneCare's firewall (OT:  I was using Outpost Firewall 2008 in Vista SP1 but I have to remove it because the afw.sys firewall driver by Outpost Firewall 2008 has big issue -- it keeps crashing the system, giving me non-stop BSOD.  Debugger tool said the probable cause is afw.sys.  Anyway, I have Comodo Firewall Pro now on Vista SP1 and so far... I like it because it's a rule-based firewall. No crashes. No BSOD.)

I have a red status from OneCare center because I changed today the settings to use Outpost Firewall Pro v4 as my firewall software and I changed the AU settings to "Notify me for Microsoft updates":

scxppro   ocstatusreport

As you can see from the above screenshot, Ad-Aware 2007 Free, Spybot S&D, WinPatrol and Outpost with Antipsyware plugin are running but OneCare did not alert me on incompatibility of OneCare with Ad-Aware 2007 or with the other running antispyware and firewall programs.  What OneCare says is AU is not set to automatic and OneCare firewall is off - that's TRUE.  The Windows Security Center reports Outpost Firewall Pro, OneCare are on - that's TRUE.

While AFFECTED WLOC users are waiting for explanation or fix from Microsoft, I recommend to NOT to remove Ad-Aware 2007 or OneCare.  Don't worry if you see the red status as long as you are aware why it is RED.  There is NOTHING wrong in running both (based on my experience on the said programs).  I've restarted the system many times already and even turned it on/off... and I have not receive information from OneCare center that I should remove Ad-Aware 2007.  Maybe it's just a glitch when Microsoft rolled-out the updated OneCare.  (I'm saying it's maybe a glitch because.. how come I don't see that incompatibility alert by WLOC on Ad-Aware 2007 Free on my system?).

Many software now runs Software as a Service (SaaS) and it's common that security tool will whine on another service by another security tool.  If it's not giving you problem or system instability.. keep what you like to keep.  That's your system.  Just be aware on what you are running.  I'm NOT saying to always IGNORE any RED warnings.  Until the vendor/s fixed their issue, just calm down.  You know what is happening and that is important. Submit a support ticket to Microsoft so they'll fix this -- if it's really a glitch... when the said WLOC update was first rolled out end of Jan. 2008.

What is NOT recommended is to enable and run more than 2 antivirus and firewall software.  Just choose 1 software firewall and 1 antivirus as your real-time protection against malicious activities.  For antispyware, run more than 1.  Other free and good antispyware or antimalware programs are:

Update:

 

 MS-MVP Corrine Chorney has some thoughts on her online journal on the above topic and on the blog post by LS:

http://securitygarden.blogspot.com/2008/02/lavasoft-addresses-conflict-with.html

LS staff made a comment on Corrine's blog entry:

We are not objecting to the practice that LiveOneCare prompts the user to remove a program that will cause a conflic.
It's the practice that they do this regardless if the other software is causing a conflict or not, it's just because there is a 'security' software installed and that it is a competitor to LiveOneCare.

Running Ad-Aware 2007 Free should not cause any conflict with OneLiveCare according to tests run by Lavasoft.
The only time a problem occurs is when you are running the realtime protection features of Ad-Aware 2007 Plus/Pro (Ad-Watch), at which point LiveOneCare might terminate prematurely. This is the only reported software conflict between the two programs.

Jona Bolin
Lavasoft AB

I'm seeing a correct experience then.  It is why I'm not seeing issue with the copy of OneCare and copy of Ad-Aware Free on XP Pro system.  But hey Lavasoft, there's Ad-watch component (e.g. GUI) in the free edition but cannot be enabled on free edition. That is maybe why MS decided to also recommend to some affected users to remove Ad-Aware free?

Look at calendar entries of updates on Ad-Aware 2007 free at Calendar of Updates.  Screenshots provided by CoU member Paul is a free edition of Ad-Aware 2007 and this free edition also receives updates for Ad-watch.

And since they've confirmed a conflict between paid edition of Ad-Aware and OneCare, then the vendors need to fix this issue.  Some users of Free edition of Ad-Aware is seeing the alert on incompatibility.  That needs to be investigated more by LS especially if WLOC will shutdown due to Ad-watch.  I think it's LS team who should the fixing job! (now that they confirmed Ad-watch can terminate WLOC)

Published Fri, Feb 15 2008 23:55 by donna

Comments

Saturday, February 16, 2008 11:11 AM by Donna's SecurityFlash

# AVG working on fix on AVG Antispyware & Windows Live OneCare issue

Thanks for the link provided thru email by a frequent reader.... after reading my blog post on OneCare

Monday, February 18, 2008 7:46 AM by JRElliott

# re: Windows Live OneCare and Ad-Aware 2007 incompatibility issue

Seems to me that if Ad-Aware 2007 "can terminate WLOC" then some other arbitrary program (a virus-infected one, for example) could also terminate WLOC. If that's the case, WLOC is insufficiently durable and it's Microsoft that needs to be doing the fixing job.