Sophos services stopping randomly is nothing new but its still worries me when it happens on a service.
Not sure what Sophos Device Control Service does or what its dependencies are but trying to start it doesn't work are rebooting the server doesn't' fix it either.
Sophos services stopping randomly is nothing new perhaps nothing new to you but definitely not normal, this isn't some flaky rough-and-ready software.
There should be associated entries in the Windows Event logs when a service stops/crashes or fails to start. Debug logging might provide more information. But perhaps you should open a case with Support.
Run Process Monitor and capture a trace of the service being started. The additional logging and PML log should help if you wish to link them here or send them to Support.
Thanks for the responses. The service eventually started on its own accord after about 4 hours. Lookingat the logs it appears that it stopped during a Sophos update. Not sure why it took so long to restart.
It's certainly working again but the problem's not necessarily "solved". Maybe Sophos just over reports. Its understandable that and update may require a service to restart but to flag it as failed service and then require two restarts to fix it, and a 4 hours wait, doesn't feel right to me.
I am fairly new to Sophos, I have had a few user machines whereby the real-time protection gets disabled. Upon investigation I found that the Sophos Device Control Service isn't running. A restart of the machine in questions fixes this, but I wanted to find out if there's any manner in which I can set the service to automatically start? It is currently set to manual and options to change it are greyedout.
Quote