Windows Update on 10
Is still as bad as it was from the start.
You can get it to not force a reboot during your standard "working" hours, sure, but you can't dictate when it downloads the updates.
Right when I'm in the middle of playing online games is NOT the right time to take over my bandwidth.
It shouldn't be hard - if there is constant use of the CPU, GPU or HDD, coupled with network activity - the user is probably doing something that requires those resources in use, and doesn't want their OS to hold their network and disk access to ransom until they are done.
Why it can't just notify that there is an update ready to be downloaded and let me download it when ready... I don't know. It was an option in Windows 7.
But even that would kill performance in Windows 7 - I never got to the bottom of that, but when there was an update ready for download, everything slowed down until installed.
There is also no way to <br>
a) shutdown the PC leaving the update pending - it now forces the update installation, even using the command line. - Fantastic when you need to shutdown the PC quickly for whatever reason.<br>
b) fully install the updates (including any restarts needed) - so you tell it to install updates and shutdown when finished using it, and then when you need to hop on quickly the next morning, it has to go through the post-restart update process which takes its time. <br>
slow shutdown or slow boot after updates. PICK ONE MS! or better yet, let us pick.
Or, you know, go the *nix route and be able to update practically everything in place.