![]() And getting High Sierra compatibility into place is a far higher priority. However, most people haven't even noticed this problem, much less any issues caused by it. Warning: Malwarebytes GUI will become inoperable because of the reliance upon this background service persisting in memory. Issue the commands 'sudo launchctl disable system/Library/LaunchDaemons/.ist'" Step two has a missing reference in the command. Check running processes to determine if 'RTProtectionDaemon' process is active ![]() Issue the commands 'sudo launchctl unload /Library/LaunchDaemons/.ist'Ĥ. ![]() Issue the commands 'sudo launchctl disable /Library/LaunchDaemons/.ist'ģ. To reverse the operation then issue the commands in steps 2 & 3 by replacing 'disable' and 'unload' with 'enable' and 'load' respectively.Ģ. This will be persistent after reboots/shutdowns and updates to the program. You can disable the daemon from launching and residing in memory, even after reboots, by using 'launchctl' in terminal.Ĭaution: This will render the Real-Time Protection service component of Malwarebytes inoperable. I would suggest that you can disable Real-Time Protection and kill the running RTProtectionDaemon process. It's apparent that lack of proper testing was conducted on the program before the initial release because of it existing on multiple OS versions and hardware platforms. It's not very impressive that a company allows a known bug which cripples the one feature of their program and is the foundation of their subscription model to exist this length of time with no intentions of repairing it for at least another month. It's great software that is now as terrible as the dreaded MacKeeper as bloatware. I'm uninstalling it and removing it from my collection of software for my users until this is fixed. RTProtectionDaemon consumed 50% of my physical RAM and rendered my iMac intolerably slow.
0 Comments
Leave a Reply. |