macOS upgrades

Upgrading to macOS 27? The first 48 hours, explained honestly

By CoreGuard · Aug 16, 2026 · 17 min read

What actually happens after a major macOS upgrade?

After a major macOS upgrade your Mac has deferred work to get through. How long that work lasts has one dated statement behind it — an Apple Communities answer during the Tahoe 26.2 cycle said the daemons involved "would be expected to do that for maybe a few hours or days after installing an OS update/upgrade" — while how long the symptoms last was never measured by anything we found. What the dated record names for the days after an update is indexing and photo-library work — the January 2026 answer names spotlightknowledged, mediaanalysisd, photoanalysisd and photolibraryd. Beyond those four, this blog covers other macOS background jobs on their own pages — mobileassetd fetches separately-delivered assets (which can include on-device Apple Intelligence models), bird and fileproviderd reconcile iCloud sync state, and dasd schedules deferred activities. Nothing we cite attributes those to an upgrade specifically; they are here as reading, in case a name you see is one of them (Oakley recorded "at least 701 non-identical activities submitted" in 72.5 seconds of a single boot on macOS 26.5.2 — a submission count from one boot, not an upgrade-specific measurement). Heat, fan noise, battery drain and heavy disk activity can accompany that work — an Apple Communities answer says plainly that "Battery drain and heat are expected" while the Mac indexes files and processes the photo library — but on their own those symptoms establish neither a healthy migration nor damage. What they justify is waiting and watching the trend, not a conclusion. The launch we have dated evidence for is Tahoe in 2025; that is the one launch we can point at directly here. Golden Gate itself is unreleased as this is written, so read the timings below as that one dated comparison, not as measurements of 27.0.

Where things stand: this guide was written during the Golden Gate beta cycle — as of August 16, 2026 the latest builds listed in MacRumors' Golden Gate timeline are developer beta 5 (August 10) and public beta 3 (August 11), and that roundup states the release is expected in September 2026. Everything below is dated and sourced to either the documented 2025 Tahoe launch wave, the documented Golden Gate beta behaviour, or Apple's and Howard Oakley's published notes about 27 itself — nothing here is a measurement of the release build, and we'll update this page when 27.0 actually ships.

The short version

The 2025 Tahoe launch produced a documented wave of complaints about elevated CPU, heat and battery drain. How long the background work runs has one dated statement behind it — Apple Communities, January 2026: those daemons "would be expected to do that for maybe a few hours or days after installing an OS update/upgrade" — while how long the symptoms last was never measured by anything we found. The 2025 Tahoe launch is the dated example of the complaint wave itself (a thread opened four days after release has since collected 35 me-toos). Nobody has measured 27.0 — the "48 hours" in our title is the window this guide covers, not a promised duration.
The dated record names four workers for the days after an update — spotlightknowledged, mediaanalysisd, photoanalysisd and photolibraryd (Apple Communities, January 2026). Other names you may see — mobileassetd, iCloud's sync family, dasd — have their own posts here explaining what they do, which is a place to read rather than a claim about your upgrade.
Two documented compatibility points, each with a named source: per Howard Oakley's June 25, 2026 round-up, Rosetta is not automatically restored after the upgrade (he reports you'll be prompted to reinstall when an Intel app needs it), and, per MacRumors' roundup, Golden Gate runs on Apple silicon only — that roundup states Tahoe is the last macOS for Intel Macs.
If your backups target a Time Capsule: test before upgrading. Oakley's deprecations round-up covers AirPort Utility and Time Capsules specifically — it says nothing about AFP servers in general, and neither do we — and his readers' documented workaround runs SMB3 via a Samba server.
The honest rule for load and heat that are trending down: give it time on power before judging — long enough for the burst to finish, which the only dated statement puts at hours to days. That patience does not extend to a Mac that shuts itself off, kernel-panics or can't be used — those deserve attention the same day. A plateau with symptoms, once the burst has had days to finish, is its own story — there's a section for it below.

A schematic, not measured data. The groups show kinds of macOS background work — the dated record ties indexing and photo-library work to the days after an update; the others are general background. They overlap, and no ordering is claimed; the only dated estimate of its length is Apple Communities' "maybe a few hours or days". The trend, not the peak, is the signal.

The 2025 precedent

