winstonsmith84 3 Posted January 19, 2018 Share Posted January 19, 2018 Really hoping that there will eventually be a better way of informing users they need to restart the computer after an Eset update. Users consistently refuse to restart when they get the "Eset needs attention" message in the system tray. I'm forced to send the pop up window message task telling them to restart. This message scares them because they think any message that pops up on the screen is a virus and they refuse to reboot after seeing it. There has to be a better way to make people restart after an update. Ideally, not requiring a restart after an update would be wonderful. What exactly happens if people don't restart? Is Eset simply not working until they do? Or is it working but certain modules aren't? Or is it working fine but a restart is recommended? Link to comment Share on other sites More sharing options...
e3z 3 Posted January 19, 2018 Share Posted January 19, 2018 Hi winstonsmith84, Not sure how everyone else does it but; I schedule a reboot at night through the Remote Administrator console at Admin/Client Tasks/Operating System/Shutdown Computer. That seems to work here pretty well. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,259 Posted January 19, 2018 Administrators Share Posted January 19, 2018 Without a restart, old drivers remain loaded when a new program version is already running. This may cause unexpected behavior if the product is left in this state for a long time. Normally the product should withstand this state, however, issues are likely to occur if an upgrade from an older major version (e.g. v4) to a new one (e.g. v6) was performed. Link to comment Share on other sites More sharing options...
Recommended Posts