Immediately after an autoupdate installed 10.0.3, SophosScanD is now no longer able to run. When I run the diagnostic tool, it says the System Extensions "Sophos Can Extension" and "Sophos Network Extension" aren't met, but under privacy settings all Sophos services and extensions are checked.
Thanks for the info, it looks like the upgrade was performed successfully but macOS is requiring an acknowledgement from the user in order to run the updated Scan Extension.
Is there a notification…
Confirming the findings of others with SophosScanD not running:
Just got my first device enrolled in the EAP today and updated Sophos Endpoint on it.
Pushing separate configuration profiles via Jamf, one with the Privacy Preferences set per our Catalina installs, and one with the system extensions per the Big Sur kbase article with the two extensions added.
Sophos window opens from the menu bar but displays a message that some Sophos services are not running, and opening Endpoint itself confirms that SophosScanD is not running.
Running systemextensionsctl list gives the same output that Sam shared.
Hi Beth,For Big Sur, there should be the usual Full Disk Access in Privacy, but in initial Security and Privacy Tab, bottom right corner, click Advanced, did you find two extensions there to click to allow as well?
Hi, clicking on advance it askes to mark 2 things like lock screen and so on ,nothing about ext
Hi Robert, after marking those 2 boxes, ScanD is still not working?
My users found that the 2 items that need to be allowed were under General, Advanced once you unlock with your credentials...and there is a prompt at the bottom of the screen saying "Some system software requires your attention before it can be used". You then click Details button and will find SophosWebNetworkExtension and SophosScanD both of which need to be selected. Also not the comment above that says the system needs to be restarted before it can be used. For my users once they have selected the 2 options and restarted SophosScanD is shown as working. Hope this helps.
Just did this on one of my users using BigSur 11.2.3 and this fixed the problem of ScanD not working - thanks Andrew
Glad it helped !