Wed, Sep 11 2013 23:45
Dear Mr. Ballmer - my email today
(note the Patch management server is not sending things through as it should so I'm not sure this has officially posted to the list yet... but this is what I posted earlier)
cc to Patchmanagement.org
Filed under: Security
As one of the moderators for the PatchManagement listserve I am part of
a community that maintains and patches primarily Windows products. On
behalf of everyone in this community, may I respectfully request that
you assign someone in a management position to investigate what is going
on with quality control with Patch testing lately?
This month in particular leaves me deeply disturbed that issues that
should have been found before these updates were released are being
found by us - your customers - after they are released and we are having
to deal with the aftermath. This leads to increasing distrust of updating.
These issues in your newer products are deeply disturbing to me. The
issues this month in particular leave end users and Patch Admins with no
other recourse than to not patch and even disable automatic updates
until we are assured that issues have been fixed.
I congratulate you on your release to manufacture of Windows 8.1 but I
beg you to pause for a moment and investigate why we are seeing so many
patching issues with your released products at this time.
Bottom line, sir, this is unacceptable to all of us in the patching
community, and quite frankly, it should be just as unacceptable to you.
Moderator at www.patchmanagement.org
Speaking on behalf of everyone here in the patching community
I showcase the following of evidence of issues this month:
Three Office 2007 security updates install over and over again:
Outlook 2013 non security update causes folder pane to disappear:
Access 2013 security update fails to install with error 80242009
Past historical issues that have broken the trust of patching include:
Historical issues with Exchange update rollups as well as the very first
Exchange 2013 security update had issues and was acknowledged as not
being properly tested before release:
Sample past media coverage:
Please review past comments on the Exchange blog: