4 ms·
With no countermeasures, Windows 10 (2016-2022) will try to reboot at local night regardless of what you have running if it has downloaded and staged an update,
by CompuHacker 4y ago
With no countermeasures, Windows 10 (2016-2022) will try to reboot at local night regardless of what you have running if it has downloaded and staged an update, so long as it believes no one is around to stop it.
With partial countermeasures, like disabling the Windows Update service, several other services (Windows Update Medic (WaasMedic) and Update Orchestrator (usosvc)) and scheduled tasks will do a variety of things silently to make WU active again. It may try to update at strange times after making those repairs. Sometimes, it grabs new firmware for OEM laptops and installs that during the reboot. That's not comforting in the slightest.
If you delete all the associated scheduled tasks and manually disable all of those services, you can get a few months, maybe a year or five of uptime.
- Beached 4y agoI hate the use of the word counter measures. a better way to phrase this is "the default settings are to auto update, which can be disabled if the user wants to"
- londons_explore 4y agoIt's not a 'one toggle to turn it off' thing. They've gone to extra effort to make it hard to disable, to the point that you need to do many actions in the right sequence or all your work will be auto-reverted.
- rat9988 4y agoI wish it was that easy.
- mrguyorama 4y agoI run windows 10 pro. I am "forced" (because I make zero effort to stop it) one update/reboot cycle a month, unless there's literally a zero day, which they think is more urgent than rolling into patch Tuesday. A lot of the preferences of Windows 10 that people hate, (ads, extra telemetry, cortana etc) aren't even defaults, the system explicitly asks you when you install it. But if you only know Windows 10 from pre-installed prebuilt computers, manufacturers make those choices for you.
- baisq 4y agoWhy go through all those lengths when you can simply disable automatic updates in the policy editor? Then you can apply them whenever it's convenient to you.
- CompuHacker 4y agoThat's usually step one. Historically, the policy you're referring to is broken, or is not specifically for "that". [1] Updates are officially required. [2] Each release makes it more difficult to positively force WU to fail with user-facing tools. So now, in 2022, after 13 major releases with different UIs, waasmedic logic, and policy effects, when I need to keep a computer online, I don't consider the options that I've found to have failed before (where failure is equal to rebooting). I kill the components of WU, repairs to WU, and repairs to the tools that repair WU. As a result, or as a consequence, you decide, I usually don't get updates again for a long while. [1] https://social.technet.microsoft.com/Forums/windows/en-US/307294ef-9ddf-412e-9dd4-9b4345dd281c/windows-10-education-updates-cannot-be-disabled https://social.technet.microsoft.com/Forums/windows/en-US/30... [2] https://en.wikipedia.org/wiki/Windows_10#Updates_and_support https://en.wikipedia.org/wiki/Windows_10#Updates_and_support