Hi, after the update to 18.104.22.168 (we are entirely Windows based) I have around 10% of my machines (around 50 affected in total) where the Sophos File Scanner Service and Sophos System Protection Service are not starting and are marked as bad devices in Sophos Central. I can manually start them but this isn't a viable solution especially as there are different machine affected each day. There is no commonality in the machines affected except all are running Windows 10 Enterprise LTSC (1809).
We have a bunch of machines running Windows 10 Education 20H2 and 21H1 and have yet to see the problem on these.
Has anyone else seen this?
As we know Win10 1809 version was already on EOL last May 2021. I would suggest you upgrade those systems to their later version to avoid encountering issues not just for endpoint but for system patches as well.
Hi Glenn, Windows 10 1809 (LTSC) is supported until January 9, 2029.
Can you link the logs showing the failure?
For SFS:C:\ProgramData\Sophos\Sophos File Scanner\Logs\
SophosFS.log is for the service. The service spawn the Sophos File Scanner processes which log to SophosFileScanner.log.
As for SSP Service:
Any errors when they fail to start?