MS really couldn't give to sh*ts about its individual customers and small businesses!

[kurttrail]

Regarding the completely irresponsible QA that MS did with MS06-015,
KB908531:

"Again, our information at this time leads us to believe that this is
having little to no impact on corporate networks." -
http://blogs.technet.com/msrc/archive/2006/04/15/425311.aspx

Just though ya'll should know what MS thinks about its non-corporate
customers. Absolutely NOTHING! Ya'll don't even exist!

--
Peace!
Kurt Kirsch
Self-anointed Moderator
http://microscum.com
"It'll soon shake your Windows
And rattle your walls
For the times they are a-changin'."

 

[David Candy]

OEMs are MS's main customer, esp for SOHO market.

 

[Manny Borges]

So what exactly was the issue? What HP devices?
I don't see how the impact can be that low, since "HP devices" are are as
wide spread and omnipresent as the XP OS is.

It does seem a little off the cuff, but it is a blog.

I am more interested in what it doesn't say. Like exactly what the problem
is and how is it going to fixed.
I mean he gave an example that basically said "If you do something sometimes
with specific applications, something happens that could effect you."
Registry edits are ok, but joe average depends on things like automatic
updates and servcie packs for these kinds of issues. Links would have been
fine.

This blogger is obviously just a diptard.
--
Manny Borges
MCSE NT4-2003 (+ Security)
MCT, Certified Cheese Master

There are 10 kinds of people in the world. Those who do understand binary
and those who don't.

 

[kurttrail]

So what exactly was the issue? What HP devices?
I don't see how the impact can be that low, since "HP devices" are
are as wide spread and omnipresent as the XP OS is.

It does seem a little off the cuff, but it is a blog.

I am more interested in what it doesn't say. Like exactly what the
problem is and how is it going to fixed.
I mean he gave an example that basically said "If you do something
sometimes with specific applications, something happens that could
effect you." Registry edits are ok, but joe average depends on things
like automatic updates and servcie packs for these kinds of issues.
Links would have been fine.

This blogger is obviously just a diptard.

There are 10 kinds of people in the world. Those who do understand
binary and those who don't.

I agree. The average joe with a HP printer, shouldn't be encouraged to
muck about in the registry as a fix to a patch gone wild.

But from what I understand, MS is leaving the fix to HP. Much like MS
leaving the ActiveX fiasco to be fixed by web developers.

MS should be held financially responsible for it f*$k-ups, and for
cleaning up the ActiveX mess due to their patent piracy. But MS is just
to good at passing the sh*t down the line for other to clean up for
them.

--
Peace!
Kurt Kirsch
Self-anointed Moderator
http://microscum.com
"It'll soon shake your Windows
And rattle your walls
For the times they are a-changin'."

 

[Bob I]

read here as to what they've identified as the cause
Problems in Windows Explorer or the Windows shell after you install
security update MS06-015
http://support.microsoft.com/kb/918165/en-us

 

[antioch]

Kellys Korner has a fix, though as yet I have not used it - will save it
until last resort/await developments in the groups.
What I do not get is why was it given in the last list of updates when I
have NOTHING HP on my system - or does that not matter in this case.
Rgds
Antioch