[TeMPOraL]

> Forced reboots for updates even if the computer is in the middle of a long-running task

Oh God don't get me started. Few days ago I was in the middle of a videoconference with some important people, when suddenly my screen went blue, flashed a Windows spinner and the word "Restarting", and boom. It just rebooted. With no warning, despite me being on a videocall, on Microsoft Teams of all things! And within the "active hours". How this behavior is acceptable is beyond me.

[p_l]

I'd recommend checking if you don't have third-party code forcing that restart - for a pretty long time now, Windows 10 has a policy that it does not restart for updates unless it can't detect user activity for a longer time, and even then it defaults to updating at night.

Corporate-forced updates, however...

[Grimm665]

I came pretty close to playfully trying to have Microsoft cover a portion of my monthly electric bill.

Why? Because I set my dual-GPU gaming rig to sleep every night, and Windows feels the need to wake it up about an hour later, fail to do updates, and then leave the machine on the rest of the night, even with auto-sleep set for 30 minutes.

I noticed the problem a few weeks later, and by then my electricity bill had increased by 20 bucks.

[xeromal]

That happened to me a few days ago. It was at like 5pm when my hours were set to 10pm. It didn't even give a countdown. It just restarted in an instant. I so annoyed as I was installing a game at the time and it completely corrupted the installation.

[ksk]

I agree, they should add some kind of option to disable updates for pro users even if they warn you. For me, W10 has always given me an option to defer updates and let me pick a time. At work, we use WSUS to manage our machines and my W10 box regularly gets months of up-time. Crazily enough, we even have a W10 laptop (!) that does some critical stuff with a year and half of up-time. https://i.imgur.com/uRGmhTU.png