Microsoft need to be held accountable!

I normally do not get so upset to the point where I feel like I have to make
such a statement, but after only a few hours of sleep in the past two nights
fixing what Microsoft screwed up and seeing half of my wife's company's
system affected the same way by this weeks security updates, I'm going to
fuss for a moment.
I have been in this industry for 16 years. I have seen Microsoft shine and
with some of their successes and there are times where it seems as though
their QA department went to lunch. This time their QA department was on
vacation while these releases were developed. Strange, on the page where the
KB's are described, there are credits to the development team ... it should
be Reprimands instead. What were they thinking by making this available to
millions without running it through their own organization first. I can
guarantee you, had they done so, some changes would have been made and we
would not be going through this.
Yes, in a day and age where we are playing cat-and-mouse with the pukes that
constantly waist their lives away exposing security breaches in Windows and
other applications, it is important to get the fixes/updates out there fast
.... but not this fast! Not when it makes a system completely unbootable to
the point where you have to go into the Recovery Console, know what your are
doing with the list of commands to un-install the offending update. What
about those poor saps that cannot remember their Administrator password? Yes
it happens: They pick something so simple thinking that they will never
forget. Then they find themselve typing in the names of their families, the
names of their in-laws, even the names of their goldfish in dire hopes that
one of them will be a hit.
How does Microsoft plan on making this up to us? I truly hope that someone
at Microsoft who still passionately cares about quality reads this and can
come up with a way to make up for the lost productivity and sleep caused by
this goof-up. How can they assure us that a security update will not bring a
computer to its knees to the point where a rebuild is the final solution? I
sure miss the days you could boot from portable media, replace the corrupt
file or make the necessary changes to the configuration with out having to be
an MCSE!
So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
these updates throughout your organization first, if you feel as though it
will be acceptable to the public, then release it. Do you hear me? Bueller?
Bueller?
Like I said, I am not one fuss much, but when you distribute such an
offending piece of code that cripples so many systems, something needs to be.
There, now I feel better (soft of).

Pappy wrote:
> I normally do not get so upset to the point where I feel like I
> have to make such a statement, but after only a few hours of sleep
> in the past two nights fixing what Microsoft screwed up and seeing
> half of my wife's company's system affected the same way by this
> weeks security updates, I'm going to fuss for a moment.
> I have been in this industry for 16 years. I have seen Microsoft
> shine and with some of their successes and there are times where it
> seems as though their QA department went to lunch. This time their
> QA department was on vacation while these releases were developed.
> Strange, on the page where the KB's are described, there are
> credits to the development team ... it should be Reprimands
> instead. What were they thinking by making this available to
> millions without running it through their own organization first.
> I can guarantee you, had they done so, some changes would have been
> made and we would not be going through this.
> Yes, in a day and age where we are playing cat-and-mouse with the
> pukes that constantly waist their lives away exposing security
> breaches in Windows and other applications, it is important to get
> the fixes/updates out there fast ... but not this fast! Not when
> it makes a system completely unbootable to the point where you have
> to go into the Recovery Console, know what your are doing with the
> list of commands to un-install the offending update. What about
> those poor saps that cannot remember their Administrator password?
> Yes it happens: They pick something so simple thinking that they
> will never forget. Then they find themselve typing in the names of
> their families, the names of their in-laws, even the names of their
> goldfish in dire hopes that one of them will be a hit.
> How does Microsoft plan on making this up to us? I truly hope that
> someone at Microsoft who still passionately cares about quality
> reads this and can come up with a way to make up for the lost
> productivity and sleep caused by this goof-up. How can they assure
> us that a security update will not bring a computer to its knees to
> the point where a rebuild is the final solution? I sure miss the
> days you could boot from portable media, replace the corrupt file
> or make the necessary changes to the configuration with out having
> to be an MCSE!
> So, the key words for you Microsoft are: "Test", "Test", and
> "Test". Run these updates throughout your organization first, if
> you feel as though it will be acceptable to the public, then
> release it. Do you hear me? Bueller? Bueller?
> Like I said, I am not one fuss much, but when you distribute such an
> offending piece of code that cripples so many systems, something
> needs to be. There, now I feel better (soft of).

Sorry you were affected - would you care to give more details?

I have distributed the update to a few thousand machines so far - with
dozens upon dozens of applications installed and have not had issues - so I
would be curious to hear about your issues.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Thanks for saying much better what I wanted to say myself

