Microsoft and the NT Service Pack 6 Fiasco

RANT MODE == 1Yet another service pack for Windows NT, SP6. Years after the initial release of NT and the 6th such combined patch release, service pack, to date. This one is another great blunder from Microsoft. Heres Why.Please dont miconstrue, all software cannot be perfect and certainly patches are very normal. I dont fault anyone for admitting a problem and trying to honestly resolve it, including Microsoft. However Microsoft claims that quality is of utmost importance to their company and that NT is the result of tireless testing and stringent quality control, the finest software available. Therefore they set the standard for themselves and they made these rules (not to mention the prices, either this stuff should be damn good software or every time I buy it the gold bar is missing.)That said, Microsoft really sucks again. Not only does the latest service pack for NT break winsock communications. Microsoft does a very poor job of making people aware of the issue and explaining what happened or how to fix it. This attitude of "dont tell means aint broke" is what truly infuriates me. Not only that, but how come in such a stringent quality control environment the patch is broken, get that, not just the software needs patches, the patches need patches. The issue is that SP6 kills Winsock communications unless admin priveleges are present for the user. Solution, make everyone a domain admin, or "download these files." Yes, that is the Microsoft answer to a "confirmed probelm", "download these files." What does that mean? Yeah, I know how to fix it, but could someone explain this better on the apparent attempt at an explanation web page? Check out the lame excuse page here : Q245678 Winsock Call Fails after SP6. Could that be more non explanatory? Yeah I know the problem, thanks, elaborate on the solution next time, or better yet, dont release crap for software in the first place. Picture NT as a huge hunk of Swiss cheese in the middle of the Colorado river, water pouring through, thats analogous to what it is. Millions of lines of code that are so convuluted that even the developers cannot possibly keep up anymore. Thats quality for you, now how much would you pay? This is ridiculous, I dont care as much about a monopoly as I do when companies rip people off.There are laws for other products. Cars, the lemon laws vary by state but basically say the manufacturer gets 2 to 4 attempts to repair and if that does not work, money back, period. Where is the software lemon law to protect consumers (I am not serious here, we do not need more legislation, that I do not agree with, its just an analogy, the real solution is for consumers to not buy the faulty products and therefore vote against the company, not to legislate quality.)RANT MODE == 0Rant over, sorry about that, this latest problem may seem minor, but I think it is inexcusable. It is just another example of poor quality control and or ineptitude and or apathy at Microsoft. Another patch on a patch on a patch on a patch on a patch on a patch with a hotfix. SP6 problem description