Skip to content

After a macOS update

Notifications during a macOS update, checks afterwards, and how macOS updates differ from Outbound app updates.

Outbound 1.3.0 · Updated

Outbound can notify you about blocked connections while it detects a macOS installer running.

When macOS is installing an update, connections that Outbound blocks can fail in ways that look like the update’s fault. Outbound knows an install is running, and while it does, a connection denied because its request could not be answered can post a notification, under the “Connections blocked during a macOS update” switch in Notifications. The preference key behind it, for outboundctl, is notify-os-update. Denials from a rule or your own answer do not trigger this notification.

The detection is deliberately careful: the update checker and cleanup services that run on an idle Mac are not an install. Only a process from the software-update installer framework counts, and the answer is cached for 30 seconds.

Automatic rule snapshots track changes to the Outbound app build number, not changes to the macOS version. A macOS update alone does not trigger that snapshot mechanism. See Updating Outbound for the snapshot triggers and restore path.

The compatibility page’s advice, worth repeating here:

  1. Back up your Mac and export your firewall rules (Settings › General › Backup, or outboundctl backup).
  2. Read the firewall vendor’s release notes for the exact macOS build.
  3. Keep the recovery steps somewhere you can read them offline.
  4. If a filter prevents connectivity, turn it off under System Settings › Network › Filters (Network › VPN & Filters on macOS 27 and later), or ask your MDM administrator.

Outbound 1.4.2 runs on macOS 14 Sonoma or later. On a macOS release newer than 27.2, Outbound warns you and asks you to update it before you rely on filtering. The compatibility page lists what changes on each version.