locked
Tune-Up Report Errors RRS feed

  • Question

  • Windows Vista Ultimate

    I have these errors every week after OneCare 2.0 BETA Tune-up is run.

     

    1.  Remove unncessary files - This task was not performed becasue of an unknown problem.  Try running Tune-up again.

    2.  Defragment the hard disk - An unknown error prevented Tune-up from performing this task.  Try running Tune-up again.

     

    I looked in the Event Viewer logs and there are no error messages.  Application, System, Security and the OneCare log.  Just informational messages about successful virus and spyware scans and updates.

     

    I do have a 3rd party defrag program that loads with Windows (O&O Defrag).  Perhaps there is a conflict here?

     

    I also clicked on the links for "contact support" and "contact help center" in the Tune-up report and they took me to

    "page cannot be displayed" web pages.

     

    Any ideas?  Known issues?  I know OnceCare 2.0 is going live soon.  I hope these issues get fixed.

     

     

     

    Monday, October 1, 2007 1:47 PM

Answers

All replies

  • The first item, cleanup files, is a known problem, though we haven't heard what the cause might be.

    The Defrag item is also a known problem in that Defrag only runs for a limited time in Tune-up and then stops. If it doesn't manage to perform a full pass, it reports that it has failed. However, I was under the impression that this had been changed with the recent update to 2.0.

    I'd file a bug and feel free to contact support.

    http://help.live.com/help.aspx?project=onecarev2 -use the "Get More Help" link in the lower right of the page to contact support via email.

     

    Please file a bug on Connect:  https://connect.microsoft.com/site/sitehome.aspx?SiteID=168

    See the Bug Submission Guide - http://connect.microsoft.com/content/content.aspx?ContentID=3480&SiteID=168 - for details on how to create and submit the Support Log zip file with your bug.

    -steve

    Monday, October 1, 2007 5:33 PM
    Moderator
  • Thanks for the info ... looks like known issues.

     

     

    Monday, October 1, 2007 7:15 PM
  • Yes, I believe so. Hang in there and hopefully we'll see them cleared up in a future release. If you can file a bug with your support logs it would help identify the cause.

    -steve

     

    Tuesday, October 2, 2007 12:57 AM
    Moderator