Until Sequoia, it was simply downloaded and installed as any other software update. Since then it has changed frequently and its behaviour can now confuse.
SilentKnight
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.
Although primarily for compatibility with Tahoe, these include a general refresh and are recommended for all versions of macOS from Big Sur onwards.
There are no changes for Sonoma and earlier macOS, and Sequoia 15.0-15.1.1 will also continue working as before. But 15.2 and later work differently, as explained here.
Did you spot the change that didn’t take place as expected in the 15.2 update this week? It marks the end of the Intel era for Macs.
It’s easy to ensure that SilentKnight won’t inadvertently install an upgrade to Sequoia, but still updates the security data files you want. Here’s how.
You’ve just installed an update to XProtect in Sequoia, so why doesn’t it change the version number? How to fix this common problem.
If your Mac is running Sequoia, it could have no XProtect data at all, or being using version 5272 or 5273 but not 5274; if it’s running Sonoma or earlier, the version could be 5272 or 5274 but not 5273. Simple.
SilenKnight 2.11 addresses issues with Sequoia, and is strongly recommended if you’re going to update from Monday 16 September onwards.
The Eclectic Light Company 