ranted wrote about the fact that a Microsoft update effectively knocked Windows 10 computers off the Internet. In the same article, I also provided a fix that worked for my customers and I said this:
In an ideal world, Microsoft would fess up to this and offer up a remedy. But as I type this, they haven’t. That’s a #fail on Microsoft’s part. I guess it’s easier for them to just pretend that this issue doesn’t exist. And that’s a shame.
Well, it appears that Microsoft has offered up a remedy and kind of fessed up to the issue. In the original article, I linked to a Microsoft web page from their discussion forms that says that they were investigating the issue. It has since been updated to say this:
KB3206632 was released to resolve this issue. Customers should first take the steps above if they are unable to connect to the Internet, and then install the update. You can manually check for updates by clicking Settings, Update& Security,Windows Update and click Check for Updates. Click the Update History button to verify it if has already been installed. For most others, KB3206632 will be installed automatically. Visit the Windows Update FAQ for more information on keeping your PC up to date.
Note: This issue is limited to PCs running Windows 10 version 1607 that have not been restarted recently, and with network adapters unexpectedly showing an IP address in the 169.x.x.x range.
So I dug into what this patch does. Here’s what it says that even remotely matches this issue:
- Addressed a service crash in CDPSVC that in some situations could lead to the machine not being able to acquire an IP address.
Of course, Microsoft assumes that people would see this on their discussion boards and take action by downloading this on a computer that was still on the Internet, sticking the update onto a USB stick to install onto the malfunctioning computer. Because they’re sure not getting this via Microsoft’s Software Update mechanism seeing as the computer was knocked off the Internet. But that isn’t what happens of course. I say that because in this case, the computer gets punted off the Internet. The person who owns the computer can’t fix it and someone like me gets a phone call. I fix it and hand the person who owns the computer (or in some cases computers) a bill. Maybe those bills should go to Microsoft as this could have been easily mitigated if users had the ability to not be force fed updates as forced Windows 10 updates are a horrible idea.
Speaking of Microsoft. I’d like to direct this paragraph to them. It’s nice to assume that the code that you release to users is solid. But there are times that it isn’t. That’s life. I get that. And as a result, users need have the option to be told that an update exists, but defer installing it a day or two to see if an early adopter who installed the update the second it was available broke his computer and raged about it online. If you allowed Windows 10 users to do that, you would not be getting all this bad press right now because you broke their computers and potentially cost them money to fix them. I don’t think your forced update strategy is really working for your users. Thus maybe you rethink that strategy before something really, really bad happens.
Just some free and friendly advice for you.