CD


"Pappy" <> wrote in message
news:57A0FF82-BDA1-40FA-AA2E-...
>I normally do not get so upset to the point where I feel like I have to
>make
> such a statement, but after only a few hours of sleep in the past two
> nights
> fixing what Microsoft screwed up and seeing half of my wife's company's
> system affected the same way by this weeks security updates, I'm going to
> fuss for a moment.
> I have been in this industry for 16 years. I have seen Microsoft shine
> and
> with some of their successes and there are times where it seems as though
> their QA department went to lunch. This time their QA department was on
> vacation while these releases were developed. Strange, on the page where
> the
> KB's are described, there are credits to the development team ... it
> should
> be Reprimands instead. What were they thinking by making this available
> to
> millions without running it through their own organization first. I can
> guarantee you, had they done so, some changes would have been made and we
> would not be going through this.
> Yes, in a day and age where we are playing cat-and-mouse with the pukes
> that
> constantly waist their lives away exposing security breaches in Windows
> and
> other applications, it is important to get the fixes/updates out there
> fast
> ... but not this fast! Not when it makes a system completely unbootable
> to
> the point where you have to go into the Recovery Console, know what your
> are
> doing with the list of commands to un-install the offending update. What
> about those poor saps that cannot remember their Administrator password?
> Yes
> it happens: They pick something so simple thinking that they will never
> forget. Then they find themselve typing in the names of their families,
> the
> names of their in-laws, even the names of their goldfish in dire hopes
> that
> one of them will be a hit.
> How does Microsoft plan on making this up to us? I truly hope that
> someone
> at Microsoft who still passionately cares about quality reads this and can
> come up with a way to make up for the lost productivity and sleep caused
> by
> this goof-up. How can they assure us that a security update will not
> bring a
> computer to its knees to the point where a rebuild is the final solution?
> I
> sure miss the days you could boot from portable media, replace the corrupt
> file or make the necessary changes to the configuration with out having to
> be
> an MCSE!
> So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
> these updates throughout your organization first, if you feel as though it
> will be acceptable to the public, then release it. Do you hear me?
> Bueller?
> Bueller?
> Like I said, I am not one fuss much, but when you distribute such an
> offending piece of code that cripples so many systems, something needs to
> be.
> There, now I feel better (soft of).

Pappy

I really like to hear what exactly was your issue when downloading the Updates. Just out of curiosity did you by any chance turn off your 3rd party security apps like Norton,MacAfee, ZA and etc when downloading and installing the Updates.

Please post back with what exactly happened. I have Updated many computers without any issues and I like to hear yours.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Pappy" <> wrote in message news:57A0FF82-BDA1-40FA-AA2E-...
>I normally do not get so upset to the point where I feel like I have to make
> such a statement, but after only a few hours of sleep in the past two nights
> fixing what Microsoft screwed up and seeing half of my wife's company's
> system affected the same way by this weeks security updates, I'm going to
> fuss for a moment.
> I have been in this industry for 16 years. I have seen Microsoft shine and
> with some of their successes and there are times where it seems as though
> their QA department went to lunch. This time their QA department was on
> vacation while these releases were developed. Strange, on the page where the
> KB's are described, there are credits to the development team ... it should
> be Reprimands instead. What were they thinking by making this available to
> millions without running it through their own organization first. I can
> guarantee you, had they done so, some changes would have been made and we
> would not be going through this.
> Yes, in a day and age where we are playing cat-and-mouse with the pukes that
> constantly waist their lives away exposing security breaches in Windows and
> other applications, it is important to get the fixes/updates out there fast
> ... but not this fast! Not when it makes a system completely unbootable to
> the point where you have to go into the Recovery Console, know what your are
> doing with the list of commands to un-install the offending update. What
> about those poor saps that cannot remember their Administrator password? Yes
> it happens: They pick something so simple thinking that they will never
> forget. Then they find themselve typing in the names of their families, the
> names of their in-laws, even the names of their goldfish in dire hopes that
> one of them will be a hit.
> How does Microsoft plan on making this up to us? I truly hope that someone
> at Microsoft who still passionately cares about quality reads this and can
> come up with a way to make up for the lost productivity and sleep caused by
> this goof-up. How can they assure us that a security update will not bring a
> computer to its knees to the point where a rebuild is the final solution? I
> sure miss the days you could boot from portable media, replace the corrupt
> file or make the necessary changes to the configuration with out having to be
> an MCSE!
> So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
> these updates throughout your organization first, if you feel as though it
> will be acceptable to the public, then release it. Do you hear me? Bueller?
> Bueller?
> Like I said, I am not one fuss much, but when you distribute such an
> offending piece of code that cripples so many systems, something needs to be.
> There, now I feel better (soft of).

