Microsoft Says Windows May Need Up to 8 Hours to Update
tomshardware.com
tomshardware.com
From the actual release: "One of the most impactful things we explored was how much time a device needs to be powered on and connected to Windows Update to be able to successfully install quality and feature updates. What we found is that devices that don’t meet a certain amount of connected time are very unlikely to successfully update. Specifically, data shows that devices need a minimum of two continuous connected hours, and six total connected hours after an update is released to reliably update. This allows for a successful download and background installations that are able to restart or resume once a device is active and connected."
What the are saying is "you need to be able to reach the download server for at least 8 hours after an update drops in order to reliably install it."
Is very much meaningful
But FWIW, my mornings usually consist of updating everything for me, personally. I never have updates happen unexpectedly. There's a script I run when I sit down to my computer for the first thing, every single day.
It's part of normal operation for any CPU/GPU released in last 10 or so years.
There is a reason why intel advertises a regular and "Boost" clock speeds. Boost clock is not sustainable without heavy duty cooling and the CPU will throttle down once it's heated up.
I don't know if it still holds, but some older systems also had a third category of throttling in between the normal speed range and an emergency power off. They would stutter badly as if they were applying some duty cycle and alternating between a suspended state and a slowly clocked state. This would show up as really frustrating IO buffering and UI latency, similar to how a machine might behave if it were stuck in a virtual-memory swapping storm and processes would freeze/unfreeze sporadically.
Linux has warts, but being able to switch on your computer and definitely use it is pretty important.
So I just accept as fact of life that on a Asus 1215B, bought with Linux pre-installed, I have to reboot the network configuration every now and then.
I guess it is still better than when Canonical replaced the wlan driver with a half-working one because FOSS rulez, or having 3D capabilities downgraded to GL 3.3 support, when the legacy AMD commercial driver was capable of GL 4.1.
In windows, some problems are simply outside of your control, or if you dip down into the registry to fix them, and that's possible, then your fixes can get unfixed on update.
To be honest, I just find it mind-boggling that all around the world, there are offices of high-paid professionals waiting for windows to finish updating minecraft before they can actually do some work.
I have to become a kernel hacker and AMD driver contributor to fix them?!?
Don't get me wrong - I find that kind of thing annoying too. But it's nothing compared to the Windows approach of interrupting your work to give you a popup about 'connecting your device' or whatever.
Computers being "out of date" doesn't stop them from working, it's most often updates that break things.
99% of things work as expected though.
I'll probably move to linux soon.
https://www.forbes.com/sites/jasonevangelho/2018/12/12/micro...
I have had the situation when the update was downloading for a long time then indicated that it had failed, wasting all the data that was already downloaded, probably around three quarters of a gigabyte.
On the other hand, I have an OS that updates individual apps and individual libraries. If something fails along the way, at least I have updated most of what was downloaded, leading to little wasted data.
And that be perfectly fine if it didn't do it in a middle of presentation. And yet here we are.