macOS Tahoe 26.0 shipped on September 15, 2025. Four days later, on September 19, an Apple Communities thread titled "macOS Tahoe 26 causes overheating, battery drain, and blurry document previews" was opened; it has since collected 35 me-toos, and one of the two replies to it says plainly that "Battery drain and heat are expected" while the Mac indexes files and processes the photo library. MacRumors carried a thread bluntly named "Tahoe 26.0 is Melting my Battery" started that same day, where posters on September 20–21 pinned their load on WindowServer — "CPU usage is around 20%, the main culprit being windowserver." What those threads establish is the complaint wave, not how long it lasted — none of them reports a resolution time. For the duration, the closest dated statement we have is an Apple Communities answer during the Tahoe 26.2 cycle (January 2026), which named four daemons from the same families as the roster above — spotlightknowledged, mediaanalysisd, photoanalysisd and photolibraryd — and said they "would be expected to do that for maybe a few hours or days after installing an OS update/upgrade." That is the honest span: hours to days, not a number with a guarantee attached. The advice that circulated — leave the Mac plugged in and awake while it works — is a recommendation, not a finding: a major upgrade queues a backlog of deferred work, and nothing published tells us what makes one Mac clear it faster than another.

One thing may genuinely differ this year. MacRumors, reporting Apple's release notes for Tahoe 26.6 (July 27, 2026), wrote that the update "optimizes Spotlight for the release of macOS 27" — that is MacRumors' rendering of Apple's notes, and it is all we found published: nothing we could find says what the optimisation does, or whether it shrinks the post-upgrade reindex. We'll find out whenever 27.0 actually ships — expected in September, per that roundup.

Who's actually doing the work (and where to read about each)

If Activity Monitor fills up, the names you are most likely to recognise are ones this blog has already covered — each with its own post, its own sources and its own decision tree, so you get a place to read rather than a panic. This is our coverage map, not a census of what runs during an upgrade:

Spotlight's indexers (mds, mds_stores, mdworker) — the classic post-upgrade heavyweight, including its disk-write side. Our post shows how to tell catch-up indexing from a stuck loop.
photoanalysisd and mediaanalysisd — Photos and media analysis re-runs. Sustained CPU from these two is consistent with those analysis passes doing their job — our post on it shows how to tell that from a process that is stuck.
mobileassetd — fetches separately-delivered assets, which can include on-device Apple Intelligence models. Can use the network while it downloads them. (General background: nothing we cite ties it to an upgrade.)
fileproviderd, bird and the iCloud family — iCloud sync-state reconciliation. (General background: nothing we cite ties it to an upgrade.)
dasd — the scheduler deciding when the deferred activities among the above run (it schedules deferred work such as backups and scans; it is not the dispatcher for every task on this list). Worth knowing this one by name in upgrade week: the Golden Gate betas gave it a documented memory-leak wave (below).
deleted — the purge daemon; our post on it carries Oakley's log-level tracing of repeated purge rounds during Tahoe update preparation, plus the pending-update snapshot that grows until you install it.

The full map, with the burst-vs-plateau reading that applies to all of them, is the daemon directory.

Documented changes and compatibility checks — check these before upgrading

