Hi - we have some updates for your machine ...
 

Had to replace a monitor, so figured I'd allow Win10 to get updates - I don't boot it too often.
6 hours or so later and after a bunch of reboots, I get the above message, followed by "this may take a few minutes".

You have go to be f'ing kidding me ...
What a bunch of crap.
</rant>

Yes, that happens when one doesn't "keep up" with Windows Updates. There seem to be weekly pushes. I keep saying I need to turn on my wife's 'puter and let it cook before (if) she actually needs to use it.

For all their resources ($ and people), Microsoft has yet to figure out how to chain updates together. It baffles me that every other OS I have used can do updates, require a single bounce, then run along fine. Windows 10 requires (in my corporate env anyway) multiple patch sets and bounces.

That's what you get for booting Windows syg00 :tisk:

It reminds me of when I still had XP - I don't miss it.

But Linux on the other hand... haven't had to reboot even once...

It's why in my place of work we just create images of drives... the alternative is a sadistic waste of time and bandwidth when setting up a new machine out of the box.

As a worst case example, I've seen Windows 7 boxes left updating over night and still not finished the following morning...

It boggles the mind as to what exactly is being done during that time. But I remember reading that many updates are cumulative, so in some cases it's essentially downloading the same thing thing over and over again. Beyond that I don't know/care, there are various ways around it for Windows sysadmins, but average Joe has to deal with the aforementioned tortuous process.

Yep, it's a terrible process. Ours always complete at work but I have to bounce my laptop 2 or 3 times in succession, which is ridiculous. This is why I have zero respect for Microsoft or their horrible products, despite that "everyone uses it, it must be good", which I hear time and time again.

IKR I've dabbled with Window$ 10 only because my laptop came with it of course it was replaced with Slackware. the Updates never finished because I canceled it, no update should take 1+ hours. I have done a full system update of a fresh install of Slackware 14.2 in less than a hour, and only had to reboot because of the new Linux Kernel.

Maybe you should rephrase that, you are free to reboot at your leisure. In Debian, APT used to say "reboot when convenient" after a kernel update. Same kind of thing. As far as I understand it, W10 tells you it is going to reboot and there's nothing you can do about it.

Exactly - I have been forced rebooted because of updates on my home laptop. My work laptop warns me but home one did not. Regardless, having to bounce multiple times in succession drives me nuts and is completely uncalled for.

Apparently the next "big" version of windows will have seamless background updates that won't require reboots.
But they always find ways to mess up things anyway so i'm not holding my breath

Read: users will have even less knowledge on what the hell their computers are doing.

Ha! Agree - like Apple, they like stupid users and try to hide every detail possible from them. In doing so, they have created this massively complex monster that is very difficult to manage and to use, for me anyway.

Pretty much an own goal then :)

I always reboot after a kernel update, because I read that it was recommended... Don't remember where it's been years back when I was starting to use Linux, always figured better safe than sorry.

Oh such a wonderful gift to mankind...
lol kidding but doing that they could do anything they want and the sheep would not know of anything good or bad from these "updates" remember the update that deletes peoples files :)