Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OneCare recommending removing conflicting program RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    The program is Symantec Live and is only used wtih Norton Ghost which is one of my backup programs.  Does anyone know if there is really a conflict here or if Symantic Live is being targeted as it is used with Symantec's firewall and anti virus programs?  How do I get Live OneCare to quit going into the red mode because of this if I choose not to uninstall Symantic Live?  Prior to this new release there has been no problem with any conflicts regarding this program.

     

    Thanks

    Friday, December 7, 2007 5:39 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    This has been reported by a few others. There is no way to bypass this in OneCare. I don't know if it is a real conflict or a mistake on the part of the coder in identifying this component of the Norton/Symantec products as being a conflict.

    At this point, I think you might want to consider removing LiveUpdate until a solution or more information is provided here about the problem and update Ghost manually as needed.

    -steve

     

    Saturday, December 8, 2007 2:53 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Appreciate the reply.  Where is the best place to check as to whether and when this problem gets resolved.  Symantec Live has not been a problem with the older version of Windows Live OneCare so I would get it's a coding problem.  Thanks again for your comments.

     

    Trdron

     

    Saturday, December 8, 2007 9:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You're welcome. Check back here to see the status of discussion on this topic if you have chosen to remove either LiveUpdate or OneCare until there is a solution. If you leave OneCare in place, and LiveUpdate running, I suspect that a rules update/signature update in OneCare will be pushed to change the behavior and the warning will cease.

    -steve

     

    Monday, December 10, 2007 3:04 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hy!

     

    The solution to the problem is upgrading Symantec LiveUpdate to the newest version, at least version 3.4. A german guy wrote about the problem in his blog: http://newyear2006.wordpress.com/2007/12/11/live-onecare-20-und-norton-bzw-symantec-live-update-problem.

     

    You can get the the 3.4 version of Liveupdate under: ftp://ftp.symantec.com/public/english_us_canada/liveupdate/3.4/

     

    To me it seems Microsoft only tested it against the latest versions of LiveUpdate.

     

    Hope it helps.

    Tuesday, December 11, 2007 4:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The newest Norton Live Update does not solve this problem for me.  I am running Windows Vista Home Premium with all the latest updates for Windows, WLOC and Norton Ghost 12.0.  I am still running at a "At Risk" state as per WLOC.  Are there any other solutions out there?

     

    Monday, January 21, 2008 7:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    None yet. I'm hoping that the next OneCare update will resolve this.

    -steve

    Tuesday, January 22, 2008 12:42 AM
    Moderator