Do you ever run XProtect Remediator manually? If so, the latest version doesn’t oblige. You might need to consider a 3rd party malware scanner.
XProCheck
To check XProtect Remediator scans, you really need log records lasting at least 24 hours. What can you do if your Mac’s only run for 6-8 hours? Here’s how to use Logistician to help, and how you can cheat.
Do you check XProtect Remediator scans using XProCheck on your laptop Mac? How often are its scans run there, daily or erratically?
Several utilities access the log. When there are problems getting entries, they each report details. Here’s what each error report means, and what you can do to fix it.
How to check secure boot, SIP, Gatekeeper/XProtect, its SSV, FileVault, macOS and its firmware, and XProtect Remediator scans.
Six years ago, the old MRT saved millions of Macs from coming under attack. XPR could one day do the same. A new deep dive into its function has just been presented at Black Hat. Also updates on status_code 30 and missed scans.
With macOS support for Intel Macs coming to an end with Tahoe, it’s time to reconsider the role of SilentKnight in the future. Plus two more updates.
How does XProtect Remediator scan your Mac once a day? What has gone wrong when it doesn’t appear to work? Explained from its property lists to its three different types of scan.
If you’re running any version of SilentKnight before 2.10, you need to update it now for compatibility with Catalina and later, particularly for Sequoia. And there are more essential updates too.
Improves performance by changing it log access to use the OSLog API, adds local time to its reports, and provides more space for long scanner names.
