Botched Microsoft update knocks Windows 8, 10 PCs offline – regardless of ISP A broken software update for Windows 8 and 10 is knackering internet connectivity for users of several ISPs in the UK, Europe and quite likely beyond. Virgin Media in Blighty is the latest provider to confirm the dodgy code is knocking a number of its customers offline. Proximus in Belgium also says a Windows 10 update is …
"A Microsoft account and internet access" are required by Win10 in order for you to use your Microsoft cloud account from Win10. Since I don't do that, I don't require a Microsoft account, and unless I want to use the internet, I don't require internet access.
It's alright though, that was intended for people who don't know what they are doing.
I have lost count at how many problems Microsoft's new-found love for 'agile' has spawned.
I don't see where agile comes in all of a sudden.
It's a standard Microsoft update.
Only now it comes without docummentation in the middle of the night and borks you off the Internet so as the plan was to make you dependable on an Internet connection, there is some sort of weird reality collision (MEGASHRUG) and as a civilian you are a bit screwed, right.
Anyway it was probably Putin all along, out to undermine democracy. You know it's true!
<quote>And it's a supreme irony that Windows 10 requires you to be online to use it and yet once again here we are watching it furiously stomping on its own cut off its dick. I have lost count at how many problems Microsoft's new-found love for 'agile' has spawned.</quote>
There, FTFY!!!
<quote>If computers were people we'd have convened at the Hauge by now and put Microsoft on trial for genocide.</quote> BUT, if that were to pass, who would face the firing squad??? Bill G? Ballmer? SatNad?
[quote]
What other branch of engineering allows so many to believe "Build Now, Plan Later" is a recipe for anything but disaster?
[/quote]
Looked at the vehicle and roads industry lately? Initially it was built ad hoc, & later planned but added to the original layout. Just look at how the London streets run!
Operating systems have grown in the same way. Built up layer upon layer & still having issues from the original design flaws. Same reason for the Y2k panic... "This code will be completely replaced by then!" Nope, just patched & built upon. Windows is not different, nor is Unix, iOS or Linux (which, I believe are respectively, based on it* & designed to be a free 100% compatible alternative to it).
Then you get strange interactions between your new bit of code and something written 10 years ago, that no one remembers even existed...
*I could be wrong, I often am. But you have to go with what you know & just note & question your assumptions as you do...
Pretty sure it has absolutely nothing to do with ISP whatsoever. My users on remote sites get their IP (or not, as the case may be!!) from our SBS2011 or 2012R2 boxes. None of our users at any of our sites get their IP from the router. So I don't see how it can relate to the router, and therefore the ISP. I think it's purely client-side (since our servers haven't been updated/bounced for a while).
And the problem first reared on one laptop on 7th November. Nothing would get it to connect, whilst the rest of the office was happily working. Got said laptop sent to different office and it connected fine.
funny enough we've been having random DHCP issues with *some* win10 boxes for a while. All are win10 dell OptiPlex 7040AIO or 7040 micros (both have the same Intel NIC chipset) win7 works fine. Symptoms are random but users lose there connection and when you check the machine has picked a 169.x.x.x address up, normally a ipconfig /release renew fixes it or a reboot but not always. This can happen even when the PC is well within its DHCP lease time so shouldn't even be trying to renew its IP.
" users lose there connection and when you check the machine has picked a 169.x.x.x address up,"
That's an APIPA address - it's the IP range microsoft PCs give themselves if they detect a network connection, but don't get a response to a DHCP request. It was designed to allow home networks of PCs to have LAN parties back in the late 90's to get all PCs on the LAN to have a working IP address so they could connect to each others PC and play network connected games together.
I knew there was another reason for paying a fiver a month for a static IP.
That would be a WAN IP address. This issue appears to relate to DHCP which manages LAN IP addresses.
In more detailed terms: The issue seems to relate to the way people's routers are handing out addresses to Windows 10 machines on their LAN (or the way those machines respond to that advisement). Your static IP address relates to the way the world communicates with your router over the public internet.
Well he could be using his fixed IP address directly on his PC. I do one some of mine.
The issue isn't to do with the router except is as much that most people use their router as their DHCP server. But regardless of what you are using as a DHCP server W10 was knaggered it. The DHCP server is happily responding to requests and offering configs and it looks like W10 is just ignoring these responses.
It appears to be the DHCP client in Win 10.
Customers with Win 10 and DHCP, as apposed to customers who use manual configuration, have been a headache. It's the ISPs and retailers who are left to pick up the pieces 'cause of Redmond's screw-up. Don't we just love he new update mechanism in Win 10? SPIT, SPUTTER, CURSE! No way in hell!
there was a very good reason not to 'upgrade' to win10 from win7 while it was free
However, how does the borked update affect someone who runs his virgin(spit) modem in cable mode and uses his own belkin router to connect the computers/printers/backup hard drive to each and the internet?
....Started seeing it last week as well, although in the first instance there had just been a lot of work done at the customer end, so it wasn't obvious what the problem was. Looked like a CPE issue for some time. Seen this across all sorts of different devices handing out DHCP leases.
Try disabling power management on the network adaptor, should keep it alive in sleep:
Control Panel > Network & Sharing Centre > Local Area Connection > Properties
'Power Management' Tab - Untick 'Allow the computer to turn off this device to save power', usually does the trick :-)
(Sorry if I'm teaching you to suck eggs!)
so - if an MS update breaks your PC and those of your employees, so they can't work but you have to pay them anyway, how do you recover that cost from MS? If they're using innocent bystanders as beta testers (which they must be, anything that borks things this much would surely not pass a decent ISO-compliant software test/QA/release process), then they should be paying businesses for taking that risk ....
You agreed to the EULA which says that you owe MS everything and they owe you nothing. If you want compensation you'd have to convince a court that the EULA wasn't a reasonable contract (it isn't) and that you basically agreed to it under duress (you don't have any choice). Then you might be able to go after the compensation you (and all the rest of us) rightly deserve. However MS will spend more of legal fees than you, so they'll win.
"Then you might be able to go after the compensation you (and all the rest of us) rightly deserve. However MS will spend more of legal fees than you, so they'll win."
Government's should do this, and I'm sure they can take on MS.
EU seems keen on doing this sort of thing.
Government's should do this, and I'm sure they can take on MS.
EU seems keen on doing this sort of thing.
Sadly they don't seem keen on wiping the whole EULA thing off the face of the planet. I really wish they would as no one else it likely to manage. Of course if the judge's PC were to bork part way through the trial it might help. If they felt the pain the rest of us do they might well reach of the black cap.
Of course if the judge's PC were to bork part way through the trial it might help.
One of those forced reboots while the judge is busy writing the summing-up notes, with no chance to save (and auto-save files somehow wiped), and a 40min+40min shutdown and restart for "installing updates" should pretty much seal it I think.
(Disclaimer : Never inflicted myself with the horror that is 10, so no idea how much actual warning you're given)
The Register - Independent news and views for the tech community. Part of Situation Publishing
Biting the hand that feeds IT © 1998–2021