You posting about 6 hrs ahead in the future. Your Time or your Zone is not set properly
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"realcestmoi" <> wrote in message news:...
> Hi Pappy,
>
>
>
> It seems you are forgetting how big a variety of software people can have
> installed on their system, not to mention the many thousands of different
> hardware configurations which are possible.
>
>
>
> All I mean to say that if Microsoft has tot test al this possibilities than
> by the time the patch is released we are as I believe at least two years
> further in time, so patching is not needed anymore by than
>
>
>
> Also a piece of software is made by man and as we all know by know, mankind
> makes mistakes.
>
>
>
> This does not mean that I am not sorry for the trouble you have run in, its
> just my two cents
>
>
>
> I believe they really are doing the best they can at Microsoft.
>
>
>
> All I would like them to do is make the prices for the software more
> accordingly to the bugs we are getting for free along with it.
>
>
>
> It would help however if people started to skip any driver updates from MS
> and would be more careful installing any updates by not blindly doing so as
> I know by excperience many users do.
>
>
>
> Wish you good luck on resolving the problem issues.
>
>
>
> Best regards,
>
> Michel Denie
>
>
>
>
>
>
> "Pappy" <> wrote in message
> news:57A0FF82-BDA1-40FA-AA2E-...
>>I normally do not get so upset to the point where I feel like I have to
>>make
>> such a statement, but after only a few hours of sleep in the past two
>> nights
>> fixing what Microsoft screwed up and seeing half of my wife's company's
>> system affected the same way by this weeks security updates, I'm going to
>> fuss for a moment.
>> I have been in this industry for 16 years. I have seen Microsoft shine
>> and
>> with some of their successes and there are times where it seems as though
>> their QA department went to lunch. This time their QA department was on
>> vacation while these releases were developed. Strange, on the page where
>> the
>> KB's are described, there are credits to the development team ... it
>> should
>> be Reprimands instead. What were they thinking by making this available
>> to
>> millions without running it through their own organization first. I can
>> guarantee you, had they done so, some changes would have been made and we
>> would not be going through this.
>> Yes, in a day and age where we are playing cat-and-mouse with the pukes
>> that
>> constantly waist their lives away exposing security breaches in Windows
>> and
>> other applications, it is important to get the fixes/updates out there
>> fast
>> ... but not this fast! Not when it makes a system completely unbootable
>> to
>> the point where you have to go into the Recovery Console, know what your
>> are
>> doing with the list of commands to un-install the offending update. What
>> about those poor saps that cannot remember their Administrator password?
>> Yes
>> it happens: They pick something so simple thinking that they will never
>> forget. Then they find themselve typing in the names of their families,
>> the
>> names of their in-laws, even the names of their goldfish in dire hopes
>> that
>> one of them will be a hit.
>> How does Microsoft plan on making this up to us? I truly hope that
>> someone
>> at Microsoft who still passionately cares about quality reads this and can
>> come up with a way to make up for the lost productivity and sleep caused
>> by
>> this goof-up. How can they assure us that a security update will not
>> bring a
>> computer to its knees to the point where a rebuild is the final solution?
>> I
>> sure miss the days you could boot from portable media, replace the corrupt
>> file or make the necessary changes to the configuration with out having to
>> be
>> an MCSE!
>> So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
>> these updates throughout your organization first, if you feel as though it
>> will be acceptable to the public, then release it. Do you hear me?
>> Bueller?
>> Bueller?
>> Like I said, I am not one fuss much, but when you distribute such an
>> offending piece of code that cripples so many systems, something needs to
>> be.
>> There, now I feel better (soft of).
>
>

Hi Pappy,



It seems you are forgetting how big a variety of software people can have
installed on their system, not to mention the many thousands of different
hardware configurations which are possible.



All I mean to say that if Microsoft has tot test al this possibilities than
by the time the patch is released we are as I believe at least two years
further in time, so patching is not needed anymore by than



Also a piece of software is made by man and as we all know by know, mankind
makes mistakes.



