3 year old threat reported with v9.5.8.209 and then crash

  • 30 June 2023
  • 3 replies



Has anyone seen something like this? Looks like a bug with the latest version on MacOS to me.
My Webroot reported what appears to be an old threat this morning (Dwell time1870 days+) on my Macbook for a file that no longer exists. I tried to open Webroot Secure Anywhere on my Mac (agent v9.5.8.209) , but it was not responding, though Activity Monitor showed it was running.
One of my clients has a similar issue, a very old threat (Dwell time 1078 Days+) endpoint (agent v9.5.8.209) has been offline/unavailable from early this morning.

I have uninstalled Webroot Secure Anywhere, restarted and reinstalled from a newly download copy. Now I get this segmentation fault from the Webroot process on my Macbook.


Translated Report (Full Report Below)

Process: Webroot SecureAnywhere [4737]
Path: /Users/USER/Downloads/Webroot SecureAnywhere
Identifier: com.webroot.Webroot-SecureAnywhere
Version: 9.5.8 (209)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-06-30 20:09:22.4738 +0930
OS Version: macOS 12.6.7 (21G651)
Report Version: 12
Anonymous UUID: 153AECB0-09BB-7E9C-00F8-ADE91A3256FC

Time Awake Since Boot: 4800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [4737]


Best answer by TripleHelix 30 June 2023, 16:30

View original

3 replies

Userlevel 7
Badge +63

Hello @MalcolmSinOz 


I’m not a Mac person but maybe it’s best to contact Webroot Support directly for help. Also hopefully some other Mac users will make a reply but support is the best route from here for now.


Webroot Support:

Submit a ticket 24/7/365

Call 1-866-612-4227  during the week Mon - Fri 7 AM to 5:30 PM (MDT)

Note: When submitting a Support Ticket, Please wait for a response from Support. Putting in another Support Ticket on this problem before Support responses will put your first Support Ticket at the end of the queue.


Please let us know the outcome!





Yes, I should have said I had already raised a case with support, sorry.

I wanted to know if this sort of thing had happened before with a version release, or is symptomatic of something else.




Userlevel 7
Badge +63

Not on the Community but support would know if they had any others!