Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 14242 views
  • Users 0 members are here
Options
Suggested
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 SysTray Icon saying Sophos is deactivated when in fact it's not

baedamichi

Hi,

just a minor issue, which is just cosmetic I guess...

On my computer (standalone installation of version 10.3.12.89 which I get from my school who pays for the corporate license), Windows 8.1 Pro, the SysTray Icon often (not always) keeps telling me that Sophos is deactivated (see attached screenshot), when in fact it is not (settings of on-acces scan is "on", Windows Security Center reports that Sophos is active, Sophos itself on entering the "main screen" of the program tells me it's active, and I get the appropriate alerts when accessing files or websites Sophos considers to be malicious).

This only happens on my Windows 8.1 machine (x64), other machines running various kinds of Windows 7 (Home, Pro, Ultimate, both x32 and x64) do not have this issue.

Any clues?

Thanks a bunch for reading my lines. :)

:55228


This thread was automatically locked due to age.
Parents
  • 0

    Yeah almon.exe is launched from the "run" registry key so it starts in the context of the logged on users.  

    If you have multiple users on a computer logged in concurrently then you would have multile almon.exe processes.

    Have you tried logging in as a different user account to see if it's a profile problem?  I don't see this being the case but maybe worth a go.

    So if you restart almon.exe (kill/launch) it's fine.  What happens to "break it"?  Does a restart of the sophos services cause it to revert, if so which ones?

    • Sophos Anti-Virus Service
    • Sophos Autoupdate Service

    Both of the above play a part in this status.

    Could also run Process Explorer (Sysinternals) and check that the same list of modules are loaded when it works an when it fails.

    It's an odd one for sure.  I have a WIn 8.1 client and it's fine.

    Regards,

    Jak

    :55250
Reply
  • 0

    Yeah almon.exe is launched from the "run" registry key so it starts in the context of the logged on users.  

    If you have multiple users on a computer logged in concurrently then you would have multile almon.exe processes.

    Have you tried logging in as a different user account to see if it's a profile problem?  I don't see this being the case but maybe worth a go.

    So if you restart almon.exe (kill/launch) it's fine.  What happens to "break it"?  Does a restart of the sophos services cause it to revert, if so which ones?

    • Sophos Anti-Virus Service
    • Sophos Autoupdate Service

    Both of the above play a part in this status.

    Could also run Process Explorer (Sysinternals) and check that the same list of modules are loaded when it works an when it fails.

    It's an odd one for sure.  I have a WIn 8.1 client and it's fine.

    Regards,

    Jak

    :55250
Children
No Data