Apple silicon only. Golden Gate runs only on Apple silicon Macs; Tahoe is the last macOS for Intel machines (MacRumors roundup). If you're on Intel, this upgrade isn't yours — and Tahoe was still receiving updates as of July 2026 — 26.6 shipped on July 27.
Rosetta is not restored by the upgrade. Oakley's deprecations round-up (June 25, 2026), verbatim: "After upgrading to Golden Gate, Rosetta won't be automatically restored, so if it is needed, you will be prompted to install it again." So the first launch of an Intel-only app after upgrading should bring up that prompt rather than simply failing — and on a bad connection or a managed Mac, the prompt itself is a wall. Rosetta being present is not a promise that a given app runs; per-app compatibility is still the vendor's business. Golden Gate is also, per the MacRumors roundup, the last macOS that fully supports Rosetta 2 — MacRumors reported in February 2026 that Rosetta support for apps ends after macOS 27, and that Apple will continue supporting older, unmaintained gaming titles with Rosetta along with software running Intel binaries in Linux VMs beyond macOS 27, with possible future security fixes. That report describes no broader carve-out for ordinary native Intel Mac apps. The pre-upgrade check takes one command and is in the how-to below — on the 346-app Mac this guide was written on, exactly 2 apps still need it.
Time Capsule administration faces uncertainty. The same round-up covers the deprecations: AirPort Utility "is no longer included with new clean installations of macOS" (it survives an in-place upgrade, but "functionality is not guaranteed starting in macOS 27"), and readers achieved Time Capsule compatibility by running SMB3 through a Samba 4.24.3 server. That published record is about AirPort Utility and Time Capsules specifically — we have seen nothing stating a macOS 27 status for AFP servers in general, so don't read one here. If your Time Machine target is a Time Capsule, test the whole path before you commit, or migrate the backup target first.
Encrypted HFS+ is deprecated, per Oakley's same round-up — still readable in 27, and in his words it "will not be supported in a future version of macOS." Old encrypted backup drives should migrate to APFS on your schedule, not a future update's.
Log archives change format. A logarchive made on 27.0 can't be read on anything before 26.2 (Oakley) — niche, but it bites anyone who diagnoses Macs for others.
A downgrade may not find your library where it left it — precedent only, not a documented Golden Gate change. One MacRumors forum poster reported in December 2025 that upgrading to Tahoe converted the Photos database to a format Sequoia could not read; that is a single first-hand account with no Apple advisory either way (our photolibraryd post covers the same thread). Nothing published says whether 27 does the same, so plan any downgrade as if libraries won't open afterwards — one more reason the pre-upgrade backup is not optional.

The beta watchlist — dated, with fix status stated plainly

Three process-level issues surfaced during the Golden Gate betas. None is confirmed for the release build; all are worth knowing by name in case they survive:

