locked
OneCare Failure To Update RRS feed

  • General discussion

  •  

    My OneCare has been stuck on version 2.0.2500.14.  I just discovered yesterday that a newer version was available.  I was under the impression that OneCare updated automatically. 

     

    I made a service request to Microsoft concerning the failure of OneCare to properly update.  I reported to them that my current version was 2.0.2500.14 and that it was displaying a green status.

     

    They responded, “I would like to tell you that if the status of Windows Live OneCare is green, it is working properly and the computer is safely protected.

     

    I went ahead and uninstalled the old version and downloaded the new version (2.5.2900.15).  I asked why the old version failed to upgrade and I got no response.  I asked if the new version would upgrade properly and got no response.  I asked a number of other questions concerning this problem and got no response.

     

    Bottom line is that I had to troubleshoot and correct the problem myself.  Microsoft support was not at all helpful

     

    I had to make three separate requests before they would even reply to me.  Microsoft support sucks!

    Saturday, October 11, 2008 8:38 PM

All replies

  • I am sorry to hear that you had an unsatisfactory support experience. The answer that "if One Care is green, it is working properly" is correct. A little more detail would have been more helpful to you. Minor updates like .14 to .15 are usually not end user critical. These are very minor updates which  can be something like correcting the grammar in a help file or cleaning up some code and do not affect performance or level of protection in One Care. This type of update, because it is not critical, is usually rolled out gradually not universally like a definition update would be.

    Sunday, October 12, 2008 6:04 PM
    Moderator
  •  JimR1 wrote:

    I am sorry to hear that you had an unsatisfactory support experience. The answer that "if One Care is green, it is working properly" is correct. A little more detail would have been more helpful to you. Minor updates like .14 to .15 are usually not end user critical. These are very minor updates which  can be something like correcting the grammar in a help file or cleaning up some code and do not affect performance or level of protection in One Care. This type of update, because it is not critical, is usually rolled out gradually not universally like a definition update would be.

    I suggest you read my OP again.  It was not a "minor update".  It was a major version change from version 2.0.2500.14 to version 2.5.2900.15.  My esitmate is that I had been running the old version for about 8 months with no updates!  Yet OneCare was set for auto update and was going out to the Internet to download updates.  Those updates never "took" on my system.

     

    For some reason (I suspect a major software failure that Microsoft doen't want to acknowledge) OneCare kept reporting a green status.  In fact, my system was obviously not getting the full protection for which I had paid.

     

    Because of the obvious liability implications, Microsoft will not admit an error.

    Sunday, October 12, 2008 6:53 PM
  • I'm sorry I mis-read your original post. That certainly was a major update and you should have been in "at risk" status. Regarding "Microsoft will not admit an error" read this - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=3008806&SiteID=2 This update issue affected a small number of users and the One Care team acknowledged it and requested information from affected users.

    Sunday, October 12, 2008 9:14 PM
    Moderator
  •  

    If your copy OneCare is anything older than the current 2.0.2500.22 and your status is Green, Microsoft would like to hear from you.

     

    Open OneCare, click Help/About to see your program version.

     

    Please send an email to the OneCare team at wloc@live.com with your name and contact information.

     

    If possible, attach your support log to the email for review. See this post for how to create the onecaresuppordata.zip file: http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2512403&SiteID=2

     

    Use a subject line of "OneCare Old Version No Upgrade" when sending the message.

     

    Note that not everyone submitting an email will be contacted.

     

    Thanks!

    -steve

     

     

    Yes indeed, I saw that post from Steve (thanks Steve) and I followed the instructions to the letter.  I sent several responses along with the support log zip file for each computer I had that suffered from this problem.  I never heard anymore about the problem.

     

    To my knowledge, Microsoft never addressed this problem nor did they explain what happened.  They never responded to any of my requests for help until I opened up a formal case incident which forced them to assign a case number.

     

    The case worker never acknowledged that the situation I described was in any way a problem.  He stated, I would like to tell you that if the status of Windows Live OneCare is green, it is working properly and the computer is safely protected.”  He further stated that, “I understand the inconvenience you have experienced.”  He tells me this knowing that I have been running version 2.0.2500.14 during the past several months and that it won’t update! 

     

    He then went on to suggest that I uninstall the old version and reinstall the new version.  Well, I had already figured that out by myself and I downloaded and installed version 2.5.2900.15 a day before he contacted me!  When I asked him what had caused the problem, he refused to answer and closed out the case!

     

    This is not support in my book, but it sure looks like a cover-up. 

    Monday, October 13, 2008 12:34 AM
  •  Bob Tom wrote:

     

     

    Yes indeed, I saw that post from Steve (thanks Steve) and I followed the instructions to the letter.  I sent several responses along with the support log zip file for each computer I had that suffered from this problem.  I never heard anymore about the problem.

     

    To my knowledge, Microsoft never addressed this problem nor did they explain what happened.  They never responded to any of my requests for help until I opened up a formal case incident which forced them to assign a case number.

     

     

     

    The last line in Steve's post would explain why you did not get a response from Microsoft - "Note that not everyone submitting an email will be contacted." and if you already read Steve's post which has been pinned in the forum for seven months how can you say Microsoft has not acknowledged this issue?

    Every support request is assigned a case number so I don't understand the point you are trying to make. Support did the job they are supposed to do which is to resolve your issue. It is not their job to report to you the status of bug fixes or what exactly is unique to a small number of computers which might cause an update failure.

    Monday, October 13, 2008 2:13 AM
    Moderator
  •  JimR1 wrote:

    Every support request is assigned a case number so I don't understand the point you are trying to make. Support did the job they are supposed to do which is to resolve your issue. It is not their job to report to you the status of bug fixes or what exactly is unique to a small number of computers which might cause an update failure.

    Support did not resolve the issue.  I uninstalled the old software and reinstalled the new software before support even responded.  As a fully paid up subscriber, support has a duty to make sure that my software product is functioning properly.  They failed in that responsibilty.

     

    My software was broken for many months but was still reporting that everything was working properly.  Was it my fault?  How would I know?  Support has not bothered to inform me what caused the problem.  But according to you, that's none of my business.

     

    Most forums are designed to solve problems not hide them.

    Monday, October 13, 2008 2:31 AM
  • The only 'Problem' not resolved is your own frustration, since the real functional issue has been resolved by the exact method provided by Support, which is all that front level Support is designed to do. They do not escalate or attampt to explain the exact reason for success, they simply attempt to help return OneCare on your PC to a working state.

     

    No organization is ever required to explain the exact reason a particular fix works, that's something you've decided to state as a requirement. As more technical users, we MVP Moderators often do our best to explain situations when we understand them, but that's not an official statement from Microsoft, just our best guess or knowledge from our own testing.

     

    Since this issue is apparently quite rare and none of us have ever experienced it ourselves, we are unable to state a specific reason for the core issue. For this reason, unless someone else who has experienced the issue took the time to investigate it deeply before re-installing, it's unlikely we will ever know.

     

    I think it's safe to assume something in the update system of either OneCare or Windows itself became 'latched' into a state where it appeared to respond as working, but was actually not communicating with the OneCare servers correctly at all. Since the OneCare development team took the step of placing a post in the Forums to attampt to identify anyone having this issue, that seems a reasonable course of action.

     

    OneCareBear

    Monday, October 13, 2008 5:22 AM
    Moderator
  • I'll simply add that if you can provide the support case numbers, I'll ask for support management to review them. The cases should not have been closed by support and they should have at least had you reinstall to get you to the latest version.

    The reasons for why an installed copy of OneCare remains stuck at an older version are unknown to me - it could be a server/subscription issue, it could be a local problem on the PC with something about OneCare that reports itself to the servers as a version other than what it actually is, or a failure to communicate at all. The latter would be unlikely as it would also lead to a problem with signature updates being out of date.

    I can be reached at sboots@mvps.org - make sure that the subject includes "OneCare" to pass my spam filtering and include this link in the message body along with the support case ID(s). http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=3989881&SiteID=2

    -steve

     

    Monday, October 13, 2008 4:48 PM
    Moderator
  •  

    I want to thank you Stephen for your willingness to help resolve this matter.  I have already contacted management in Redmond, WA and have been assigned an incident investigator who has resolved most of the problems.

     

    As I suspected, OneCare was indeed broken as evidenced by the support data zip file that I submitted.  Rudimentary tests and analysis by the investigator narrowed the problem down to the servers being unable to properly identify my outdated version.  The supposition in your reply was absolutely correct!  I wish I had heard from you earlier.

     

    Monday, October 13, 2008 7:29 PM
  • You're welcome. I hope that the information learned from your cases will be used to improve support's available knowledgebase so that they can deal with the issue appropriately in the future.

    -steve

     

    Tuesday, October 14, 2008 4:16 PM
    Moderator