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.

Comments

Satnav

[Anonymous Coward]

Having fun in Satnav's involuntary public beta testing program?

Re:Satnav

[nmb3000]

Having fun in Satnav's involuntary public beta testing program?

No worries, I'll just disable automatic updates until they sort it out.

Wait, I can't do that anymore? Oh.

Okay then, I'll just not install the optional KB3206632 update.

Wait, the only option is the December Rollup Update package? I can't disable single updates anymore? Oh.

Okay then, I'll just look for my Windows 7 installation DVD and abandon this Windows 10 shit.

Wait, they forced the same update model onto Windows 7 users? Oh.

Okay then, so Microsoft changed their update model to take away all customer control, fired most of their QA department, and now releases update after update with bugs and problems?

Well, fuck Microsoft.

Networking.....Windows Update?

[segedunum]

Always on updates................ How do people get the update fixing the update when you've broken their fucking network you dumbasses?

Re:Having fun yet?

[arth1]

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.

Re:I tried to get the patch

[Anon-Admin]

I'm sure some people probably thought their computers were broken and took them in for service,but since they couldn't get on the internet, most people probably called their ISPs, who have technicians in India who have no troubleshooting skills beyond asking them to reboot.

I fixed that sentence for you.

Re:I tried to get the patch

[Immerman]

Yeah. Seems to me an awful lot of affected people ought to bill Microsoft for having a tech guy come set things right for them. Even accidentally breaking the means of acquiring repairs is a special sort of evil.

I know it's not exactly difficult to manually assign an IP, but only if you know what you're doing.

Re:Yet another result of decimated QA

[UnknowingFool]

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.