Want to stay running Sequoia or earlier? Want to install security updates such as XProtect data as well? Here’s how to do that without risking being upgraded unintentionally.
Software Update
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.
Originally two separate services in Mac OS X Server, for Software Updates and later Content, it reached client versions of macOS in High Sierra in 2017.
Users should be given a third option to defer updating further, as well as doing it now or later tonight. Does the DAS scheduling and dispatch system rely on security through obscurity too?
I had left my Mac running near midnight. Next morning it had shut down in the middle of an unwanted macOS update. Here’s how macOS went against my express settings.
iCloud is now used for key services including notarization checks. For XProtect updates, it should be quicker and simpler, so long as you mind the pinniped.
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.
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.
Does XProtect confuse you in Sequoia? Do you know why it could show as version 0, 5273 or 5274? Here’s a guide to what I think is going on.
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.
The Eclectic Light Company 