KB908531 and Microsoft

[Dannie]

With all the posted problems about update KB908531 has anyone heard from
Microsoft acknowledging these problems? Seems awfully quiet and I wonder
what next months updates will bring if KB908531 has not changed. In short
what happens if one doesn't use this update but next month installs
Microsoft's new KB?? update?
Think about it!!
Dan

 

[neil]

Suppose the problem is you never here of updates that go without a problem.
Just for the record mine is OK and it installed via "Automatic Updates". We
have about 100 PC's at work and they are OK. MS may not see it as a problem
in their Security update but a software problem on the PC.

Just a thought
Neil

 

[All Things Mopar]

Today neil commented courteously on the subject at hand

Suppose the problem is you never here of updates that go
without a problem. Just for the record mine is OK and it
installed via "Automatic Updates". We have about 100 PC's
at work and they are OK. MS may not see it as a problem in
their Security update but a software problem on the PC.

None of us outside the coistered halls of Redmond really know
for sure, but it would seem prudent for the purveyor of the
world's most popular OS and a major cash cow to not only be
aware of any and all problems, but to regression test for them
and re-release the patch.

I can't argue with yours or anyone's successes but one cannot
prove a negative hypthesis by example, meaning, 1,000,000
KB908531s may install without problem but all it takes is one to
"prove" it has a problem. Presumeably "by definition" a security
"critical update" should not derail anything on anyone's PC,
doncha think?

 

[George Weston]

With all the posted problems about update KB908531 has anyone heard from
Microsoft acknowledging these problems? Seems awfully quiet and I wonder
what next months updates will bring if KB908531 has not changed. In short
what happens if one doesn't use this update but next month installs
Microsoft's new KB?? update?
Think about it!!
Dan

See fix at:
http://support.microsoft.com/kb/918165
George

 

[Willy]

George,
This fixed it as I do have an HP Photo-Smart Printer and the Share to Web
Utility.

 

[Guest]

I tried the fix mentioned re Share to Web, which involves changing the
registry. It did not work for me. I have simply been removing KB908531 each
time it arrives (which is daily) to solve this very serious problem that
affects all Office products. MS says it is working on a fix. I'll wait for
that. You can also disable automatic updates and install them individually.

 

[Richard in AZ]

Just changing the registry as defined in the MS KB does not complete the job. You need a few other
tweaks.

Go to the following web site:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Scroll down to line 383 and on the right hand side is a Script file that you download and run.

This Script file will make the required registry changes for you that will fix the HP Share-to-Web
software conflict.
Microsoft put out a technical bulletin on April 15th that describes the steps to manually change
your registry, but the recommended change is really too hard for most "non-techies" to perform.
Hence one of the experts (Kelly Theriot ) has generously written a Script file that accurately makes
the changes for you.

 

[All Things Mopar]

Today =?Utf-8?B?Q1doaXQ=?= commented courteously on the
subject at hand

I tried the fix mentioned re Share to Web, which involves
changing the registry. It did not work for me. I have
simply been removing KB908531 each time it arrives (which
is daily) to solve this very serious problem that affects
all Office products. MS says it is working on a fix. I'll
wait for that. You can also disable automatic updates and
install them individually.

I can understand Bill the Gates' tenacity in wanting to "help"
you when he detects you've uninstalled his, er ..., handiwork,
but why do you let him and Murphy in your house or business ever
again?

Just curious, as this KB seems to sprout wings on what is a no-
brainer to me - iffn ya ain't affected or even if ya is, don't
install the dog until you confirm it is rock solid. Better the
devil you know than the one you don't meaning, I'll take a minor
security risk and keep working, without bullshit Registry hacks
from the folks who want my OS money and are demonstrably poor at
quality control.

 

[All Things Mopar]

Today Richard in AZ commented courteously on the subject at
hand

Just changing the registry as defined in the MS KB does not
complete the job. You need a few other tweaks.

Go to the following web site:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Scroll down to line 383 and on the right hand side is a
Script file that you download and run.

This Script file will make the required registry changes
for you that will fix the HP Share-to-Web software
conflict. Microsoft put out a technical bulletin on April
15th that describes the steps to manually change your
registry, but the recommended change is really too hard for
most "non-techies" to perform. Hence one of the experts
(Kelly Theriot ) has generously written a Script file that
accurately makes the changes for you.

Interesting. Kelly is always top-notch. I am still trying to
figure out exactly how dangerous the vulnerability really is
in some statistically valid way as well as why people want
whatever Share-to-Web is. My HP 1220C is quite old and is
definitely my last HP product, so I guess I shouldn't
complain.

Yeah, I will complain. Why do the rest of us (apparently)
without the so-called problem have to put up with the CU in
the first place? If Bill the Gates can look at my system for
current update state (repeadedly on the same KB) and
presumeably anything he wants to know about my installed
hardware and software (and call home without bothering to tell
me), why can't he simply note I don't have the problem and go
elsewhere hawking his crap?

 

[Guest]

Thanks for the link to kellys-korner. However, I followed the MS tech
bulletin instruction faithfully to edit the registry, double-checked the long
string for accuracy, and it still didn't work. I may try kellys fix but I
think I'll just wait for MS to fix the KB. After all, I've lived for some
time without it, and I wonder how "critical" it really is. The problem
sounds pretty "remote" (pardon the pun) to me.

 

[Richard in AZ]

If you don't have a problem with the update, don't fix anything.
If you do have problems after the update, Kellys-Korner fix implements the MS recommended fix for
you so you don't have to muck up the registry. His fix is accurate, complete and well done. We all
own him a great big thanks.

 

[All Things Mopar]

Today Richard in AZ commented courteously on the subject at
hand

If you don't have a problem with the update, don't fix
anything. If you do have problems after the update,
Kellys-Korner fix implements the MS recommended fix for you
so you don't have to muck up the registry. His fix is
accurate, complete and well done. We all own him a great
big thanks.

I thought Kelly was a she ...