Re: Most Recent Windows Updates

I am in agreement with Howard, and appreciate his frustration and agree with
his apology to Alan. I believe with the "MS MVP" label associated, Alan gets
tagged with what is called "the color of authority" of an MS employee. Sorry
if Alan gets personal hits, it really isn't his fault, but the lack of
customer understanding on the part of MS. My confusion came from the fact
that a critical MS update affected my other MS software specifically. When
things go wrong, I ask myself, "What changed and might be the cause?"
Computers are integral parts of our lives and we get upset when problems come
out of nowhere and we didn't feel we did anything to cause these problems. If
the problem is actually due to non-MS software (such as HP Share-to-web)
interacting with the updated MS files, then MS needs to understand beforehand
that MANY people have HP printers and probably have the HP software. A little
forethought and testing may have prevented the problems I and others are
seeing. I am semi-literate on computers and not at all comfortable with
mucking around in registry. I pity grandmothers trying to deal with this
issue when all they want to do is send e-mail. Here's my analogy: These MS
patches are like trying to fix a leaky roof with tar and an occasional new
shingle. Buckets catch the incoming rain where the problem leak can't be
identified. At some point it is best to spend the money and get a new roof...
or move.

"Howard" wrote:

Alan,

Randy's assessment of what "most of the peope who have problems" are
thinking when they view this site describes my perspective precisely. I
believed you to be an MS employee - attributable somewhat to the "MS MVP
WINDOWS...." postscript on your messages. It appears that I have no idea what
such postscripts actually mean.

No offense, but your original response seemed a bit cryptic for the nature
of the problem as originally described by Wisecracker". It wasn't useful to a
less-than-knowledgable person such as myself. On the other hand, the
information at link to "aumha.net" provided by Maurice is extremely helpful

I apologize for my misunderstanding.

I still feel that MS is handling this situation very poorly.


"Alan Edwards" wrote:

I can't argue with any of that.

I am afraid I am not 100% sure what form the update will take on 25th.
I have read information over and over and still cannot be certain. The
way I read it, the same number will be used. At this stage, I assume
the only way to see that it is the new one is by the date.
Read
http://www.microsoft.com/technet/security/bulletin/ms06-015.mspx and
see if you put a different interpretation on it.

....Alan
--
Alan Edwards, MS MVP Windows - Internet Explorer
http://dts-l.org/index.html

On Sun, 23 Apr 2006 22:04:01 -0700, in microsoft.public.windowsupdate,
Randy1701 <Randy1701@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Alan,
I'm sure most of the people who have problems with your responses don't
understand that you don't work for MS. Since they get here to the newsgroups
from MS support website they assume that any MVP responses are from MS. And
they are understandably upset that they don't see any explicit signs that MS
is doing what they all expect to be a reasonable response, ie. remove the
problematic update from the update site until the "fix to the fix" is made.
Last I looked even the official admission of any problems was rather buried
in the updated version for the original MS Bulletin. I see nothing wrong in
your responses at all since all you can do is post what others see right now
as a workaround, even though that's what the update sight will essentially
have whether it comes out as the same or different KB number. And of course
people are nervous about trusting MS, after all would you want to pick up the
rattlesnake that just bit you, they expect to get bitten again. Thanks to
you and all the others who have posted links to reg patches for those of us
leery of manually updating the registry ourselves.
So, question - will the update on the 25th still read as the original
KB number, in which case how will anyone know for sure it is the "fixed
version", or will it be an entirely new number that says it fixes issues with
older number?


"Alan Edwards" wrote:

As I don't work for MS, I doubt they would be embarrassed by my
responses, which seem to have pleased hundreds of people with the same
problem. I really don't see what you have against the information I
supply.

....Alan
--
Alan Edwards, MS MVP Windows - Internet Explorer
http://dts-l.org/index.html



On Sun, 23 Apr 2006 19:55:02 -0700, in microsoft.public.windowsupdate,
Howard <Howard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I have the exact same problem with my Media Center 2004 system with Office
Pro 2003. All Office apps lock up whenever I attempt to open a file using
the "file" menu or the "open" button. I also restored to April 10th but
negelected to shut off auto updates. So....I've had to do three restores so
far because the auto update has reinstalled the same bad updates three times.
I'm sometimes dumb. However, what Microsoft has done here is unforgivable.
Worse, the manner in which "Alan" has responded is an embarassment for MS.

Will someone competent at MS please fix this mess and quickly and give us
some useful support?

"wisecracker" wrote:

I installed on April 18 the automatic updates: KB 908531; KB 911562; KB
890830; KB 912812; KB 911701; KB 911565 and KB 911567. I have MS Office XP
with Publisher 2000, and after installation I could no longer open MSWord
documents stored on my hard drive. I could no longer import and export my
calendar or contacts from MS Outlook using a floppy disc. I did system
restore back to April 10 and all the problems went away. I re-installed
these automatic updates again as a test, and the problems returned. I then
did system restore back to April 10 and turned off automatic updates from MS.
Problem solved. I do not intend on going through this again. Does anybody at
MS have a clue what is going on here with this update?


.

Quantcast