dasd memory leak. A MacRumors thread (June 25 – July 27, 2026, ~31 posts) documented dasd at 10–70.6 GB of memory on betas 2–3, and our dasd post lists the hardware those reports name, from an M1 iMac to an M4 Max Studio and an M5 MacBook Pro. Fix status from the thread itself: mixed through beta 3, and its last word is one hedged user "not seeing it in beta 4; might be fixed?" — no beta 5 report either way. Our dasd post carries the full story and the one-Mac reference points to compare against — explicitly not thresholds.
appstoreagent at 250%+ CPU — reported alongside the dasd leak in the same thread.
AMPDevices.framework at 100% CPU — a single report in the beta 5 discussion thread (August 10, 2026), quoted in full: "AMPDevices.framework was using 100% of CPU and staying there. 'more than 10' in Feedback. I thought this was fixed, but it isn't." (What the Feedback line counts is ambiguous, so we won't interpret it.) Nobody else confirmed it in the posts we could read — pages 1–2 of 3; page 3 refused our request — so it stands as one report, not an established pattern.

If 27.0 ships with any of these alive, the reading is the same as always: note your exact build, check whether the load trends down, and file Feedback rather than force-quitting in a loop.

When upgrade-week load stops being normal

The honest heuristic from the daemon map applies with an upgrade-week twist: the opening stretch is a legitimate burst, so a plateau is only worth calling once the burst has had time to finish. Nobody has published a threshold for when a burst becomes a plateau, and we are not inventing one: give it clearly longer than the "hours or days" the work is expected to take, then judge the flatness rather than the height. That patience applies only to load and heat that are trending down, never to a Mac that shuts itself off, panics or cannot be used, which deserves attention the same day. Once the burst has had days to finish, look for the plateau-plus-symptom combination — the same process pinned high, heat or fans that never settle, overnight battery drain — and use the per-daemon posts above to work out whose plateau it is. Two upgrade-specific tells: free space that seems to vanish can be a pending-update snapshot or post-upgrade snapshots (the purge daemon's territory — measure in Disk Utility, not Finder), and a battery that drains after the update has its own diagnosis post — find the process before blaming the OS.

The cheapest in-page measurement, if you'd rather not click out: open Activity Monitor → Energy a few hours after the upgrade and write down the top name and its number, then look again the next day. (Those intervals are our suggestion for getting two comparable readings, not a documented schedule — any two spaced-out readings do the job.) One reading is a snapshot. A visibly smaller number for the same name tells you the displayed value differed between the two readings — nothing more; two samples are not a measurement of your machine. If the same name keeps coming back at a similar number across several spaced-out readings, that is the one to read about — the per-daemon posts above tell you what it does. Two snapshots cannot establish a trend; they only tell you what the display said at those two moments.

How to prepare a Mac for macOS 27 — four checks before you upgrade

Back up, completely, and verify it. A Time Machine run plus a spot-restore of one file. One MacRumors forum poster reported (Dec 2025) that upgrading to Tahoe converted the Photos database to a format Sequoia could not read; there is no Apple advisory either way, and nothing published says what 27 does. Treat the backup as the only true undo.
Count your Intel apps. system_profiler SPApplicationsDataType | grep -c "Kind: Intel" — on the Mac this guide was written on, 346 apps included exactly 2 Intel ones. If the count is nonzero, expect the Rosetta reinstall prompt on first launch of those apps, and update or replace what you can beforehand.
Test your backup target if it's a Time Capsule. Run a backup, then restore one file from it. If it depends on AirPort Utility, plan the migration to an SMB target before the upgrade, not after.
Clear the runway. Free space (the installer needs headroom), pending app updates installed, and — if you rely on the Mac for work — a plan to leave it plugged in and awake while the burst finishes.

Where CoreGuard fits

CoreGuard is an honest, local-only Mac health monitor — it observes and explains, and never cleans or optimizes. Upgrade week is exactly its shape of problem: live CPU, temperature and fan readings with the top process named in plain English, and a per-minute history of system CPU, memory and temperature, so "is this settling or is it a plateau" is a curve you can see across the whole 48 hours instead of a feeling on hour six. It makes no network connections of any kind, and the danger-visibility layer is free, always.

Frequently asked questions

Why is my Mac hot after upgrading to macOS 27?

One hypothesis to check first, if your Mac is hot in the days after upgrading, is the backlog: for the days after an update the dated record names indexing and photo-library work (spotlightknowledged, mediaanalysisd, photoanalysisd, photolibraryd), and macOS works through such deferred jobs in bulk. Two separate records sit behind that, and they are not the same event: the 2025 Tahoe launch produced a documented wave of heat and battery-drain complaints (with WindowServer named in one thread), while the four daemons above and the "maybe a few hours or days" estimate come from a January 2026 Apple Communities answer about a Tahoe 26.2 update. Neither is a diagnosis of your machine, and 27.0 has not shipped yet — treat any window as the one dated comparison rather than a measured fact. Heat that trends down on power, over hours or days, is consistent with the migration finishing; load that stays flat once the burst has had time to finish, with symptoms attached, deserves investigation. Severe symptoms — thermal shutdowns, kernel panics, a Mac you cannot use — are never something to sit out for three days.

How long does indexing take after a macOS update?

Hours to days: the only dated statement we could find is an Apple Communities answer from the Tahoe 26.2 cycle, that the daemons involved "would be expected to do that for maybe a few hours or days after installing an OS update/upgrade." Nothing published says what puts a given Mac at one end of that range or the other. MacRumors, reporting Apple's release notes, wrote that Tahoe 26.6 "optimizes Spotlight for the release of macOS 27" — what that changes about the post-upgrade reindex is unpublished, so treat any shortening as unknown rather than promised. If indexing-like load stays flat well after the burst should have finished, our Spotlight post shows how to tell catch-up from a stuck loop.

Will my Intel apps work on macOS 27?

Rosetta 2 remains available — per the MacRumors roundup, Golden Gate is the last macOS that fully supports it — so Intel apps can still run through translation, but that is not a guarantee any particular app works: apps break for their own reasons and vendor support statements still matter. Rosetta is also not automatically restored by the upgrade; per Howard Oakley's round-up, you will be prompted to install it again the first time an Intel app needs it. Count your Intel apps before upgrading with: system_profiler SPApplicationsDataType | grep -c "Kind: Intel".

Does macOS 27 work with a Time Capsule?

Treat it as at risk. AirPort Utility no longer ships with clean macOS 27 installations and its functionality is not guaranteed, per Howard Oakley's deprecations round-up; his readers kept Time Capsules working by connecting over SMB3 via a Samba server. Nothing published states a general macOS 27 status for AFP servers. Test a backup and a restore before you upgrade, or migrate to a supported SMB target first.

Should I wait to upgrade to macOS 27?

That depends on what your Mac must not break. The honest checklist: a verified backup, a count of your Intel apps, a tested backup target (especially if it is a Time Capsule), and tolerance for a stretch of elevated load while the migration works. If any of those is shaky — or your tools' vendors haven't declared support — waiting for the first point release costs little; Tahoe was still receiving updates as of July 2026.

Sources & further reading