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

[Anonymous Coward]

I have to wonder about this specific bug. They fucked up DHCP? Doing what to it? The DHCP stack isn't something that needs regular tweaking; it's not like there are new features being introduced to DHCP all the time. The protocol is mature and relatively static, and the DHCP client in Windows has been robust for years. Even XP's DHCP client was rock solid, fully IPv6 aware, etc. There's nothing to be making changes to in that codebase. Just as I wouldn't expect CALC.EXE to get updated (and suddenly quit working) unless there's some major new discovery in mathematics that redefines how a calculator should operate, I wouldn't expect the DHCP client to be getting buggered when there haven't been any breakthroughs in IP lease assignment.

So what the hell they were mucking around with - adding more spying? Everybody gets a persistent route to FBI HQ in their config?

Re:Satnav

[fuzzyfuzzyfungus]

Reports mention that the failure to acquire an address is, at least sometimes, tied to the "Connected Devices Platform Service" crashing. Apparently this service is "used for Connected Devices and Universal Glass scenarios", which really clears things up.

Nobody seems to have much to say on what exactly the 'connected devices platform' is; but it sounds like the problem isn't with the DHCP client itself; but with some questionably sensible abstraction layer failing at automagic above it, in the service of some windows-everywhere-in-the-connected-home fever dream.

Sort of like the time they broke all those webcams, not by monkeying with UVC support; but by quietly inserting a poorly thought out frameserver without telling anyone because being able to log in with your face is obviously more important than Directshow working as expected.

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.

I tried to get the patch

[Anonymous Coward]

But I couldn't get online.

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

[JustAnotherOldGuy]

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

I know what ya mean- for some reason my grandma just never got the hang of configuring DHCP or assigning static IPs.

I tried to email with instructions her but she never responded.

Re:I tried to get the patch

[Anonymous Coward]

I had this happen to 1 machine at work, and did this to fix it:

netsh winsock reset catalog (Reset WINSOCK entries to installation defaults)
netsh int ipv4 reset reset.log (Reset IPv4 TCP/IP stack to installation defaults)

All of that cryptic command-line mumbo-jumbo just proves it: Windows is not yet ready for the desktop.

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:Networking.....Windows Update?

[arth1]

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...

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.