TR Forums

DancinJack wrote:

Redocbew wrote:

I don't know of any "other OS" which does that, but maybe that's just me.

Unless you mean how linux installs new kernels side by side with the old one and doesn't switch over until you reboot, but that's not really the same thing as installing an entirely new image. It doesn't seem like the recent snafu's with windows updates have really involved the kernel much either.

Android does (and I'm sure some other forms of Linux do it that we don't know about).

ludi wrote:

synthtel2 wrote:

It's a short interruption by the time you get to 60 Mbit, but it's still an interruption (with opaque and inconsistent behavior, even).

The inconsistent behavior I'll grant (and have seen it, particularly in the networking subsystem), but I think the rest of that is your tacit admission of exaggeration. Not everyone can get a 50+mb connection but anyone that can get at least 10mb will be able to deal with the update process more or less gracefully.

ludi wrote:

And given that the majority of systems in the wild will never be updated manually, I'll take the mild inconvenience of the auto-update process over the drive-by system pwnings and botnet attacks that characterized the latter days of XP and, to a lesser extent, Win7.

synthtel2 wrote:

Gaming isn't exactly a mission-critical workload. People do run mission-critical workloads on desktop Windows (though I recoil at the thought for reasons such as this), and WU has screwed them up badly enough that it made the news on at least one occasion.

synthtel2 wrote:

Gaming isn't exactly a mission-critical workload.

just brew it! wrote:

To this day I have no idea how they got the customer to agree to that.

synthtel2 wrote:

My own median Windows workload is to see or hear (from Linux) that friends are playing or about to play Planetside, reboot into Windows to join them, fire up the game, and hope that WU sees fit to stay out of the way because if it doesn't the game will be unplayable (10 Mbit) or barely playable (25 Mbit).

Captain Ned wrote:

As for W10 update policy, I approach it from two prongs.

Prong 1 affects maybe 5% at most (more likely far less than that) of the W10 population, namely us gerbils who have the skills to assess our own situations and schedule updates when we want, and don't like how W10 makes full control difficult.

Prong 2 is the 95-99% of clusers who are the ones whose unpatched computers form the botnet/spamnet brigades that make the modern 'Net such a pain at times

Would I as a "Prong 1" user wish more control? Without a doubt. That said I fully grok why MS forces W10 updates on the cluser population, fully support same, and can deal with the occasional confusion. It's the IT version of herd immunity vs. anti-vaxxers.

ludi wrote:

synthtel2 wrote:

My own median Windows workload is to see or hear (from Linux) that friends are playing or about to play Planetside, reboot into Windows to join them, fire up the game, and hope that WU sees fit to stay out of the way because if it doesn't the game will be unplayable (10 Mbit) or barely playable (25 Mbit).

Well, yeah, in general Windows 10 will try to keep updates out of the way of normal use, but if you only fire it up once in a while, there will usually be a backlog ready to download and the system will have no expectation of being available again any time soon. So away it goes. Unfortunately I don't see a way around that for your use case, since it sounds like you use it in a way where it would never (or rarely) get updated otherwise, i.e. exactly the problem Microsoft is trying to kill.

Captain Ned wrote:

Would I as a "Prong 1" user wish more control? Without a doubt.

Ifalna wrote:

Works like a charm on our school computers, I only update them once a year from USB stick, because Internet security isn't mission critical, since these devices never get to see any sensitive data, only kid learning programs.

derFunkenstein wrote:

Speaking of school computers, Windows 10 was the reason I bought a laptop for school work. It seemed like every time someone sat down at a computer in one particular lab, they'd get booted mid-class period for a restart. And since they were equipped with spinning rust, those updates took FOREVER, despite having decent quad-core i5 CPUs and 8GB of memory. They were otherwise spec'd fine.

just brew it! wrote:

derFunkenstein wrote:

Speaking of school computers, Windows 10 was the reason I bought a laptop for school work. It seemed like every time someone sat down at a computer in one particular lab, they'd get booted mid-class period for a restart. And since they were equipped with spinning rust, those updates took FOREVER, despite having decent quad-core i5 CPUs and 8GB of memory. They were otherwise spec'd fine.

What a dumb decision. Being lab systems, they probably did not even need a lot of local storage. I bet they could've used smaller SSDs for the same price, and avoided the performance hit.

just brew it! wrote:

Ifalna wrote:

Works like a charm on our school computers, I only update them once a year from USB stick, because Internet security isn't mission critical, since these devices never get to see any sensitive data, only kid learning programs.

Unless they are on their own subnet firewalled off from any systems used by teachers and staff, they could still act as an infection vector for other more sensitive systems.

Usacomp2k3 wrote:

Most of the school labs I've used are all "frozen" images that open an effective read-only partition every reboot that thaws the image. IT manages the image and pushes out any updates at whatever interval. The individual machines didn't even have the ability to do updates.

sweatshopking wrote:

https://imgur.com/a/mSB3lop

these are my download settings for windows update, courtesy of the new insider preview coming out in likely april. you've got more control over how updates are downloaded, and i think it's long overdue. Will it be enough to placate some of the rage? i doubt it. before we lose it over uploading updates, if you don't want to share because of your bandwidth caps just set your connection as metered (which you should do anyway if it's metered) and you won't upload.

synthtel2 wrote:

Updates that complete faster aren't the real solution, updates that don't interrupt other stuff in the first place are the real solution.

sc config wuauserv start= disabled

DancinJack wrote:

Y'all must be using some seriously crappy hardware. Which is understandable. Not like each of us can afford to upgrade every PC we touch. I have just never seen these kind of issues on any of the W10 machines I interact with on the regular. Even my dad's old Thinkpad, which is a dual core i5 from years ago with spinning rust handles updates just fine. :/

bthylafh wrote:

DancinJack wrote:

Y'all must be using some seriously crappy hardware. Which is understandable. Not like each of us can afford to upgrade every PC we touch. I have just never seen these kind of issues on any of the W10 machines I interact with on the regular. Even my dad's old Thinkpad, which is a dual core i5 from years ago with spinning rust handles updates just fine. :/

No! The user I spoke of has a newish laptop, I think a Latitude E5550 or thereabouts, probably a Core i3 and 8GB of RAM.

But we do have some crufty old crap around. Plenty of old early C2D-era stuff still, many with spinning rust. Budget cuts suck.