How many times is MS going to fuck up their own networking capabilities & expect us peons to somehow magicly download the fix over that bricked network connection?
Hey Microsoft! It's called DUE DILLIGENCE, you should try it!
Microsoft has issued an out-of-band Windows 10 patch to fix a self-inflicted error that can crash devices that attempt to access Wi-Fi networks secured with Wi-Fi Protected Access 3 (WPA3) standard. The code landed in a January 21 preview build of upcoming Windows 10 and Windows Server releases. And then it landed in KB4601315 …
No need to download anything.
Select the Start button, then select Settings > Update & security > Windows Update > Advanced options > View installed update history > Uninstall updates.
Select the update you want to uninstall, and then select Uninstall.
You’ll need to restart your PC after uninstalling the update because this is Windows we are talking about.
Unless you can’t get into a Wi-Fi network because of the bug, in which case The Register wishes you a happy weekend figuring that out. ®
There still is such a thing as a network cable. If your computer doesn't have an RJ45 receptacle, it becomes more fun, but with a USB to RJ45 converter, that can be solved as well.
"There still is such a thing as a network cable. If your computer doesn't have an RJ45 receptacle, it becomes more fun, but with a USB to RJ45 converter, that can be solved as well."
Great, I'll just order one from Amazon... oh wait Ok I'll go and buy one from a local shop... oh wait.
I'm sure the audience of The Register will have no problem going to one of their myriad of machines to get the patch installed. The problem is the old guy at home who turned on his laptop this morning and it blue-screens. He's not going to have any of that laying around and he's not going to be thinking "lets check out the Microsoft patch releases".
It's inexcusable to break stuff in this way, if it happened to any other piece of home tech people just wouldn't put up with it.
I hate to think what is going to happen when all us old farts retire and we have to rely on the Minecraft Generation to fix anything. If anything happens to the cellphone towers so they can't download a YouTube video, civilization is doomed...
This post has been deleted by its author
It used to be the default that you could control your own device in a simple manner. Did not need to fake being an IT pro and create group policies (explain that to grandpa).
The realm of controlling your own computing device is now solely in the hands of the Open Source operating system vendors.
Regular Windows, Apple and Android users are led to the (data) slaughter.
"Is there anything out there to defer the update for a month, gives them chance to fix the BAFU's"
Next month is going to be a different broken thing, so waiting a month is not better, just different. This one is worse than usual, but they could have easily delivered it next month, the timing is random.
My solution is to turn off the wifi before booting into Windows, and *never* update. Since it doesn't ever connect to the network, it doesn't need updates anyway. The Linux and Mac boxes go on the network, so they get updates.
This snafu is oddly reminiscent of the under-reported incident a couple of years ago when Google emitted a Chromecast update which rendered them unable to connect to networks powered by TP-Link branded routers (it really was that specific). After a few weeks they issued a patched version of the firmware but that still meant those with stranded devices having to jump through hoops to connect them to an entirely different network briefly to receive the OTA fix.
This stems purely from an attitude of overestimating their competence and declaring that if it works in a test in their labs it'll work everywhere.
They just won't admit that they need an easy to use cumulative patch manager built in to the OS, which does more than simply download gigabytes of stuff and spew it into the filesystem. This needs, above all else a rollback function that enables users to look at installed patches, and roll them back with a button click on the regular occasions that updates break vital stuff. Of course this would also require their patches to be limited to actual changes in order not to chew up vast amounts of storage keeping the old stuff available before it gets overwritten.
But even if they did this, it wouldn't take too long before they discovered loads of problems in the patch manager and had to patch that, breaking it too, so really it's just a hopeless situation..............
I haven't used Windows since Win7 so my memories might be distorted, but back then I don't remember patches going wrong, at least not that often or that bad. IIRC I only started being wary of Windows Update when Microsoft started trying to forcefully shove Win10 down my throat. Is it me, or has update quality gone downhill real fast?
While I am not sure about this... but I think that Microsoft's critical flaw in their two feature releases per year is catching up to them.
So, a standard windows release has 18 months of support. With two releases every year, that's roughly three supported editions of Windows that Microsoft must support at any given time.
Throw in the LTSC version of Windows which has mainstream support for five years and extended (security only) for an extra five years for a total of 10 years of support. Oh and they release those about once every three years, so on average another three supported versions swinging in the breeze at any given time
So, with just the Windows client, Microsoft has to support six versions of operating systems and one of them could be approaching 10 years of age. Multiply in the subtle differences between different flavors of Windows (pro vs home vs enterprise vs pro workstations vs LSTC vs S) over those supported versions... like how LTSC has no UWP support... (worth its weight in gold I say!)
Overlay that shitshow with Windows server and they've gone into plaid.
Why, they did support several systems back in time too: When they launched Win10, they were still supporting Win7, Win8 and Win8.1, in all their variations (Home, Pro, Enterprise, POS, whatever). Earlier in Win8 times, Win7 and WinXP were still in support.
My point is this isn't a new situation and shouldn't cause the issues we see. It looks more like Windows isn't a priority anymore, having slipped from flagship to freebie status.
Thank you for proving my point. There's now up to six supported editions of Windows Client, excluding the variants. Twice as many as they did back in the Windows Vista/7/8 days.
Instead of having a three-year cadence between "Feature Releases", its now six months. I'm sure that Microsoft didn't shed their entire dev team in the period between Windows XP to Vista, or Vista to 7, or 7 to 8, so on and so forth. I'm sure they were busy making the next OS, or squishing bugs, or whatever it is that developers at massive companies do in-between RTMs.
And as an aside... Windows 8.0 support died six months after the first edition of Windows 10 (1507) was released. When 8.0 came out, XP only had 18 months left of support and when 8.1 came out, only six month of overlap. All told, there wasn't really that much time where Microsoft was supporting more than two "feature releases" of Windows.
One Dell system I had to wait a long time for 2004.
Turned out that some drivers related to Thunderbolt needed updating before it was suitable to upgrade.
Dell update utility identified all the out of date drivers but hung when trying to apply them.
Much cursing and manually installing each patch later all was up to date.
Then some days later the update appeared
Biting the hand that feeds IT © 1998–2021