Microsoft Pulls Broken XP Update 478
Cally writes "Yahoo! reports that
Microsoft have pulled a Windows XP update from the Windows Update servers after it killed network access for some users of the claimed 600,000 who installed it. (Does this mean only 600,000 XP users trust Windows Update?) The story hints that the problem was something to do with VPN or IPSec drivers clashing with Symantec software - however I haven't found anything about this on the Microsoft KnowledgeBase (the link Yahoo provide goes to the generic support home page.) Anyone got more info?"
That's the problem with automatic patching (Score:5, Insightful)
At least this patch made it perfectly obvious that it had a bug.
Why is this news? (Score:3, Insightful)
I'd say it was a slow news day, but it ain't even daytime yet.
Hmmm....I wonder why... (Score:5, Insightful)
Maybe because they couldn't get online to report the problem???
Old news (Score:5, Insightful)
More Slashdot Sensationalism (Score:5, Insightful)
What do you think is more likely: "only" 600,000 people trust Windows Update or everyone else just hasn't patched for checked for patches yet? I personally don't use the little auto-notification thingie, I just check every once in a while.
Also, how is this different from any automated Linux update method? Software has bugs. Patches may have bugs. Regardless of vendor, patches are not perfect and may induce problems.
Agree or disagree with me, when you think about it without bias it's true.
Palladium Pre-Testing (Score:3, Insightful)
But that would leave a major gap which, according to this story, has been admirably filled.
Trusted computing - only trust the worms written and distributed by MS itself.
Re:Microsoft Security (Score:2, Insightful)
Re:Microsoft Security (Score:5, Insightful)
Geez (Score:5, Insightful)
Umm... NO. It doesn't.
And stop taking cheap shots at MS, it just make you look like a whiny school kid.
There is plenty of reasons to bash MS policies and software, but the signal-to-noise ratio is getting silly.
Software Update Services... (Score:5, Insightful)
If you're paranoid^H^H^H^H^H^H^H^Hsensible, wait a week or more to give the rest of the world time to find bugs, test the patch thoroughly in a test environment, and of course ask yourself if you actually need it.
ps. how many of todays slashdot readers know what ^H means?
Unfortunate (Score:5, Insightful)
Bugs like this keep the common microsoft user from installing the latest and greatest updates. They might not understand that their security is troubled until they recent damage; however, they understand this:
"I finally ran windows update... and now I can no longer get on the internet. Crap, I'm never doing that again."
Methinks it's a Microsoft-is-too-huge-syndrome. Microsoft can't test its fixes on every possible configuration; therefore, problems like this will occur. Episodes like this [microsoft.com] have previously occurred and will occur again.
It's the nature of the beast.
btw, thanks Slashdot. I could have installed that this morning!
Davak
Re:Maybe its not on KB because nobody is at work? (Score:2, Insightful)
After deinstalling the update (luckily that was possible, there are updates where there is no rollback) everything worked fine.
I checked again with windows update and the patch wasn't avaialble anymore (this was last saterday), so I reckoned it had nothing to do with my setup, or at least was not the only one.
Re:Why is this news? (Score:2, Insightful)
Anyway, hopefully this is yet another incident that tips a few more to 'switch'.
Re:More Slashdot Sensationalism (Score:2, Insightful)
Re:More Slashdot Sensationalism (Score:5, Insightful)
If (insert your favorite distro here) releases a bug fix, its generally well documented, you get the source if you really care, and you can know exactly whats going into your system.
If MS releases a bug fix, the only way to retrieve it is through Windows Update, you don't know what else they slipped in, you often must have all the other service packs/hotfixes installed first, and (this is the really irritating part) it may change your EULA if you choose to install it. If you don't accept the new EULA, you don't get the exploit-fixing critical update you must have to keep your server clean.
I like and use both MS products and Linux, but severly dislike MS's tendency to grab as much control as they can get away with. They grab until there's a user backlash and either ignore it or back off just enough so it looks to the press like they're the good guys for making a concession.
Re:More Slashdot Sensationalism (Score:4, Insightful)
I'll agree with you on the bias issue. Slashdot for all I can remember (which is a couple of years) was not pro-microsoft. I'm not speaking for anyone, just stating a fact.
But there is a difference between Microsoft and where with Windows Update, you have paid for the update service, and you should expect at least a minimum of Q&A done to a patch. With Linux, well... I can remember some packages I installed in which they gave you a very explicit warranty : This might screw you up, we're not responsible if it does.
I've always installed packages on Linux with this in mind. This might not be the best mentality if we really want Linux on the desktop, but at least, I know what I'm getting myself into.
MS Update makes it seem like everything was double-checked for you, and all is well and good to install... MS even goes so far as to recommend URGENT patches, which may or may not leave you worst off... And this you (should have) paid for. So yes, there is a difference, bias or not, since I paid money for my MS release, whereas my RedHat is downloaded and free... So yes, I should expect working patches from MS, and not expect RedHat to give me the time of day if they dont feel like it.
'nuff said.
Re:More Slashdot Sensationalism (Score:4, Insightful)
You're correct, but one of the reasons Microsoft has given in the past for being slower on security updates than the Open Source community is that they have a much more rigorous regression testing procedure that must be run before release. The idea is to make sure that something like this never happens. It is one of the ostensible reasons that you pay so much more for Windows. If the extensive test procedure is no better than Red Hat's or SUSE's, then that proposition kind of goes up in smoke.
Lots More Slashdot Sensationalism (Score:5, Insightful)
Its not. Well, this wasn't automated, it had to be downloaded from the windowsupdate.com site, but I think we're just seeing something of a double standard here.
Okay
What really gets me is that whenever there's an MS problem the
MS's automated patching system isn't bad, it keeps Joe User updated and there simply will be x amount of problems over y amount of time, as you said just like with any other vendor.
Enjoy the schadenfreude guys, it'll just make real MS complaints sound all the less convincing. Optional supplemental reading: the boy who cried wolf.
Crying wolf is a big problem when criticizing MS to the uninitiated. I have the displeasure of taking a 3 hour class with a rabid anti-MS type and at this point no one takes him seriously because of his zeal, even though 2/3 of the stuff he says are actually excellent points.
Engaging in simple-minded schadenfreude simply makes people look less credible. Seems like a tough lesson to learn for the loud-mouth anti-MS types.
Re:windows update (Score:3, Insightful)
Does this mean only 600,000 XP users trust Windows Update?
Probably only 600,000 users actually bother to use the updates. I know any number of people who just use the software that came on their Win98 CDROM, it never even occurs to them to update their software. Like all the academics at my university using Netscape 4.7x with MacOS 9.1.
don't trust windows update (Score:3, Insightful)
For whatever reason, though, I never use Windows Update, and I don't know that I've ever patched my Windows XP, outside of SP1. Maybe it's because I really only want to use Windows for gaming and not bother with much else, but I think it's also because, when I get something working, it's sometimes through some steps that elicit black magic from Windows, and I'd like the feature to stay working. The most recent example is the Windows XP VPN service, which for whatever reason will issue me an IP I want, and will work with other users' routers, only occaisionally. Windows allows so little control over its features (compared to Linux and others), and VPN is no exception: A set of wizards, so when it works, yea I'd like it to stay working, and this patch warning that VPN may be affected, is certainly only redoubling my avoidance of Windows Update.
We all know the history of Microsoft and patches, so I'm certain that is a sort of "subconcsious" reaction when I see that awful tooltip in the corner. My Windows patching tendencies are highlighted by my almost religious running and adherence to OS X's Software Update panel (alright, I haven't installed the latest iTunes update
No, that's not what it means (Score:4, Insightful)
No, that's not what it means. Users who are savvy enough to know about the 'issues' with Windows Update probably don't use Windows XP, for the most part.
Actually, what this means is that you found a story about Microsoft, and needed a way to trash them, so you came up with a lame rhetorical question.
Honestly, what would you have them do? Not retract the broken update? Around here Microsoft is "damned if they do, damned if they don't". They just can't do right by many Slashdot posters.
Sure Microsoft does a lot of bad things, but certainly retracting a broken is not one of them.
Call them on their bad business practices, sure. But snide remarks like yours only make anti Microsoft people look childish, foolish, and generally make you look like you're really struggling to find something wrong with them.
Anti Microsoft Slashdot Goldmine
1. Find non-news story about Microsoft rightly retracting a broken update.
2. Insert witty, yet trollish rhetorical question.
3. Post to Slashdot.
4. Wait for the Karma to roll in.
5. Profit!
Re:More Slashdot Sensationalism (Score:5, Insightful)
I assume your speaking of paying for Windows XP when you say that you've paid for the update service, or else someone really ripped you off. If that is indeed what you are referring to, then I have an issue with Mandrake, Red Hat, and SuSe because I did pay for them (support the cause and all) and although you say "I can remember some packages I installed in which they gave you a very explicit warranty : This might screw you up, we're not responsible if it does. " -- this is exactly what Windows Update says in it's EULA.
So, I would say that Microsoft does a better job in this aspect. Also, you're going to knock Microsoft because they are pro-actively getting people security updates? Wow, this seems to me like a better way, because we all know that many exploits have actually been patched, it's the sysadmins who don't patch their systems that get hacked.
I know we're supposed to be Anti-MS here and all, and I generally am, but please, don't throw out logic and reasoning when attacking the giant.
Re:Why is this news? (Score:2, Insightful)
Re:That's the problem with automatic patching (Score:2, Insightful)
Poor argument... (Score:3, Insightful)
Microsoft is a software vendor - a software vendor has employees that know, love, and baby their source code to produce a software product. Windows XP is one of their software products. These software developers know their particular piece of the puzzle well - while they may know jack and doodle about another piece of the puzzle within the same product. Nevermind they have no clue on how another piece of software is written from a completely different vendor!
If Microsoft were to release a patch to Windows XP - do you honestly want them to test the patch against the fifty three million software products that are available to run under their operating system? Let's not forget all the legacy versions that are still floating out there.
C'mon - that's ridiculous. It's an unfair argument to state that Microsoft should test against software not written by them. I would expect Microsoft's testing strategy is to make sure that the software does not adversely affect the performance of their own operating system and the software that came with it.
Since we do not have sufficient information about all the software that was affected by the patch, we do not know the whole scope of the problem. All we know is that Symantec's software product conflicts with the latest update.
If five software products out of fifty three million are broken while the remainder has absolutely no problem - would it not be safe to say that the problem does not lie within the patch, but perhaps the coding practices of the five software products that have the conflicts?
Unlike what I would have expected from Microsoft, pulling the patch was the right idea. I imagine their quality department immediately dispatched a request to Symantec to evaluate the possible conflict and to work a resolution as a fast as possible.
Re:If only they had apt-get (Score:3, Insightful)
Just a thought.
Dave
Come On Now... (Score:4, Insightful)
Re:Why is this news? (Score:1, Insightful)
Re:That's the problem with automatic patching (Score:3, Insightful)
Not easy to do.
Think about it. QA on Linux has the advantage that the first "users" of any new module/driver/system are actually developers and other savvy users. Many bugs get worked out relatively early -- certainly before they get rolled into a stable distribution.
The Windows OS has to support a nearly infinite variety of hardware, and. It doesn't have the same first-tier of support. Sure, it has beta testers, but, by and large, they aren't developers. They certainly can't tweak the source.
But even then, security is not easy. Think about Open BSD. This OS's community prides itself on its approach security, and they do a very good job. But occasionally, things sneak by (i.e., the SSH remote exploit of a year ago).
So it's nice idea to just do things right the first time. But you can't just make the decision "hey, from now on we're gonna do things right" and have the problem miraculously solved...
Re:windows update (Score:4, Insightful)
I mean, think about it
If it were such a "simple error", it would have happened to ALL of the 600,000 people who downloaded the update. Crap happens. QA isn't an exact science -- there is no algorithm you can follow to make sure you find 100% of all bugs in existance. The best you can do in this case is find the problem and make sure you test for it in the future.