Mon, Apr 23 2007 12:14
bradley
Dear 0x80070643:
2007-04-11 07:40:19 1716 34c Report REPORT EVENT: {5BB9F788-003E-4F24-B5DA-3052179C5C86} 2007-04-11 07:40:14-0700
1 182 101 {FC50A191-E7DF-46E3-A56D-779E48C03DDA} 100 80070643 AutomaticUpdates Failure Content Install
Installation Failure: Windows failed to install the following update with error 0x80070643: Update for Outlook 2003 Junk Email Filter (KB932330).
http://support.microsoft.com/kb/906602
Dear WU people. Or should I just call you 0x80070643? Your prime directive... of which even in the Vista era you failed, is to build an update engine that
a. Works
b. Doesn't cripple the box
c. Doesn't take a masters degree in reading error codes in order to figure out why patches aren't working.
Why can't there be a "patch installer/fixer" tool built to go into the MU plumbing, clean stuff out, give things an oil lube and help people get their MU MUing. Instead they are doing what many of my fellow CPAs are reporting that they are doing...because they can't figure out how to fix the MU reoffering of a service pack, they are shutting off automatic updates period.
How about in addition to making stuff easier.. that you make it easier for us to figure out WHY something isn't working. Self healing technologies only work so far, what we need is better error message to help us figure out why the technology isn't doing what it's supposed to do. Telling someone to go dig up their windowsupdate.log file and figure out why patches are barfing doesn't work for the masses.
Filed under: Rants
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")