Again?
You have to laugh at the fact the updates are referred to as Quality Updates, yet the seem to lack that attribute.
That said, my machines didn't have a problem with it.
Microsoft has offered a resolution for widespread reports of issues from Windows 10 users attempting to install the latest cumulative update. Users took to online discussion boards to vent their frustrations over the KB5031356 update failing to install. Many said they were presented with the 8007000D (ERROR_INVALID_DATA) error …
Updated 6 - Win10 22H2 boxes Wednesday. 4 out of 6 suffered hangs at 40 and 76%. 1 suffered a reboot loop that required "DISM /Online /Cleanup-Image /RestoreHealth" to fix. All HDD boxes suffered hangs, 2 of 4 SSD boxes suffered hangs. Restarting to install the "pending installation" updates and resetting the current stuck update using the "Restart Now" button (when displayed) also worked around a hang on one box.
Update install time ballooned to more than 2 hour with required troubleshooting on boxes with hangs. Boxes with no hangs installed all updates/patches in less than 30 minutes and completed updated windows defender and re-indexing scans. No slowdowns noted on any of the 6 boxes after updates installed, but boxes are a mix of business use desktops and laptops, though the laptops do use the proprietary Nvidia driver - no non-gaming slowdowns noted. They may do just fine gaming as well - but no games are installed to test.
This issue didn't just start with October patch Tuesday, but similar partial updates were also observed during the September patch Tuesday updates as well. Seems all users receiving updates from MS are now members of the "windows insider's program" who get to do beta-testing of updates each patch Tuesday...
So that's how that poxy thing got there. My parents were upset about something that showed up on their computer (Windows 10), but couldn't tell me what it was. When I got to see it, it was firstly that the Windows Search widget/whatever was on the taskbar again (they don't use stuff like that ever, if they search, it's in their browser and they don't lose their files etc.), and it had brightly coloured icons, a book and a wheel chair or lounge chair or some stupid shit.
That was "Search Gestures" (huh, aren't gestures some movement thing with your pointing device?) setting in the right click menu. So then I think, maybe I should reduce it to an icon instead of hiding/disabling it. So I click this icon, and what pops up with it? Side panes with spammy tiles like the ones that used to be on the start menu (that I cleared lol). Back to hidden again.
By the way, Windows 10 and its disruptive (and at the time, very wrongheaded driver updates replacing vendors') and time consuming, forced updates made my self employment gig of on-site service impractical. I'd get there, start assessing things, and the next reboot could have been 2 hours of gyrations, the outcome of which I'm now stuck holding the bag for. So when COVID started, it was a great excuse to just stop doing that and not get back to it. So I don't see Windows very often anymore, only when I have to see family members' computers.
On openSUSE Tumbleweed (or similar) you get like 2000-3000 updates a WEEK sometimes and such catastrophic or system downing reports are rare. Even if they happen, they offer "fraction of a second" rollback mechanisms such as "snapper".
I remotely connected to 2 critical machines running Windows in panic after reading this story, they seem to be updated fine but this is absurd. These are also critical security updates and in that specific location they _have to_ be updated since they are exposed to Internet and local network.
This must have cost a lot of people a lot of downtime and cash. Why is Microsoft not forced to pay compensation for each and every case? Maybe the clowns running our declining nations can pass a law enforcing that.
After the first few billion, they may start to be a bit more careful with their crapware.
Instead of targeting social media companies for things that their users are responsible for, target Microsoft for things Microsoft is responsible for.
Money is really not that important to the people with money. They like to pretend it that it is, but, that is just their way of moving the discussion to a prepared battlefield where they have the upper hand.
IOW, this means nothing, they will continue to license Windows because Bill has such a nice barbeque for top-tier clients - or whatever it is they actually value.
I wrote a script for the issue when "200+" updates were to be installed, which usually failed to ever finish.
It installs one update after the other until one requests a reboot, which it then does instead of installing more. Together with a scheduled task for automation and over 50 reboots even problematic boxes manage to install everything.
Not a thing anymore though. Instead of releasing individual updates for each issue, they are all munged together into a single monthly Frankenupdate.
If you don't want to update because of one issue, you have to put up with being vulnerable to everything else until the fixed update comes out.
That Frankenupdate is a real threat all by itself. Microsoft pushed the monolithic patches to reduce the load on it's own operations, not for our benefit, and it shows in the months where there are truly critical updates paired with low threat garbage and feature enhancements.
While it is unlikely for M$ to go back to individual patches, maybe they need to be forced to split out critical security and stability updates into their own bundles, so that the scope of a bad patch for a less critical patch or a feature update doesn't block us from fixing a "brown pants" class fix separately. That is still a manageable test matrix, and the OS can chain the updates.
We have had to put up with the near constant SSU updates as a separate install and often reboot, so the idea of splitting up the monthly bundle into critical stability, critical security, and the rest of the kitchen sink shouldn't be unreasonable.
"Feature Enhancements" seems to be, these days, Microsoft code for "We found another place to cram in adverts for Edge and ways to steer you towards a Microsoft account".
I'm still bitter about the %&@$!-annoying "Microsoft Points / Microsoft Account / Reset your browser to Edge" crap-banner that infests Windows 10's Settings app.
There used to be a way to remove it with Vivetool, but of course Microsoft closed that loophole ASAP. Far more important than fixing security issues, yes?
OK, rant over. Thank you for listening.
Indeed. It wasn't finally fixed until Windows6.1-KB3138612_Mar 2016 Windows Update Client fix iirc. Remember the obtuse strategy of installing an update and then having to install the servicing stack update last to be ready for the next set of monthly windows updates? By the time they came around, parameters would have changed. It was a broken system for so long. It tended to hang indefinitely or refuse to install certain updats. Never could figure out why they did that instead of installing SSU first and then the updates that could have been paired with it.
Ditto, I suppose, although I think my update took a bit longer and was a little nerve-wracking:
My initial post-download, pre-restart install hung at 9% for *at least* 20 minutes (probably closer to 30); followed by a computer reboot rather than a windows restart — which I know because the Windows boot menu I'd enabled appeared — followed by *something* getting installed from 1% to 100%, with a non-standard progress display at the bottom of the screen; followed by another computer reboot; followed by a standard Windows update progress display going from 1% to 100%; followed by *another* computer reboot; followed by *another* standard Windows update progress display going from 1% to 100%; followed by a normal Windows restart (sans boot menu); followed by the Welcome screen. After logging in, I ran Windows update again, and a type of update for Windows Defender I don't recall seeing before got installed without requiring a restart. I then manually restarted Windows for good measure (as I usually do); Belarc Advisor gave me a clean bill of health; and I disabled updates using Sordum's Windows Update Blocker (as I always do between Patch Tuesdays to prevent drive-by updates). ShutUp10 didn't flag any reactivated privacy vulnerabilities and, most importantly, my computer isn't behaving any worse than it was before — in contrast to a few/several months back, where the Patch Tuesday install *seemed* to go smoothly but a number of things in Windows got borked and I had to restore a pre-update Macrium Reflect drive image for the first time and wait for a "fixed" update to become available.
VERY long story short, I guess I got lucky too. Still, though, it usually only takes me around five minutes to install Patch Tuesday updates, too. The LONG hang at 9% and the very unusual sequence of reboots had me on the verge of feeling anxious. If this story had popped up before Sunday, I probably would have held off, notwithstanding the three critical zero-day vulnerabilities that got patched. Speaking of which, back in the day when Windows Update was still serving up discrete updates for Windows, it was easy to vet Windows updates before installing them. If any of them were problematic, *someone* would post about it on the Net within thee days, tops. Nowadays, Windows-update bug reports seem to have all but disappeared from the Internet, or are showing up much later, like this one. Curious.
> "Just a few minutes lost time, not a lost device."
> Devices are replaceable. Time is not.
Devices are not instant replaceable as you suggest. Replacing my work machine costs a lot more time than just a half hour. And don't forget other peoples time in that process. Getting it back to workable state once it is in my hands is fast though, I do take care of my backups - even though not mandatory since the device is meant to be replaceable. But just restore, boot up and go on is still faster.
"Devices are not instant replaceable as you suggest."
I did not suggest any such thing.
"Replacing my work machine costs a lot more time than just a half hour."
That's your Boss's problem. If you can't work, go home and mow the lawn or paint the kitchen or cook your .sig other supper.
"And don't forget other peoples time in that process."
I'm not. See elsewhere in this thread.
"Getting it back to workable state once it is in my hands is fast though, I do take care of my backups"
Good for you. But wouldn't it be better if a company the size of Microsoft made certain that it was unnecessary on your part BEFORE shipping the broken update?
"even though not mandatory since the device is meant to be replaceable"
Again, that's your Boss's problem.
"But just restore, boot up and go on is still faster."
It is nowhere near as fast as update and just get on with it, no reboot required.
> That's your Boss's problem. If you can't work, go home
Classical "I don't care about the company I work for" answer, quite often combined with "easy replaceable workforce". Nice!
> It is nowhere near as fast as update and just get on with it
So you suddenly agree with my initial point? Interesting contradiction with yourself!
> no reboot required.
You know the topic is Windows Updates, hm? Dream on. Even Linux updates often require a reboot, else the kernel stays old and may be vulnerable.
Do what I do: The base installation on my laptop is Debian, Windows runs in virtual machines.
This delivers several benefits: Windows is easy to back up and restore by simply copying the VM's virtual disk files. I can also have several installation of Windows - one for each system environment that I work with. Each Windows installation is much more stable because I'm not installing anything else than Visual Studio and any other tools that I need for the specific environment and there's no problem with conflicting updates or accumulating registry cruft due to multiple install/uninstalls. If a Windows update is taking ages (as they tend to), I can fire up another Windows VM and work on something else while the first one is grinding through its update.
I've worked this way for over 15 years now and it has given me an incredibly stable and resilient working environment.
Point is that Microsoft has no inalienable right to waste the time of billions of people. And yet, here we are.
Two billion people each losing "only" 15 minutes equals a half billion hours. That's a hair over 57,000 man-years. Wasted. Now extend this to the number of fucked up "updates" that Microsoft has foisted on the great unwashed over the last 20 years or so.
It's not a matter of being in a hurry. It's a matter of wasted time.
"I first met that nonsense with DEC software in the 1970s, but I wonder if it is even older than that."
I first heard it at SAIL in the late 1960s. Later, I heard it originated in the TMRC at MIT in the 1950s ... but as I was setting up my Uncle's first computer in 1987ish, I used the phrase regarding Procomm. He told me it was fairly common when he was serving in the Pacific in WWII, so perhaps it's US military slang?
I'm willing to bet the concept goes back millennia ... for example, the inventor explaining mankind's first recurve bow.
It's not nonsense, it's just how things work.