Slashdot Mirror
Windows 10 Update Broke DHCP, Knocked Users Off the Internet (arstechnica.com)
Microsoft has quietly fixed a software update it released last week, which effectively prevented Windows 10 users from connecting to the Internet or joining a local network. From a report on ArsTechnica: It's unclear exactly which automatic update caused the problem or exactly when it was released -- current (unconfirmed) signs point to KB3201845 released on December 9 -- but whatever it was appeared to break DHCP (Dynamic Host Configuration Protocol), preventing Windows 10 from automatically acquiring an IP address from the network. There's also little detail on how many people were affected or why, but multiple cases have been confirmed across Europe by many ISPs. A Microsoft spokesperson has meanwhile confirmed that "some customers" had been experiencing "difficulties" getting online, but that's about it for public statements at present. However, a moderator on the company's forums has said the fix was included in a patch released on Tuesday called KB3206632.
Having fun in Satnav's involuntary public beta testing program?
But I couldn't get online.
Is there anyone out there that is not yet aware that this is basically one giant beta test?
Yes, me. A beta test means that there is a plan to release a finished product. I see no such plan.
Always on updates................ How do people get the update fixing the update when you've broken their fucking network you dumbasses?
Simple. You buy and install a server that can feed a pxe environment through bootp, and install the patches that way...
OpenSSL has a serious vulnerability for 2 years and nobody bats an eye.
I assume you are referring to HeartBleed.
Let's start with the obvious: OpenSSL had a vulnerability which no one knew about for 2 years. As soon as it was discovered, a fix was issued 6 days after the bug was discovered.
Now let's talk about the details: Heartbleed was a vulnerability which would allow someone to undermine security of OpenSSL. It didn't stop computers from functioning outright.
Lastly, EVERYONE treated Heartbleed as serious. Your assertion that "nobody bats an eye." is an outright lie.
Microsoft has a network issue for a week and the Linux fags line up to crucify people. What a community of hypocritical fuckwits.
Way to downplay the problem which is not entirely accurate: MS released an update which borks their customer's internet connection.
Well, there's spam egg sausage and spam, that's not got much spam in it.
Dude, 1996 called and wants its joke back, but you missed the call because you were on the modem.
Proving (yet again) that the claim made by open source advocates of "many eyes make bugs shallow" is bullshit. The reason that the bug went unnoticed for 2 years is that nobody was looking at the source code. Not even the people who wrote it.
Except someone did find it, even if it took awhile. How does that work with a closed-source product like Windows? How many critical vulnerabilities are lurking in there, perhaps bugs or perhaps intentionally introduced at the behest of governments, and simply cannot be discovered because the source isn't available?
"BSD: Free as in speech. Linux: Free as in beer. Windows 10: Free as in herpes." --Man On Pink Corner in #52607549.
How do people get the update fixing the update when you've broken their fucking network you dumbasses?
I'm sure the Microsoft people never thought of this and the Slashdot people are smarter. After all we only ran a story a few days ago about how this problem is transient and doesn't persist through a full restart, which is precisely what Microsoft is telling people to do. (It was also mentioned in TFA)
This is one of those issues which will affect some Slashdot users more than mum and dad's, not because the Slashdot users are more technically minded and mess with their machines, but because they seem incapable of doing something as simple as reading.