Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos 2.5.2 Interfering with SCCM/Software Center 1906

I've been working in an environment that rolled out Sophos Central. At the time of deployment, the Sophos Central client was 2.4.2. 

In the last few weeks, we've been experiencing problems with applications/packages failing to download via Software Center. The error that comes back from SCCM is usually 80004005 (generic, useless), and occasionally we get in our SCCM CAS.log on the endpoint --> "CheckExclusiveFileAccessAndSetFilePermissions failed" 80070020 and references to "Failed to do hash verification with preference : 4, Try to verify at next hash algorithm" 80091007.

Experience as SCCM consultants suggest this is most likely caused by AV On Demand scanning of the Source Repsitory.

Also, Software Center (SCCM's "App Store") now delays opening with a white screen and occasionally, after some time -- 10 minutes? It will open up, but not always. This feels like something is blocking the engine behind Software Center.

However, with all policies off and Tamper disabled in Sophos, the issue still occurs.

Removing Sophos 2.5.2 from the machine fixes all the issues described above.

 

I have previous experience with Sophos Intercept-X causing problems with Hyper-V back in the Win10 1709 days. The issue I'm experiencing here feels somewhat similar, in that no error logs are recorded in Sophos.

 

The team I am working with have reached out to their Sophos account manager and have been issued with a "Hitman Pro BETA Fix" (again, similar to the what happened when I faced Hyper-V issues in 1709) -- but I'm not sure this has helped.

Has anyone else noticed this?



This thread was automatically locked due to age.
Parents Reply Children
  • According to the Sophos engineers who looked into this escalated issue, the problem lies with Sophos AMSI Protection, which in general, breaks a lot of things. Apparently Sophos AMSI interacts/integrates with Microsofts AntiMalware API, but the early access implementation has a few issues.

     

    The suggestion was to disable Sophos AMSI using the info found in https://community.sophos.com/kb/en-us/134719

  • Hi  

    Thank you for sharing this information here.

    It'll be beneficial to other customers as well. AMSI is still in EAP, so there might be clash issues with AMSI currently.

    Regards,

    Jasmin
    Community Support Engineer | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

  • Hi Vini,

    The Sophos AMSI feature has been in our Early Access Program (EAP) since October and has had excellent feedback. We have had a very small number of reports of conflicts that the team have been addressing as the EAP runs. This is exactly the purpose of the program, and we are very happy that we have customers who participate and provide vital feedback before we launch the products for all customers.

    The team are investigating the ticket that was raised as a result of your support call, i will provide an update to this thread once I have one.

    Regards,

    Stephen