I thought more recent OS had ways to update files currently in use and not require reboots.
Corporate policy of rebooting once a week and forcing it is killing me: I usually have tens of excel windows interlinked, and having to reboot daily just saps my will to live….
In: 68
They don’t *need* to — it’s just a place for bugs to live if you try to avoid it, and can make it harder to troubleshoot what caused issues.
Lets say you’ve been installing updates and not rebooting for the last two years. Then you reboot because reasons (power outage, whatever) and the system doesn’t boot up. Why didn’t it boot up? There are a LOT of options. If you rebooted after every patch cycle, then you know it’s caused by either a very recent hardware failure or something in the most recent patch because you know you had a working, bootable configuration after the last patch cycle.
Also, if you apply updates without rebooting, you may run into issues caused by some third party service not reloading after the patching when it should have. You aren’t capable of determining this, so you’ll likely waste a bunch of helpdesk peoples time trying to get it fixed when the answer is to reboot.
Also there may be security reasons with the recent trend in signed code.
Your solution is to automate your process of opening tens of interlinked excel windows so that reboots become trivial. A growing trend in computing is “cattle, not pets”. You should aim to not care whether this is “your computer” or some rando company laptop or virtual machine spun up on AWS 10 minutes ago. Separate *your* process from the actual hardware (and ideally, OS)
Latest Answers