Hi, after the update to 2.20.4.1 (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?
Thanks,
Andrew
This thread was automatically locked due to age.