I've had several support tickets from the same department where employees refused to restart their computers after updates. One person said they had 47 browser tabs open and couldn't risk losing them, while another was proud of having 89 days of uptime. I've explained that security patches may not take effect until the machine restarts and that browser sessions can usually be restored, but they feel IT doesn't understand their workflow. Meanwhile, some of the same users are reporting slow performance and random freezes. Management doesn't want us enforcing reboot policies because they're worried about interrupting productivity, so security updates remain pending and everyone treats restarting like a major disruption. Is this a losing battle everywhere, or have you found a good way to get users to reboot when required?
4 Answers
Management buy-in is the real issue here. Explain that delayed reboots leave security updates incomplete and can increase the risk of vulnerabilities, compliance problems, ransomware, and unplanned downtime. Put the current uptime and patch status into a report, document that the risk was raised, and propose a controlled overnight reboot policy rather than arguing with individual employees.
The practical answer is to stop making this a user-by-user debate. Give people clear warnings and a reasonable postponement window, then schedule an automatic restart outside business hours. For example, allow several deferrals after patching and force the reboot when that window expires. Once it becomes normal and predictable, most users stop fighting it.
Make the policy and maintenance window explicit, then enforce it through your patch or device-management system. Workstations can reboot overnight or over the weekend, while laptops can receive repeated reminders before a final mandatory restart. Document the schedule so users have time to save work, but don’t leave security patches indefinitely optional.
For troubleshooting, I keep it simple: check the actual uptime, explain that a restart is the next required step, and don’t continue until it’s done. A shutdown may not count if fast startup or hibernation is enabled, so specifically ask for Restart. Modern browsers can usually restore a previous session, and important pages should be bookmarked or saved instead of kept open indefinitely.
That makes sense. I’ve been spending too much time persuading people instead of treating the restart as a normal prerequisite for support and patch compliance.
A generous delay period helps a lot. Users don’t necessarily need an immediate reboot, but they do need a firm deadline so the decision doesn’t get postponed forever.