softwareupdated, the daemon that decides when your Mac updates itself
softwareupdated checks, downloads and stages macOS updates before installd installs them. Measured live: the six-hour clock, the ledger, the staged 509 MB.
By Chethan Kumar S N · Updated
People arrive at this page holding one of three mysteries. The first is Activity Monitor showing not one but two processes named softwareupdated, both owned by a user called _softwareupdate that appears nowhere else. The second is the one-letter trap: advice forums say run softwareupdate, Activity Monitor says softwareupdated, and nobody explains that these are two different things. The third is the strangest: a Mac that downloaded an update weeks ago, politely, over good Wi-Fi, and has since done absolutely nothing with it.
All three have answers in the daemon’s own files, and this page reads them the way the rest of this series does: read only, on a MacBook Pro on macOS 27.0.1, nothing installed and no setting changed.
The receipts
ps finds two processes with the same name and one family around them:
_softwareupdate 98700 RSS 6752K up 2d18h CPU 0:27.38
/System/Library/CoreServices/Software Update.app/Contents/Resources/softwareupdated
_softwareupdate 57572 RSS 3696K up 10h47m CPU 0:00.21
/System/Library/PrivateFrameworks/MobileSoftwareUpdate.framework/Support/softwareupdated
root 603 suhelperd, up since 20 October
chethankumar 46689 SoftwareUpdateNotificationManager, up since Monday
Both daemons have launchd as their parent, both run as _softwareupdate, a dedicated service account that exists so the update machinery never runs as you and never needs root. Both are Apple platform code: the main binary’s code signature reads Identifier=com.apple.softwareupdated, Platform identifier=26.
The sizes are the first surprise. The main daemon, the one your updates actually flow through, is 175,504 bytes, a fifth of a megabyte. The mobile twin is 6,138,768 bytes, 35 times larger, and it carries three architectures, x86_64 alongside the two arm64e slices, while the main one carries only arm64e. The small one is the orchestrator. The big one is the machinery, inherited from the MobileSoftwareUpdate framework that updates iPhones and older Intel Macs, and its size is the family resemblance showing through.
One line of manual, times three
The manual section of this Mac holds four pages for this family, and the shortest three fit in a pocket:
softwareupdated.8, dated January 2017, 327 bytes: softwareupdated is the main daemon responsible for running software updates. The see-also line names the two relatives, softwareupdate(8) and suhelperd(8), which is more navigation than most daemons get.
SoftwareUpdateNotificationManager.8, dated April 2018: a system daemon that manages displaying notifications related to macOS software updates.
remotesoftwareupdated.8, dated September 2024: a daemon that facilities paired devices to perform a remote software update over the network. That verb, facilities, is Apple’s own prose in their own manual page. The fourth page, softwareupdate.8 at 4,975 bytes, is the only long one, because it documents the command, not the daemon.
The clock, and the doors
The launch job file, com.apple.softwareupdated.plist, contains no RunAtLoad key. The daemon does not start because the Mac started. It starts because the clock or a knock says so, and the schedule is written out in plain sight:
One repeating activity, com.apple.SoftwareUpdate.Activity, every 21,600 seconds. That is the six-hour catalog check, and its gates are the story: Maintenance priority, Power Nap allowed, network connectivity required. Your Mac checks for updates while it sleeps, if you let it.
Two notification triggers from the system’s message bus: CheckForCatalogChange, fired when the catalog changes, and ManualBackgroundTrigger, fired when something in the system asks for a check outside the schedule. When you open Software Update in System Settings and it spins for a moment, this is the door being knocked on.
And in the running job’s event list, two triggers that only exist because an update is pending: SUOSUScheduler.tonight.install and its cancellation twin. The install trigger’s descriptor is the most honest sentence in the whole file. It lists AllowBattery and MayRebootDevice, both true. The daemon that downloaded your update politely over the weekend is also the process holding permission to reboot the machine at night.
The daemon listens on three message services: its own name, an OSUpdate variant, and one called com.apple.sumaccontroller. Apps never knock on any of them directly. System Settings, the softwareupdate command and the notification manager are the real clients, and the daemon’s log keeps a visitors’ book, which comes up later.
The ledger
Most daemons in this series keep state in SQLite files you cannot read. This one keeps its history in a preferences file you can:
$ defaults read /Library/Preferences/com.apple.SoftwareUpdate
FirstOfferDateDictionary = {
"MSU_UPDATE_26A434_patch_27.0.1_minor" = "2026-09-29 01:58:22 +0000";
"MSU_UPDATE_26B123_patch_27.2_minor" = "2026-10-27 04:28:07 +0000";
"MSU_UPDATE_26B131_patch_27.2.1_minor" = "2026-11-10 05:05:40 +0000";
};
DoItLaterTonightAttemptsCount = { 26A434 = 2; };
InstallDateDictionary = { 26A434 = "2026-10-20 07:22:00 +0000"; };
Every update this Mac has ever been offered has a date and time in that dictionary: 27.0.1 offered at 01:58 on 29 September, 27.2 offered at 04:28 on 27 October, 27.2.1 at 05:05 on 10 November. The offers arrive overnight UTC because that is when the six-hour clock and a sleeping Mac overlap. The install dictionary records when the machine actually moved, 20 October for the current build, and it agrees to the minute with the user-facing receipt, softwareupdate --history, which lists macOS 27.0.1 installed at 20/10/2026 12:52 local time.
The best key is DoItLaterTonightAttemptsCount. That is the daemon counting, in public, the number of times the person at the keyboard chose install tonight and then kept using the Mac past the window. This Mac’s count stands at 2 for the current build. No forum post will tell you that your Mac keeps score of your deferrals. The preferences file does, without caring who reads it.
The staged half gigabyte
The mystery of the downloaded-but-not-installed update has a physical answer. /Library/Updates currently holds 509 MB:
$ du -sh /Library/Updates
509M /Library/Updates
$ ls /Library/Updates/142-50405
142-50405.English.dist 31 KB
CLTools_Executables.pkg 351,228,115 bytes
CLTools_SwiftBackDeploy.pkg 49,095,077 bytes
CLTools_macOSLMOS_SDK.pkg 61,624,678 bytes
...
A Command Line Tools update, staged on 31 October, seventeen days ago at the time of writing, verified and waiting. Beside the folder sits ProductMetadata.plist, 107,924 bytes, and its modification date is yesterday afternoon. Nothing installed yesterday. The daemon had simply come by, on its six-hour clock, and checked that the staged packages still matched the catalog. It does this constantly. The folder is why the System Data section of your storage bar is bigger than it looks, a connection the System Data page measures elsewhere in this series.
Downloading and installing are separate permissions, set separately in Software Update settings. This Mac allows the first, so updates arrive on their own. It does not allow unattended macOS installs, so they wait, half a gigabyte at a time, for a night when someone taps Install.
What the family actually does
The update is a relay, and each runner owns one leg.
softwareupdated decides, downloads, stages and schedules. It compares the catalog against the current build, pulls what it is allowed to pull, parks it in /Library/Updates, and holds the tonight-triggers open.
installd installs. When the window finally opens, the packages are decompressed, verified and moved into place by a different daemon that works in shifts, summoned for the install and released after. The installd page measured those shifts: a few seconds of processor time on an ordinary day, real work only when something is actually being placed. This page’s daemon never touches a package’s contents.
suhelperd, the root helper, has been running since 20 October, which is the day this Mac last installed an OS update, and has used under four seconds of processor time since. It exists because installing into /System needs privileges the daemon deliberately does not hold.
SoftwareUpdateNotificationManager, the only family member running as you, is the face: the badge, the banner, the red dot on System Settings. It runs as your user because notifications are yours, not the system’s.
And the softwareupdate command is not part of the machinery at all. It is a client. When you run it, the daemon’s log records the visit.
The cost, measured honestly
Over two days, 18 hours and 47 minutes, the main daemon used 27.38 seconds of processor time, about ten seconds a day. The mobile twin used 0.21 seconds in ten hours and 47 minutes. Sampled mid-afternoon, both sat at 0.0 per cent CPU. In a series where the Wi-Fi daemon spends five minutes a day and the accounts database daemon nineteen, this is one of the cheapest processes measured, because most of its life is a clock and a wait.
The log agrees. In six hours the daemon wrote 1,721 lines, and they are nearly all visitors’ book entries. This one, verbatim, is the CLI checking in and out:
Adding client SUUpdateServiceClient pid=644, uid=501, installAuth=NO
rights=(), transactions=0 (/usr/sbin/softwareupdate)
Removing client SUUpdateServiceClient pid=644, uid=501
pid 644 was a softwareupdate command, run by user 501, allowed to ask but not to authorise installs. The daemon logged the arrival, the door used, and the departure. A line further down records it choosing its on-console client, the notification manager, for anything that needs to reach the screen.
The one-letter trap
softwareupdate, no d, is the command in /usr/sbin. softwareupdated, with the d, is the daemon in /System. The convention is older than macOS: the d stands for daemon and it has marked background processes since the earliest Unix manuals. It matters here more than usual because the two names sit in the same Settings screen, the same forum threads and the same search results. A command you run belongs in Terminal. A process you watch belongs in Activity Monitor. The daemon’s own log draws the line for you: when the command runs, it is a guest.
What Apple says, and does not
The Mac User Guide page for this feature is called Keep your Mac up to date, and at 270 kilobytes it is one of the longest in the guide. It does not contain the word softwareupdated once. Neither does the guide’s full table of contents. Apple documents the feature, never the machinery:
If you receive a notification that software updates are available, you can choose to install the updates immediately or choose to install the updates later that night.
Later that night. The phrase the guide uses to explain the feature to humans is the same phrase the daemon uses in its own keys, DoItLaterTonightAttemptsCount, and the launch trigger SUOSUScheduler.tonight.install. The documentation and the machinery agree with each other, in words, two floors apart.
The settings page names the switches the same way: Download new updates when available, Install macOS updates, Install Security Responses and system files. Three toggles, and the daemon’s preferences file holds their state as AutomaticDownload, AutomaticallyInstallMacOSUpdates, ConfigDataInstall and CriticalUpdateInstall, all reading 1 on this Mac.
Is it a virus, and can you quit it
It is Apple’s signed platform code, running as a service account that cannot log in, with one line of manual and a settings screen. It is not malware, and the two-in-Activity-Monitor question that brings people here has the boring answer: two daemons, one name, both normal.
Quitting it is equally pointless. The system itself stops and starts the daemon constantly: 26 runs for the main copy, 40 for the mobile copy, in the current stretch of uptime, with the last exit reason reading JETSAM_REASON_MEMORY_IDLE_EXIT, which means the system reclaimed an idle process, by design, the moment memory was more useful elsewhere. Force quitting a daemon the system recycles on purpose buys you an empty row for about a minute. The levers that exist are real and they are upstream: the three switches in Software Update settings, or the schedule options of the softwareupdate command. Turn the switches off and the courier has nothing to deliver, which is the only version of stopping this daemon that means anything.
The short version
softwareupdated is the decision layer of Software Update: it checks every six hours, remembers every offer in a readable ledger, counts your deferrals, downloads what you allow, stages it in /Library/Updates, and holds a nightly window that is allowed to reboot the machine. It costs about ten seconds of processor time a day. It never installs anything; installd does that, suhelperd lifts what needs root, and the notification manager wears the badge. There are two of them in Activity Monitor because the iPhone side of the family ships its own copy, 35 times the size, and both are where they should be. Apple’s own guide describes the whole arrangement without once naming it, and calls it, in the phrase both the docs and the daemon share, later that night.
Questions
What is softwareupdated on Mac?
It is the daemon behind Software Update. Every six hours, and on Power Nap, it asks Apple's catalog whether a newer macOS exists, compares it against what this Mac runs, downloads what you have allowed it to download, and stages the packages in /Library/Updates ready for the night it is allowed to finish. It runs as a dedicated system user called _softwareupdate, not as you and not as root, and its manual page is one line long: softwareupdated is the main daemon responsible for running software updates. It does not install anything itself. When the staged update is finally cleared to go, the install work belongs to installd, which the installd page in this series covers separately.
Why are there two softwareupdated processes in Activity Monitor?
Because there are two daemons with the same file name. The one in /System/Library/CoreServices, 175 KB and the one your updates actually flow through, is the orchestrator. The one in the MobileSoftwareUpdate framework is 6.1 MB, 35 times bigger, carries three CPU architectures because it shares its machinery with the iPhone side of the family, and starts at boot to mind its own weekly cleanup job. Both run as the _softwareupdate user with launchd as their parent, both have been restarted dozens of times by the system in 28 days, and both are quiet. Seeing two is normal and has been for years. There is also a root helper called suhelperd and a notification manager running as you, which makes the full cast four processes when everyone is on stage.
What is the difference between softwareupdate and softwareupdated?
The final d. softwareupdate without the d is the command line tool in /usr/sbin, the one with flags like `--history` and `--schedule`, and it is a client: when you run it, the daemon's own log records the arrival, adding client SUUpdateServiceClient, followed by the tool's path. softwareupdated with the d is the daemon that answers. The two are documented on facing manual pages, and the difference matters when you read forum advice: a command that starts with softwareupdate belongs in Terminal, a process name ending in d belongs in Activity Monitor. Nothing you type at the command line is ever the daemon, and force quitting something in Activity Monitor never runs a check.
Why did my Mac download an update and not install it?
Because downloading and installing are separate permissions, and your Mac is allowed to do the first without the second. On the measured Mac, Software Update settings allow automatic downloads, so when macOS 27.2.1 was offered the daemon pulled it, and a staged Command Line Tools update has been sitting in /Library/Updates since 31 October, half a gigabyte, waiting. The daemon keeps count of the nights you deferred: a preference key literally named DoItLaterTonightAttemptsCount stood at 2. When you pick install tonight, the daemon schedules the window, and its launch trigger for that window carries a flag that says the job may reboot the device. The waiting state is not stuck. It is exactly what download new updates when available, without install macOS updates, produces.
Why is softwareupdated using CPU or network?
For the same reason a courier burns fuel on collection day, not delivery day. Measured over two days and 19 hours the main daemon used 27 seconds of processor time, about ten seconds a day, and its mobile twin used a fifth of a second in eleven hours. The busy moments are predictable: the six-hour catalog check, a download when something new is offered, and the staging and verification of packages, which is real work and shows as network first and CPU second. In six hours it wrote 1,721 log lines, mostly bookkeeping about clients connecting and disconnecting. If it stays busy for an hour with nothing downloading, check the update list, because the daemon only moves what the catalog told it to move.
Can I quit or turn off softwareupdated?
Quitting is pointless and turning it off is a settings question. The system reclaims the daemon under memory pressure on purpose and restarts it on demand, 26 times for the main copy in the current stretch of uptime, so force quitting only buys you an empty row for a minute. The real levers are in System Settings under General, then Software Update: the automatic updates section holds the switches for downloading new updates, installing macOS updates, and installing security responses and system files, and each maps to a key in the daemon's own preferences file. Turn those off and the daemon has nothing to orchestrate. Its manual page, like most of this family, says you should not run it manually, and there is no reason to: everything it does is reachable through settings or the softwareupdate command.
Ready? Buy Ribbon for $15, or read all the guides.