Sounds like your IT doesn’t know how to properly orchestrate updates.
Best way to do it in a Windows enterprise environment that I’ve seen so far:
1 Week: Install in the background silently and finish when the machine reboots.
After the week, 2 Days: Warn once that the machine will automatically reboot in 48 hours.
12 hours before forced reboot: Pop up a warning in the corner with the countdown before reboot. Options are reboot now or warn me again in X hours. If you dismiss it without selecting, it pops up again in an hour.
If your Windows machine hasn’t rebooted in a week and a half, of course you’re going to have performance issues. What, you expect devs to avoid memory leaks?
That all said, the amount of Windows sysadmins who haven’t entirely given up on wrestling Microsoft’s update bullshittery is shrinking every day.
It is about reasonable defaults. Why would anyone want to stop their presentation for Windows update reboot? It should be much more friendly how it handles this. Like always check what the user is doing and when is a reasonable time to do it? Maybe at the end of the day.
Personally, I think they need to work on the whole concept. Make it as transparent as possible or less likely need a full reboot - containers or put more things in like wsl? Make the reboot only do reboot and not 20min installing updates… The user cant even chat on teams or browse the web while waiting. Think if it worked like like live cd that Linux can do.
Microsoft claimed ages ago when they made updates effectively mandatory (you can turn them off entirely or delay them by 27 day chunks forever on non-enterprise installs) that they would dynamically detect the times your computer wasn’t actively being used and try to target that, but it never really made a difference besides “aim for when the computer is likely powered off anyway”.
And that still doesn’t hit the basic “is the user presenting in PowerPoint, running a full screen video/program?” sort of common freaking sense stuff you’re talking about.
In some nicer news, Microsoft finally started trying to release some updates as “live updates” that don’t require a reboot late last year. So maybe in a decade they’ll get close to the Linux update experience.
Sounds like your IT doesn’t know how to properly orchestrate updates.
Best way to do it in a Windows enterprise environment that I’ve seen so far:
If your Windows machine hasn’t rebooted in a week and a half, of course you’re going to have performance issues. What, you expect devs to avoid memory leaks?
That all said, the amount of Windows sysadmins who haven’t entirely given up on wrestling Microsoft’s update bullshittery is shrinking every day.
It is about reasonable defaults. Why would anyone want to stop their presentation for Windows update reboot? It should be much more friendly how it handles this. Like always check what the user is doing and when is a reasonable time to do it? Maybe at the end of the day.
Personally, I think they need to work on the whole concept. Make it as transparent as possible or less likely need a full reboot - containers or put more things in like wsl? Make the reboot only do reboot and not 20min installing updates… The user cant even chat on teams or browse the web while waiting. Think if it worked like like live cd that Linux can do.
Oh 100%.
Microsoft claimed ages ago when they made updates effectively mandatory (you can turn them off entirely or delay them by 27 day chunks forever on non-enterprise installs) that they would dynamically detect the times your computer wasn’t actively being used and try to target that, but it never really made a difference besides “aim for when the computer is likely powered off anyway”.
And that still doesn’t hit the basic “is the user presenting in PowerPoint, running a full screen video/program?” sort of common freaking sense stuff you’re talking about.
In some nicer news, Microsoft finally started trying to release some updates as “live updates” that don’t require a reboot late last year. So maybe in a decade they’ll get close to the Linux update experience.