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

Network Threat Protection not running

Last week we suddenly had 30+ systems start reporting "Policy non-compliance: Network Threat Protection". When I check the status of one of these devices it shows "Not started: Sophos Network Threat Protection". So far, I've only found one post that gives two possible options on how to resolve this and neither of them have worked for me. The first was that the MS Visual C++ redistributable wasn't installed or broken so reinstall that, the second option was that the BFE (Base Filtering Engine) service wasn't running so make sure that's started.

Also, many systems seem to just resolved them selves somehow.

So, has anyone else managed to figure out how these resolved systems are resolving themselves, or a way to resolve this without completely reinstalling the endpoint software?


Thank you.



This thread was automatically locked due to age.
Parents Reply
  • Yes, these did all freak out after the update. And many did resolve themselves but a lot didn't. My own desktop and laptop have been rebooted and such a few times and still aren't running right so I couldn't figure out what was causing some to resolve themselves. From what this article describes it's exactly what is happening. And it appears I just need to wait for Sophos to be in the mood to fix itself.

     

    Thanks!

Children
  • If you change under:
    HKEY_LOCAL_MACHINE\SOFTWARE\[WOW6432Node]\Sophos\AutoUpdate\

    PlatformRelease

    to a different version than the current OS version then it will similulate the OS upgrade.  For example, if they updated to 1809, maybe set them to 1808.  It only cares about the string being different but the next update will run all the setup plugins and fix MTD.

    Tamper Protection would need to be disabled to change that value.

    Regards,

    Jak