Not what you are looking for? Ask the experts!
Symquald maxing out cpu problem resurfaces on macOS 10.13.6
This bug in Norton for Mac has appeared, disappeared and now reappeared. The symptom is that symquald will consume all available cpu for hours and hours. The only solution that the community has found is the one posted by Jerb back on an earlier version of Norton Security for Mac (see link below). I had to implement this hack again with Norton Security for Mac version 7.10 which recently installed itself. I am pretty frustrated with Norton for not acknowledging this as a bug and fixing it properly.
Note that Jerb's solution is slightly out of date in that the correct folder to open up to rename symquald so that it doesn't run is:
<your boot drive>/˜Library/Application Support/Symantec/Silo/NFM/Symqual/Symquald
I'm curious as to how many others are having this problem running on older MacBook Pros with macOS 10.13.6 and Norton Security for Mac 7.10