Jump to content

jsahmri

Members
  • Posts

    4
  • Joined

  • Last visited

    Never

Posts posted by jsahmri

  1. I am having the same trouble after recently upgrading to Big Sur.  Apologies I can only reply in English.

    • macOS 11.4
    • Outlook 16.51
    • Kaspersky Endpoint Security for Mac 11.1.0.210a

    While Kaspersky is running, Outlook uses 100% CPU and a constant stream of the following messages appear in Console.

     

    When stopping Kaspersky by doing the following, utilisation drops back to normal levels.

    sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.kav.kavd.plist && sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.klnagent.plist && sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.sysextctrld.plist 

    Upon restarting Kaspersky, CPU utilisation hits 100% again after a few minutes.

    Uninstalling and reinstalling KES did not fix the problem.  Disabling protection in KES preferences did not fix the problem either.

  2. I am having the same issue after having just upgraded to Big Sur.

    • Kaspersky Endpoint Security 11.1.0.210a
    • Microsoft Outlook 16.51 (21071101)

    After KES has been running for a few minutes, Outlook starts using a constant 100% CPU (give or take a few percent).

    Opening up Console.app shows a continuous stream of the following messages:

     

    Process: Microsoft Outlook (libnetwork.dylib)

    nw_socket_handle_socket_event [C145.1:1] Socket received READ_CLOSE event

     

    When killing KES, the messages stop appearing in Console.app and Outlook CPU usage drops off entirely.  Upon starting KES and waiting a few minutes, Outlook CPU usage again hits 100%.

     

    Here’s how I'm killing KES

    sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.kav.kavd.plist && sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.klnagent.plist && sudo launchctl unload /Library/LaunchDaemons/com.kaspersky.sysextctrld.plist

    Unchecking ‘Enable Protection’ in KES Preferences does not fix the problem.  Uninstalling and reinstalling KES did not solve the problem.

    Apologies that I can only respond in English.

     

    Here is a screenshot of the console:

     

×
×
  • Create New...