Re: OT: Problems with latest Micorosoft security update


"Steve Cobham" <steve@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:qqo6425vgkqhea1dv48fu1aanne9aud54o@xxxxxxxxxx
On Sun, 16 Apr 2006 22:09:04 +0100, "George Weston"
<george@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

As I said
earlier, there's a registry fix available for those in that position.

And as I said earlier, this is no "fix" when looking at the Windows
Users' community as a whole.

Whilst you and I might have no qualms about editing the registry - and
that always has to be done carefully and after backing it up - let's
take a new user, or an OAP or someone with maybe less intelligence
than the norm and think what havoc they could wreak............

That MSoft should suggest such a course of action is the height of
irresponsibility and plumbs new depths of cockwittery even for them.

It's like a surgeon cocking up an operation and then giving you a
*** of instructions and a scalpel and telling you to get on with it
and put it right or a mechanic repairing your car badly and then
handing you a spanner and telling you what to do to rectify *their*
mistake.

Besides, unless you're reasonably net-savvy, how are you going to

a) discover that your Word and IE problems are down to the update and
are shared with thousands of people ?

and

b) find the registry "fix"?

I would suggest that the vast majority of Windows users just use their
systems like a TV - they turn it on, use it and don't think about how
it works and what to do if it goes tits up.

Like most users of a machine they have an innate trust in experts when
things go wrong.

When those experts can't provide adequate customer support then the
whole service aspect just breaks down.

Yup - Microsoft have done it again.

Steve.

I don't think we're at issue here, Steve. This is one god-almighty fcuk-up
by MS, who took 4 days to recognise there was a problem and then reluctantly
issue a "physician, heal thyself" fix, which, as you say, won't get picked
up by the majority of windoze users. Even if some of them do, they might
well have a problem in carrying out the registry fix if they don't copy and
paste the line of code, as it uses curly brackets { } . I made the mistake
first time of typing it in and using ( ) brackets and wondered why it didn't
work first time!

My original post was, of course, to warn others in this NG who might be
adversely affected by the update in a similar way to myself, having HP
photosmart printer software on my machine. It was purely by chance that I
realised there was a problem when Mrs W created a Word document a few hours
after the update download and found she couldn't save it. I suspected it was
the update that caused the problem, went back to an earlier restore point
and found that solved the problem temporarily. I then spent 3 days trawling
microsoft.public newsgroups until I found the "resolution" fix information.

George



.

Loading