OneCareCleanUp_exe - No documentation RRS feed

  • General discussion

  • Posting this tool with no documentation as to what it will do is neither proactive support response, nor helpfull to the end user community. Incomplete registry cleanup is worse than no cleanup at all.


    A few weeks ago the version 2 software was finally pushed onto my computer. In the process of installing it locked up the system, and when it finished I was unable to shut down the system, or reboot in the normal fashion. Ultimately resulting in a failed install and an unstable system. It worked fine on my laptop, but screwed up my desktop machine to the point that it required a clean install.


    The "Team" is in strong need of Customer centered leadership. Live OneCare has bastardized the Beta testing process in selling a product for the last 24 months that should have been solid and stable. Now Live OneCare has fouled up the Windows Automated Update system. Out of sequence and partial installs of .Net corrupted the Clean Install process, and crashed a perfectly stable system.


    Pushing the "Circle" concept and opening multiple "Hub" (another ill defined term for providing another open port) does not appear to add any real value to the product. It may provide some minimal reduction in update activity at the Microsoft update site by pushing updates to a hub for further distribution to two circle client installations.


    Keep up the current stategy with this product and you will see your customer base melt away in short order.



    Thursday, January 17, 2008 5:39 PM

All replies

  • I agree that some detailed information on what the cleanup tool does would be helpful for some and I also think that the tool needs to be better at removing *all* traces of OneCare from a system. As you noted, it does leave some registry keys behind. I don't think that's worse than no tool, though, as those keys are harmless and I'm only aware of one program that had problems installing because it incorrectly detected OneCare by seeing a leftover key.


    I'm sorry that you had problems with the upgrade.


    I'm not sure I understand your point about the Windows Automated Update system. I suspect that you ran into a problem where Windows Update pushed a security update for .Net Framework that in some cases has caused problems for OneCare in this upgrade. I don't see how OneCare was responsible for this, though.


    The Circle and Hub does not open any ports that I'm aware of, but I could be wrong. OneCare communicates to the servers and always has. That status is not pushed back to the Hub to update the status and can be pushed from PC to PC on a local network. I beg to differ in opinion - I think that the OneCare Circle is a great idea and will likely be expanded upon going forward. Having a central management point for multiple PCs in a home for security makes sense. In fact, your suggestion for Windows Updates using the Circle functionality is a interesting concept, though not one I'd expect to be implemented soon. I wouldn't want OneCare to have to run a full WSUS database on a home network - that would be overkill.


    Thanks for your feedback - even the negative. OneCare needs to continue to improve.




    Thursday, January 17, 2008 8:02 PM