Before I bite into Microsoft again, I will credit Kaylene with an exceptional
corporate mentality and also endless personal patience. Were I her, I would
have told Microsoft to shove it days ago after having to constantly placate
poorly informed consumers and answer the same questions over and over and
over again. That said...
Gee, a superb passive-aggressive response to tell me I can update when I
feel ready. Again and most unfortunately, the *tremendous* respect and
admiration I long had for Microsoft MVPs has been blown to BITS (pun
intended) with their "circle the wagons" responses to consumers' XPSP2
problems, and Microsoft's update inadequacies and poor communications to
their user base.
Bill G. should pull a few of those billions of dollars out of his pocket and
fix his firm--including buying a few more update servers. And what happened
to all the beta testing I read about that kept telling me there would be few
and manageable problems? (I guess that's what they meant in using, but not
defining the term "behave differently" to describe some potential issues.)
Only now am I reading from sources other than the press about the real
problems to be expected. I guess providing the media a dollar or two and/or
free software buys lots of bogus press.
Admit it, Microsoft has blown this one. Otherwise, why are so many people
completely clueless as to how the update process is supposed to work? Why
didn't Microsoft tell consumers [after telling them to turn on auto-update]
to expect incremental downloads over days or even weeks? I reckon Microsoft
also promises wonderful baskets of candy to children, but then doles out only
one piece at a time. It is glaringly obvious better communications would have
saved Microsoft tons of ill-will, time addressing the same questions over and
over again, and users tons of worry and frustration. Again, Duh!
By the way, if statistics hold then only one out of nine consumers with
problems are voicing their dissatisfaction. But in this very different
scenario, that does not take into account consumers who really don't know
anything about computers other than to turn them on, or to come to these
forums seeking advice. Given that, I would multiply the number of complaints
seen here by no less than 1000 to *very conservatively* estimate the real
scope of this problem. (Hey, I'm an MVP, too--but one who has made a career
of understanding and improving service quality and customer satisfaction. I
will stake my Ph.D. on my numerical assessment.)
"Kaylene aka Taurarian" wrote:
> I updated on Friday and so far so good. It's entirely up to you when you're
> ready.
> http://www3.telus.net/dandemar/spackins.htm
> Service Pack Installation Check List
>
> "ZenWarrior" <> wrote in message
> news:FB32358C-4185-4142-A05F-...
> > Thanks, Kaylene and wooosh. However, I will now wait no less [and likely
> > more] than 2-3 months before subjecting my perfectly good and working
> > computer to Microsoft's current ineptitude. Right now, I might even choose a
> > virus infestation over this update. At least I would not have to wait a
> > Microsoft millennium for a fix--and the root problem would be much more
> > easily identified.
> >
> > (Microsoft's attempt at beefing up security may well end up dreadfully
> > backfiring. Unless tortured with burning coals placed in my eyes, I won't
> > even think about the XPSP2 update for quite a while. And as I look around the
> > net, I see I am not alone.)