> Perhaps the answer is as simple as "there's a setting buried somewhere that all technically-literate Windows users change"
With all the editions and versions of Windows 10, there doesn't appear to be a single definitive answer to that.
I for one settled on https://github.com/marcosbozzani/Win10ActiveHours , which prevents reboots by scheduling a task to update Windows' own "Active Hours" twice a day.
My roommate in college refused the Windows update request enough times that it just took the decision out of his hands and _told_ him it was rebooting...in the middle of a LAN Starcraft game we were having. (Hilariously, Starcraft also ran perfectly on my Wine/Ubuntu and had all sort of weird bugs and visual artifacts on his Vista/7)
I truly can't imagine how anyone can consider a system that reboots without your consent, no matter whether you're playing Starcraft or giving a presentation or launching nuclear warheads, to be appropriate for serious work. It seems like one of the very basic jobs of an OS to _not turn off while you might be doing something important_. Perhaps the answer is as simple as "there's a setting buried somewhere that all technically-literate Windows users change", but the default behavior is beyond insane.