You know what I'm sick of?

I'm sick of having to jump through hoops trying to implement windows updates.
If you get this error code, then try these solutions. Why are there any error
codes in the first place? Why can't Microsoft get it's act together and sort
these issues out.

I mean, it's pretty absurd having a fix like "Stop the Automatic Updates
service, delete the SoftwareDistribution folder and then try to update again"!

AMEN!


"Frustrated" <> wrote in message
news:016DD08A-FE8A-42EA-ADCB-...
I'm sick of having to jump through hoops trying to implement windows
updates.
If you get this error code, then try these solutions. Why are there any
error
codes in the first place? Why can't Microsoft get it's act together and sort
these issues out.

I mean, it's pretty absurd having a fix like "Stop the Automatic Updates
service, delete the SoftwareDistribution folder and then try to update
again"!

"Frustrated" <> wrote in message
news:016DD08A-FE8A-42EA-ADCB-...
> I'm sick of having to jump through hoops trying to implement windows
> updates.
> If you get this error code, then try these solutions. Why are there any
> error
> codes in the first place? Why can't Microsoft get it's act together and
> sort
> these issues out.
>
> I mean, it's pretty absurd having a fix like "Stop the Automatic Updates
> service, delete the SoftwareDistribution folder and then try to update
> again"!

I venture to suggest that the problems you are experiencing do not occur for
most users, certainly I do not have problems updating my systems (3).
Perhaps it is time to fix your setup and stop whinging!

Ah edward, while i agree that frustrated is blowing off steam, your comment
is absolutely inaccurate. I venture to suggest that 45% of this site is
devoted to that one subject. I also have multiple systems, multiple OS's,
have used computers every work day since the late 70's (altair), write C a
lot, and also find SP2 "clunky" to install. But if you want to prove you're
superior...take a crack at the root cause to my complaint on this board a few
months ago, search on zanex and you'll find it
NSZ

"Edward W. Thompson" wrote:

>
> "Frustrated" <> wrote in message
> news:016DD08A-FE8A-42EA-ADCB-...
> > I'm sick of having to jump through hoops trying to implement windows
> > updates.
> > If you get this error code, then try these solutions. Why are there any
> > error
> > codes in the first place? Why can't Microsoft get it's act together and
> > sort
> > these issues out.
> >
> > I mean, it's pretty absurd having a fix like "Stop the Automatic Updates
> > service, delete the SoftwareDistribution folder and then try to update
> > again"!
>
> I venture to suggest that the problems you are experiencing do not occur for
> most users, certainly I do not have problems updating my systems (3).
> Perhaps it is time to fix your setup and stop whinging!
>
>
>

"Frustrated" <> wrote in message
news:1A4F71D9-D335-41CE-BF38-...
> Gee thanks Edward. That was a really helpful comment. Beats me why people
> like you bother responding to posts like this when you've got nothing
> worthwhile to contribute.
>
> If you'd care to look furhter than then end of your nose, you'd see that
> many users have problems with doing a windows update - just search on a
> few
> of the error codes and you might have a bit of a clue.
>
> "Edward W. Thompson" wrote:
>
>> I venture to suggest that the problems you are experiencing do not occur
>> for
>> most users, certainly I do not have problems updating my systems (3).
>> Perhaps it is time to fix your setup and stop whinging!
>>
I'm sorry you don't think my response is worthwhile. Although I could and
perhaps should have been a little more diplomatic, your problem is almost
certainly not with WINXP but with what you have surrounded the system with,
that is incompatible software and even, perhaps incompatible hardware.

It is not MS responsibility to work around third party software or hardware.
It is the responsibility of those who design software and hardware to
function with WINXP to insure that it does exactly that. Unfortunately MS
seems to be the fall Guy when suppliers do not observe the 'rules'..

As far as I am concerned the popular proposition that problems with the OS
occurs due to the innumerable variations between systems is not tenable. If
all software and hardware were fully compatible with the OS no conflicts
will occur as a common standard would prevail. If you care to put this to
the test, reformat your system, load WINXP SP2 and now update with all the
various updates and patches and see whether you now have problems. If you
do then I will agree with you that the OS is the problem but if you do not,
and I am confident you would not have a problem, then I think it
demonstrates my point.