Windows Live OneCare is completely braindead.
When you install a new anti-virus program you expect that when it installs a base set of definitions are included and that you have at least some protection. After installation, you'd expect it to attempt to contact their update server and get the latest set of definitions and have you completely protected. This is the way most AV programs operate - Norton, McAfee, AVG.. they all do this. Not, on the other hand, Microsoft Live OneCare. A wonderfully executed product from Microsoft. Can you hear the sarcasm dripping in that statement? If not, it was.
So, the MS designers thought that instead of giving the user a basic level of protection that they'd just start you off with complete protection. Sounds good, huh? Yup, good concept, poor execution. What Live OneCare does is, start installation and then check the installation site for updates, the achilles heel being that if the site is down installation does not, and will not continue. If the site is down, of course it's not MS' fault so you have to go through their diagnostic steps of removing MSXML, .NET, disabling all startup items and non-MS services, reinstalling MSXML, reinstalling .NET and trying again only to find the same cryptic 14-80072EFE error. Which, at the time of this writing, MS does not have listed as an error code. There is a similar 14-80072EFD error code.
Great, so you're left with an unprotected computer and can't install Live OneCare because you're either not on the internet, there's a routing problem, or their installation site is down. The first two problems are out of MS' control so you wouldn't expect them to deal with them, but the last error IS under their control and they should deal with that properly. How would you deal with that properly? Hmmm, first thought would be a message stating "Sorry, the installation and activation server is down please try again later." You could even go so far as to offer to install with an old, but a base set of virus protection definitions. Producing an error code that has no knowledgebase article is senseless, it gives the user NOTHING to go on. That's the MS' solution - give an error code that blames the user and puts the onus on them to fix it.
It's never our fault.
So, the MS designers thought that instead of giving the user a basic level of protection that they'd just start you off with complete protection. Sounds good, huh? Yup, good concept, poor execution. What Live OneCare does is, start installation and then check the installation site for updates, the achilles heel being that if the site is down installation does not, and will not continue. If the site is down, of course it's not MS' fault so you have to go through their diagnostic steps of removing MSXML, .NET, disabling all startup items and non-MS services, reinstalling MSXML, reinstalling .NET and trying again only to find the same cryptic 14-80072EFE error. Which, at the time of this writing, MS does not have listed as an error code. There is a similar 14-80072EFD error code.
Great, so you're left with an unprotected computer and can't install Live OneCare because you're either not on the internet, there's a routing problem, or their installation site is down. The first two problems are out of MS' control so you wouldn't expect them to deal with them, but the last error IS under their control and they should deal with that properly. How would you deal with that properly? Hmmm, first thought would be a message stating "Sorry, the installation and activation server is down please try again later." You could even go so far as to offer to install with an old, but a base set of virus protection definitions. Producing an error code that has no knowledgebase article is senseless, it gives the user NOTHING to go on. That's the MS' solution - give an error code that blames the user and puts the onus on them to fix it.
It's never our fault.