This does not mean that I am not sorry for the trouble you have run in, its
just my two cents



I believe they really are doing the best they can at Microsoft.



All I would like them to do is make the prices for the software more
accordingly to the bugs we are getting for free along with it.



It would help however if people started to skip any driver updates from MS
and would be more careful installing any updates by not blindly doing so as
I know by excperience many users do.



Wish you good luck on resolving the problem issues.



Best regards,

Michel Denie






"Pappy" <> wrote in message
news:57A0FF82-BDA1-40FA-AA2E-...
>I normally do not get so upset to the point where I feel like I have to
>make
> such a statement, but after only a few hours of sleep in the past two
> nights
> fixing what Microsoft screwed up and seeing half of my wife's company's
> system affected the same way by this weeks security updates, I'm going to
> fuss for a moment.
> I have been in this industry for 16 years. I have seen Microsoft shine
> and
> with some of their successes and there are times where it seems as though
> their QA department went to lunch. This time their QA department was on
> vacation while these releases were developed. Strange, on the page where
> the
> KB's are described, there are credits to the development team ... it
> should
> be Reprimands instead. What were they thinking by making this available
> to
> millions without running it through their own organization first. I can
> guarantee you, had they done so, some changes would have been made and we
> would not be going through this.
> Yes, in a day and age where we are playing cat-and-mouse with the pukes
> that
> constantly waist their lives away exposing security breaches in Windows
> and
> other applications, it is important to get the fixes/updates out there
> fast
> ... but not this fast! Not when it makes a system completely unbootable
> to
> the point where you have to go into the Recovery Console, know what your
> are
> doing with the list of commands to un-install the offending update. What
> about those poor saps that cannot remember their Administrator password?
> Yes
> it happens: They pick something so simple thinking that they will never
> forget. Then they find themselve typing in the names of their families,
> the
> names of their in-laws, even the names of their goldfish in dire hopes
> that
> one of them will be a hit.
> How does Microsoft plan on making this up to us? I truly hope that
> someone
> at Microsoft who still passionately cares about quality reads this and can
> come up with a way to make up for the lost productivity and sleep caused
> by
> this goof-up. How can they assure us that a security update will not
> bring a
> computer to its knees to the point where a rebuild is the final solution?
> I
> sure miss the days you could boot from portable media, replace the corrupt
> file or make the necessary changes to the configuration with out having to
> be
> an MCSE!
> So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
> these updates throughout your organization first, if you feel as though it
> will be acceptable to the public, then release it. Do you hear me?
> Bueller?
> Bueller?
> Like I said, I am not one fuss much, but when you distribute such an
> offending piece of code that cripples so many systems, something needs to
> be.
> There, now I feel better (soft of).

On Sat, 14 Apr 2007 11:56:26 +0200, "realcestmoi" <>
wrote:

>It would help however if people started to skip any driver updates from MS
>and would be more careful installing any updates by not blindly doing so as
>I know by excperience many users do.

Most of the critical updates state that this update fixes a problem
that might let others take over your computer... blah, blah. That's
just too generic a description in my opinion. If I didn't install
those, I'd be 50 or 60 updates behind. I wish they would give a bit
more specifics with the descriptions. Another concern with those
generic descriptions for updates is that they might be slipping us
little 'spys' to check that we are doing everything Microsoft's way
and that one day, they might decide we are doing something our way and
kill our system. :/

--
Zilbandy

Zilbandy wrote:
> Most of the critical updates state that this update fixes a problem
> that might let others take over your computer... blah, blah. That's
> just too generic a description in my opinion. If I didn't install
> those, I'd be 50 or 60 updates behind. I wish they would give a bit
> more specifics with the descriptions. Another concern with those
> generic descriptions for updates is that they might be slipping us
> little 'spys' to check that we are doing everything Microsoft's way
> and that one day, they might decide we are doing something our way
> and kill our system. :/

Are you serious?
You just need to know WHERE to look I guess...

Once you know the KB article # for an update - it's easy to find out WAY too
much information on it...

Example... Let's say you wanted to look more closely at the patches released
this month (April 2007):
http://www.microsoft.com/technet/sec.../ms07-apr.mspx

Out of those critical updates - let's say you wanted to know more about
932168...
http://support.microsoft.com/kb/932168

Since you want to know MUCH more - one would assume you are not considering
yourself a home user in this case - you want the dirty details so you would
choose to view the information for IT professionals...
http://www.microsoft.com/technet/sec.../ms07-020.mspx

