A practical guide to Software Update, automatic installs, and checking your current build without confusing a security patch with a major upgrade.

Start with the version you run

Open Apple menu → About This Mac and note both the macOS version and the build. Then open System Settings → General → Software Update. Software Update presents updates compatible with that Mac, but read the name of the offered release before selecting it. A numbered point update and a full major upgrade have different consequences for application compatibility.

Choose the automatic update controls deliberately

In Software Update, open the Automatic Updates information control. Apple separates checks, downloads, installation of macOS updates, App Store updates, and security responses or system files. If the Mac is used for critical work, automatic download and installation can be configured independently; make a backup and plan a restart window. On a managed Mac, your organization may determine timing and which controls are available.

A safe sequence for macOS 27

First check that a recent backup actually completed. Connect a MacBook to power, save open work, and leave room for the update to prepare. Run Software Update, verify the version, and let the Mac restart. Afterward confirm the new build in About This Mac and test the few tools you depend on: VPN, audio interface, printer, external display, and any extensions. If a component fails, update its vendor software before changing system security settings.

When no update appears

A blank update screen does not prove that every Mac has the same latest release. Availability depends on hardware, installed version, and administrative policy. Check the connection, restart once, and compare with Apple’s current release information. If the Mac is managed, ask the admin before trying standalone installers. Do not download a “security patch” from an ad or a random mirror.

What to record for troubleshooting

Write down the installed build, the name of the offered update, available disk space, and the exact error text. Those four facts are more useful than a screenshot of the progress bar. If the update fails repeatedly, use Apple’s Recovery guidance and preserve data before considering erasing a disk.

How to distinguish update types

An Apple update inside macOS 27 keeps you in that major version; an upgrade changes the major version and can change app support. Security fixes may also arrive on an earlier supported branch. Compare the number shown in About This Mac with the title in Software Update. The installed build is a reliable way to tell whether a restart actually applied an update. If the update prompt vanishes without a restart, check again rather than assuming success.

A small post-update acceptance test

Open a document from local storage and one from your cloud provider. Try the VPN or work login you rely on, then reconnect your primary external display and peripherals. For a developer Mac, run the usual build or test for one important project. Record only concrete failures and versions; broad claims that “macOS broke everything” make diagnosis slower. Keep the last successful Time Machine backup until you know your normal workflow still runs.

If you are staying on an older version

Staying on an older release can be a sound temporary compatibility choice, but do not ignore updates offered within that branch. Apple’s security releases page shows which versions received a fix. Set a review date for the apps blocking your upgrade. When the vendor publishes a compatible version, test it and re-evaluate the major upgrade. This is especially important for machines that no longer receive the same security coverage.

Before you change system settings

Make a backup, note what you changed, and follow your organization’s policy on managed Macs.

Apple documentation