![macOS Update Stuck or Won't Install? 14 Fixes That Actually Work [2026]](/images/blog/macos-update-stuck-fix-hero.webp)
You clicked "Update Now," walked away, and came back to a progress bar that hasn't moved in an hour. Or worse — a black screen with a spinning gear or an Apple logo that never advances. A stuck macOS update is one of the most anxiety-inducing Mac problems, because the instinct is to panic and force restart immediately, which is sometimes exactly the wrong move. The good news: the overwhelming majority of "stuck" updates are not actually stuck at all — they're just slow, and the fix is patience followed by a short, specific checklist.
This guide covers all 14 fixes, ordered by how likely each one is to be the actual cause, from the simple "wait it out correctly" step through disk space, network, Safe Mode, and — as a safe last resort — a full Recovery Mode reinstall that doesn't touch your files. We also explain exactly how long each stage should normally take, so you know when "slow" becomes "actually stuck."
What makes this problem particularly stressful is timing: macOS updates are usually started right before bed or right before leaving for the day, which means the "is it stuck or just slow" question often gets answered hours later, under time pressure, with no easy way to check progress in the meantime. Working through this guide methodically — starting with the duration table below — removes most of that guesswork and tells you within a few minutes whether you're looking at a normal install or a genuine problem.
We field this exact call constantly at IT Cares, both from home users and from small businesses managing a handful of Macs without dedicated IT staff. The pattern is consistent enough across Intel and Apple Silicon models that we can usually identify the stuck stage and likely cause within the first two diagnostic questions — this guide follows that same triage logic so you can do it yourself before reaching for the phone.
Before anything else: don't force restart in the first hour
The single most common cause of a macOS update turning into a real, hours-long problem is a user force-restarting a progress bar that was simply moving slowly, not frozen. Interrupting an active install while files are being written is the one scenario in this whole process that can cause genuine corruption. Unless your screen is completely black with zero progress indicator, give it a full 60-90 minutes before touching the power button.
How Long Should Each Update Stage Actually Take?
macOS updates move through distinct stages, and each has a different normal duration. Knowing this table prevents most unnecessary force restarts:
| Stage | Normal Duration | Treat as stuck after |
|---|---|---|
| Downloading update | 5-40 min (depends on connection + update size) | No progress for 45+ min on stable Wi-Fi |
| "Preparing Update" | 5-25 min | No movement for 45+ min |
| Restart + black screen with progress bar | 15-45 min (major version), 5-15 min (point update) | No bar movement for 60+ min |
| "Few minutes remaining" holding steady | Can genuinely hold for 20-30 min near the end | 90+ min stuck at the same estimate |
| Completely black screen, no logo, no bar | Should not happen for more than 2-3 min | 10+ min — likely already stuck |
If you're within the normal window for your stage, the best fix is simply to keep waiting. If you've exceeded it, move on to the fixes below. It's worth noting that these windows are conservative estimates built from typical repair-shop cases across a wide range of Mac ages and configurations — a brand-new Apple Silicon Mac with fast internet and plenty of free storage will often finish well inside the lower end of each range, while an older Intel Mac with a nearly-full drive can legitimately sit at the upper end without anything being wrong. Context matters more than the raw clock time alone.
Can't fix it yourself? Skip the trial-and-error.
Our certified bilingual tech remotes in, checks the exact stuck stage, and resolves it on the spot — same day, from $119.99. No fix, no fee.
14 Fixes for a Stuck macOS Update
Wait the Full Recommended Window
Use the table above to check whether you're actually within normal range for your current stage. Major version upgrades (moving to a new yearly macOS release) routinely take 45-90 minutes end to end on perfectly healthy Macs — this is normal, not a malfunction. Resist the urge to intervene until you've genuinely exceeded the window for your specific stage. If you can, physically observe the screen for the first 5-10 minutes after starting rather than walking away immediately — this confirms the install actually began correctly and gives you a reliable timestamp to measure the wait window against, rather than guessing later how long it's actually been stuck.
Check Available Disk Space
Go to Apple menu > About This Mac > Storage (or check before starting if you haven't updated yet). macOS needs roughly 20-45GB of free space to download the installer, stage files, and create a recovery snapshot — major version upgrades need more than point updates. If you're below 20GB free, the update can stall silently on "Preparing Update" with no clear error. Free up space (empty Trash, offload large files to an external drive or iCloud, use Storage > Recommendations) and retry.
Verify You're on a Stable Network
A macOS installer package can be 12-15GB for a major release. An unstable Wi-Fi connection — one that drops or throttles mid-download — is one of the most common causes of a stuck "Preparing" or download stage. If possible, connect via Ethernet (a USB-C to Ethernet adapter works on any modern Mac). If Wi-Fi only, move closer to the router, disconnect other bandwidth-heavy devices on the network, and avoid VPNs during the download. Corporate or public Wi-Fi networks with content filtering or captive portals are a particularly common culprit, since they can silently block or throttle the specific Apple domains the installer needs to reach without showing any obvious error — if you're on such a network, switching to a personal hotspot or home connection for the download portion specifically often resolves a stall that nothing else fixes.
Check Apple's System Status Page
Occasionally, Apple's own update servers experience high load or brief outages right after a new macOS release, especially in the first 24-48 hours. Check apple.com/support/systemstatus on another device for "Software Update" or "Mac App Store" service issues. If Apple's servers are degraded, waiting a few hours (or trying overnight) resolves it without any action on your end.
Force Restart Once You've Confirmed It's Truly Stuck
If you've exceeded the normal window in the table above with zero progress movement, hold the power button for 10 seconds until the screen goes black, then press it once to restart. In most cases, macOS resumes the update automatically or restarts the download from where it left off — you rarely lose the progress made so far.
Disconnect All External Peripherals
Unplug every external drive, USB hub, dock, printer, and non-essential accessory before retrying — leave only the keyboard/mouse (if wired) and charger connected. A peripheral that doesn't respond correctly during the install's hardware re-scan can stall the whole process, particularly older USB hard drives and some Thunderbolt docks.
Delete the Downloaded Installer and Re-Download
A partially corrupted download is a common, quiet cause of a stall. Open Finder > Applications and look for an app named "Install macOS [version name]" — if present, delete it (you may need to quit System Settings first). Then go back to System Settings > General > Software Update and let it re-download the installer fresh. This alone resolves a large share of stuck-download cases.
Boot Into Safe Mode and Retry From There
Shut down, then hold Shift while powering on (Intel), or hold the power button until "Loading startup options" appears and select your disk while holding Shift (Apple Silicon). Safe Mode loads a minimal set of software and clears some system caches, which can clear whatever was blocking the update. Once in Safe Mode, check Software Update again — for major version upgrades you may need to restart normally first, since some installs can't run entirely inside Safe Mode.
Reset NVRAM and SMC (Intel Macs)
A corrupted NVRAM or SMC state can occasionally interfere with the installer's ability to restart and resume correctly. Shut down, press Power, then hold Option + Command + P + R for about 20 seconds to reset NVRAM. For SMC on MacBook Pro/Air: hold Shift + Control + Option + Power for 10 seconds while off, then power on normally. Apple Silicon Macs handle both automatically and don't need a manual reset — a full shutdown and restart achieves the equivalent.
Check for MDM Profiles or Restrictive Security Software (Business Macs)
On Macs managed by a company (enrolled in an MDM/Mobile Device Management profile), IT policy can delay, block, or interfere with updates by design — sometimes intentionally, to control rollout timing across a fleet of devices, sometimes as an unintended bug in the management profile itself. Check System Settings > General > Device Management for an installed profile. If present, contact your IT administrator before troubleshooting further; forcing an update against an active MDM restriction can create a longer-lasting conflict than the original stall, and in some managed environments can trigger a compliance flag that causes additional headaches unrelated to the original update problem.
Check Startup Security Utility Settings
On Macs with the T2 chip or Apple Silicon, a restrictive Startup Security Utility setting (Full Security requiring a specific trusted state, or a custom Secure Boot policy) can occasionally block an update from completing during the firmware-verification step. Boot into Recovery Mode, open Utilities > Startup Security Utility, and temporarily set security to "Reduced Security" if you've customized this setting, then retry the update and restore your preferred setting after.
Free Additional Space via System Data Cleanup
If disk space was tight even after Fix #2, dig deeper: Apple menu > About This Mac > Storage > Manage. Clear old iOS device backups, unused language files, and large cached files under "System Data" (often mislabeled as huge but frequently safe to reduce via a restart, which clears temporary caches). Emptying the Trash on all connected drives and clearing your Downloads folder can also free several GB quickly. Photos libraries and old Xcode/developer caches are two frequently-overlooked space hogs worth checking specifically if you're a few gigabytes short of the threshold — both can quietly grow to tens of gigabytes without the user realizing it.
Reinstall macOS via Recovery Mode (Keeps Your Data)
If the update has failed or stalled at the same point twice in a row, boot into Recovery: hold the Power button until "Loading startup options" appears (Apple Silicon), or hold Cmd+R during startup (Intel). Choose Reinstall macOS from the utility window. This downloads fresh system files and installs over your existing setup without erasing your personal files, apps, or settings — it's the safest deep-repair option and resolves most installs that fail at the same stage repeatedly, because it replaces the entire system-file set at once rather than trying to patch whatever got corrupted during the failed attempt. Expect this process to take roughly as long as, or slightly longer than, a normal major update, since it's downloading the full installer again from Apple's servers. Back up important files first regardless, using Time Machine or our data recovery software guide as reference if anything looks wrong beforehand — this is standard precaution, not a sign the reinstall itself is risky.
DFU/Revive via Apple Configurator (Last Resort, Apple Silicon)
If Recovery Mode itself won't boot or the Mac is completely unresponsive after repeated failed attempts, Apple Silicon Macs can be restored using Apple Configurator on a second Mac via a USB-C cable, in DFU (Device Firmware Update) mode. This fully re-installs the firmware and OS from scratch and is the deepest recovery option available before hardware service — it goes a level below even a standard Recovery Mode reinstall by rewriting the low-level firmware that Recovery Mode itself depends on. This step requires a second Mac, the correct cable, and careful attention to backup status beforehand, since a DFU restore does erase the drive in most cases (unlike every fix above it in this list). Most users are better served bringing the Mac to a technician at this stage rather than attempting it solo for the first time on a machine that's already in a fragile state. IT Cares performs DFU restores routinely on both MacBook and desktop Apple Silicon models and can usually complete one within an hour, including data recovery beforehand where the drive is still accessible.
Apple Silicon vs. Intel: what actually differs during updates
Apple Silicon Macs (M1/M2/M3/M4) generally install updates faster and more reliably than Intel Macs, thanks to a more integrated firmware-and-OS verification process, but they're also more sensitive to a truly interrupted install since NVRAM/SMC resets aren't manual — a full shutdown-and-restart is the only equivalent. Intel Macs give you more manual recovery tools (NVRAM/SMC key combos, standard Cmd+R Recovery) but can take noticeably longer on major version upgrades, especially on machines with traditional (non-SSD) storage or less than 8GB RAM, where 90+ minute installs are common and normal.
Common Mistakes That Turn a Slow Update Into a Real Problem
The single most damaging habit we see is force-restarting repeatedly, in quick succession, while the progress bar was still genuinely moving. Each interruption during an active file-write increases the chance of leaving the system volume in a partially-written state, which is exactly the scenario that eventually requires a full Recovery Mode reinstall. If you're going to intervene, do it once, after confirming you've exceeded the normal window in the duration table, not every ten minutes out of anxiety.
The second common mistake is closing the laptop lid mid-update, assuming it will pause safely like a normal sleep cycle. Some update stages explicitly block sleep and will simply stall in whatever state they were in in when the lid closes, which can look identical to a genuine freeze but is really just the Mac waiting for the lid to reopen. Keep the lid open and the display awake for the entire duration of any macOS installation, and disable Energy Saver settings that might dim or sleep the display automatically during a long install.
The third mistake is starting a major macOS upgrade with less than 15 minutes of remaining battery, on battery power alone, with no charger nearby. If the battery dies mid-install, the resulting interruption is far more likely to cause real corruption than a controlled force restart, precisely because it happens without warning at an unpredictable point in the write process. Always plug in before starting any update, and for major version upgrades specifically, keep the charger connected for the entire process even if the battery shows a full charge at the start.
Finally, don't assume a successful update means you're permanently safe from this issue. New macOS versions occasionally reintroduce update-related bugs that were fixed in a previous release cycle — this has happened with staging-space calculation bugs and installer-verification bugs across multiple recent releases. If an update that previously went smoothly suddenly stalls after a new macOS version drops, treat it as a fresh troubleshooting case rather than assuming your Mac is uniquely broken.
Preventing a Stuck Update Next Time
Most stuck updates are preventable with three habits: keep at least 30-40GB of free storage as a standing buffer (not just before an update), install major macOS version upgrades on a stable wired or strong Wi-Fi connection rather than public or mobile-hotspot Wi-Fi, and avoid installing a brand-new macOS version in its first week — waiting for the first point release (.1) after a major launch avoids the highest-risk period when Apple's servers are most loaded and early bugs are still being patched. None of these guarantee a perfectly smooth update, but together they eliminate the two most common root causes covered in this guide.
Is This a Widespread Bug or a Problem With My Specific Mac?
Stuck macOS updates are one of the most commonly reported issues across Apple Support Communities, MacRumors forums, and enterprise IT forums like the Jamf community, and the pattern repeats predictably around every major release: a spike in reports in the first 48-72 hours (server load and early bugs), a smaller spike around each subsequent point release, and a steady background rate the rest of the time tied mostly to individual storage and network conditions. That volume is useful context — this is a widely shared category of issue tied to Apple's release cycle, not evidence that your specific machine is uniquely defective.
That said, a few signals do point toward something specific to your Mac rather than a general update-cycle issue: the same update stalling at the exact same percentage or stage on repeated attempts (suggests corrupted local files or a hardware issue rather than a server problem), a Mac that struggles with every update it's ever tried to install (suggests chronic low storage or an aging drive), or a stall that only happens on this one machine while other Macs on the same network and macOS version update normally (points at local disk health or a peripheral). Disk Utility's First Aid tool (Applications > Utilities > Disk Utility, select your drive, click First Aid) is a quick way to rule out an underlying storage-health problem before assuming the update itself is simply buggy.
Drive age matters here too. SSDs on Macs older than 6-7 years, and any Mac that has never had a clean reinstall in its lifetime, statistically show a higher rate of update failures tied to accumulated filesystem clutter and, occasionally, genuine SSD wear. If your Mac fits that profile and updates have become progressively less reliable over time, a clean Recovery Mode reinstall (Fix #13) proactively, rather than only after a failure, is a reasonable maintenance step.
macOS Update Still Won't Complete?
IT Cares resolves stuck macOS installs in Montreal and remotely across Canada: disk diagnostics, safe Recovery Mode reinstall, and DFU restore for Apple Silicon when needed. Most cases fixed same-day, without data loss.
Frequently Asked Questions
How long should a macOS update actually take?
A full macOS version update (moving to a new yearly release) commonly takes 45-90 minutes total: 20-40 minutes downloading, 10-20 minutes "Preparing," and 20-40 minutes installing with one or two restarts. Smaller point updates (a .1 or .2 release) usually finish in 15-30 minutes. Older Macs, Macs with less free storage, and slower internet connections can take noticeably longer — we've seen legitimate installs on older, storage-constrained MacBooks stretch past two hours without anything actually being wrong. Don't assume something is broken until the progress bar has shown zero movement for a full hour at whichever stage you're on.
Is it safe to force restart during a macOS update?
It's safe once you've confirmed the update is genuinely stalled — no progress bar movement for a full hour, or a completely black screen with no Apple logo or progress indicator at all. What you should avoid is force restarting while the progress bar is visibly moving, even slowly, since interrupting an active file-write to the system volume is the one scenario in this entire process that can cause real corruption requiring a full reinstall. If in doubt, always err toward waiting longer rather than restarting sooner.
What if my Mac shows a black screen with a frozen progress bar?
A black screen with a visible, unmoving Apple logo and progress bar for more than 60-90 minutes, with zero increments the entire time, indicates a genuinely stalled install — usually caused by insufficient staging space, a corrupted update package, or in rarer cases a failing storage drive. Wait the full hour first regardless, since some installation stages appear completely frozen on screen but are still writing data slowly in the background. If it's truly stuck after that window, force restart once and reattempt the update; if it stalls again at the exact same point, stop retrying the same way and boot into Recovery Mode to reinstall macOS instead.
Can insufficient storage cause a macOS update to get stuck?
Yes, and this is one of the two most common causes we see. macOS needs roughly 20-45GB of free space to download the installer, stage files, and create a recovery snapshot safely — major version upgrades need more than point updates. If your Mac was below about 15-20GB free when the update started, it can stall silently on "Preparing Update" with no clear error message pointing at storage as the cause. Check Apple menu > About This Mac > Storage before starting any future update, and free up space first if you're close to full.
Will I lose data if a macOS update fails midway?
In the vast majority of cases, no — macOS updates are specifically designed to be resumable and don't touch your personal files (Documents, Photos, Desktop) during the system-file installation stage. The update either completes successfully on retry, or macOS automatically rolls back to the previous working version. The realistic data-loss risk comes from repeatedly force-restarting during active disk writes, which in rare cases can corrupt the system volume and require a Recovery Mode reinstall. We still recommend a Time Machine or cloud backup before any major macOS version upgrade as standard precaution, the same way you'd back up before any significant system change.
Should I use a wired connection for macOS updates?
It genuinely helps, especially for large downloads on unstable Wi-Fi. A major-version macOS installer package can be 12-15GB, and an unstable or throttled Wi-Fi connection is one of the most common causes of an update stalling during the download and "Preparing" stages specifically. If you have access to Ethernet — even via a simple USB-C to Ethernet adapter — use it for major updates. If Wi-Fi is your only option, move physically closer to the router and avoid running other bandwidth-heavy tasks (streaming, large uploads, cloud backups) during the download window.
What's the difference between being stuck on "Preparing Update" and stuck while "Installing"?
"Preparing Update" happens before your Mac restarts into the installer proper — it's verifying the downloaded package and staging files on your existing storage, and is most often stalled by low disk space or a corrupted download that needs to be deleted and re-fetched. Being stuck on the black-screen progress bar during "Installing" happens after the restart, while system files are actively being written to disk — this stage is more sensitive to interruption and is more often linked to a failing drive, or on managed business Macs, a conflicting security or MDM profile blocking part of the install. Knowing which stage you're stuck on tells you exactly which fix in this guide to try first.
Comments (3)
I almost force restarted three times before finding this. Turns out my update was sitting at "About a minute remaining" for 25 minutes and that was apparently completely normal for the last stage. Left it alone and it finished on its own. Wish I'd known that before nearly interrupting it.
My MacBook Air had only 8GB free and the update kept stalling on Preparing Update for hours. Cleared out old iPhone backups and some old Final Cut project files to get to 60GB free, retried, and it finished in under 30 minutes. Should have checked storage first.
Had a work MacBook stuck for two full days because of an MDM profile conflict I didn't even know existed. IT Cares figured that out over remote support in about 20 minutes and coordinated with our IT admin to push it through properly. Would have never guessed that was the cause on my own.
Leave a Comment