Where you can find expandable sections detailing out more than you probably
will ever need to know + some more just in case...

There are MANY patterns there...

You can see the critical (security and other) patches released for a given
month using the following:

http://www.microsoft.com/technet/sec.../ms##-***.mspx

At the end of this line you see "ms##-***.mspx" .. If you simply replace ##
with the two-digit year and the *** with the three character month
abbreviation, you will see the list of "critical" and "important" patches
for that month (since it only happens once a month usually, if you check by
the second Tuesday (wait until afternoon) of each month - you should be
fine) - note that future months will not work.

As an example...

December 2004's patches..
http://www.microsoft.com/technet/sec.../ms04-dec.mspx

March 2005's patches..
None released.. so that one will fail...

May 2006's patches..
http://www.microsoft.com/technet/sec.../ms06-may.mspx

January 2007's patches..
http://www.microsoft.com/technet/sec.../ms07-jan.mspx

Once you know the KB article number - you can always go to
http://support.microsoft.com/kb/###### to view more information about said
patch. Usually that links you to the Microsoft Security Bulletin - which
once you know that number can be viewed by going to
http://www.microsoft.com/technet/sec.../ms##-###.mspx <- both of
those links are fill-in-the-blanks for the article/bulletin numbers.


The information is out there - you might have to put forth effort instead of
someone spoon feeding you - but it is there.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

On Sat, 14 Apr 2007 15:07:15 -0500, "Shenan Stanley"
<> wrote:

>Are you serious?
>You just need to know WHERE to look I guess...

I guess looking at the description on the update page isn't enough.
I've clicked the links from that page. The 'more info' link is
useless. I'll have to wait until next update Tuesday to double check.
I'll get back to you next time I have an update to install.

--
Zilbandy

Customers in the U.S. and Canada can receive technical support from
Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for
support calls that are associated with security updates.

International customers can receive support from their local Microsoft
subsidiaries. There is no charge for support that is associated with
security updates. For more information about how to contact Microsoft for
support issues, visit the International Support Web site:
https://support.microsoft.com/common/international.aspx
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org

Pappy wrote:
> I normally do not get so upset to the point where I feel like I have to
> make
> such a statement, but after only a few hours of sleep in the past two
> nights
> fixing what Microsoft screwed up and seeing half of my wife's company's
> system affected the same way by this weeks security updates, I'm going to
> fuss for a moment.
> I have been in this industry for 16 years. I have seen Microsoft shine
> and
> with some of their successes and there are times where it seems as though
> their QA department went to lunch. This time their QA department was on
> vacation while these releases were developed. Strange, on the page where
> the KB's are described, there are credits to the development team ... it
> should be Reprimands instead. What were they thinking by making this
> available to millions without running it through their own organization
> first. I can guarantee you, had they done so, some changes would have
> been
> made and we would not be going through this.
> Yes, in a day and age where we are playing cat-and-mouse with the pukes
> that
> constantly waist their lives away exposing security breaches in Windows
> and
> other applications, it is important to get the fixes/updates out there
> fast
> ... but not this fast! Not when it makes a system completely unbootable
> to
> the point where you have to go into the Recovery Console, know what your
> are
> doing with the list of commands to un-install the offending update. What
> about those poor saps that cannot remember their Administrator password?
> Yes it happens: They pick something so simple thinking that they will
> never
> forget. Then they find themselve typing in the names of their families,
> the
> names of their in-laws, even the names of their goldfish in dire hopes
> that
> one of them will be a hit.
> How does Microsoft plan on making this up to us? I truly hope that
> someone
> at Microsoft who still passionately cares about quality reads this and can
> come up with a way to make up for the lost productivity and sleep caused
> by
> this goof-up. How can they assure us that a security update will not
> bring
> a computer to its knees to the point where a rebuild is the final
> solution?
> I sure miss the days you could boot from portable media, replace the
> corrupt
> file or make the necessary changes to the configuration with out having to
> be an MCSE!
> So, the key words for you Microsoft are: "Test", "Test", and "Test". Run
> these updates throughout your organization first, if you feel as though it
> will be acceptable to the public, then release it. Do you hear me?
> Bueller? Bueller?
> Like I said, I am not one fuss much, but when you distribute such an
> offending piece of code that cripples so many systems, something needs to
> be. There, now I feel better (soft of).