
How to Fix a Mac Stuck on Loading Bar After an Update
When macOS hangs on the Apple logo and progress bar following a system update, the bootloader (boot.efi) has stalled while verifying the cryptographically Signed System Volume (SSV), reconciling an incomplete auxiliary kernel extension collection, or attempting to write swap memory to an internal SSD exhausted of free storage. Whether the bar freezes at 100%, stalls midway, or reboots into an infinite loop, resolving the boot halt requires determining whether the operating system is hung on a filesystem seal, a hardware handshake, or damaged staging cache.
Quick Diagnostic Matrix
| Symptom | Root Cause | Setting / Path / Key Combo | Recommended Fix |
| Progress bar freezes at 100% or last 5% for hours | Signed System Volume (SSV) seal mismatch or APFS dirty filesystem state | macOS Recovery > Disk Utility | Run First Aid sequentially on APFS Container and volumes; check APFS snapshot status. |
| Progress bar halts halfway; cooling fans run at 100% | Legacy third-party kernel extension (.kext) or launch daemon stalls boot sequence | Safe Mode (Shift or Power Hold) | Boot into Safe Mode to bypass non-Apple kexts and trigger automatic cache rebuilds. |
| Boots to loading bar, shuts down, and repeats (boot loop) | Insufficient free storage space preventing installer from expanding system payload | Recovery > Terminal (df -h) | Verify storage overhead; delete corrupted /macOS Install Data staging directory. |
| Screen turns black or loading bar stops with no disk activity (Intel) | Stale NVRAM boot-args or desynchronized SMC power management rails | Option + Command + P + R | Perform a 20-second NVRAM/PRAM purge and reset the System Management Controller. |
1. Verify Real-Time Freeze vs. Background APFS Migration
Before forcing a reboot, verify that the system is genuinely frozen. Large macOS updates (such as major version upgrades) convert internal database formats, re-index Spotlight metadata, and seal APFS snapshots—operations that can keep the progress bar stationary for up to 45 minutes without visual movement.
- Perform the Caps Lock Test: Tap the
Caps Lockkey on the built-in keyboard.- If the green LED fails to illuminate, the macOS kernel has panicked or the hardware bus is completely deadlocked. You must proceed with a hard reboot.
- If the green LED toggles on and off normally, the CPU is actively processing background tasks, but the display server has not drawn the next percentage tick. Wait an additional 20 minutes.
- Disconnect all peripherals: Unplug Thunderbolt docks, external drives, display adapters, and USB hubs. A hung handshake from an external mass-storage device can stall the bootloader indefinitely while it queries connected volumes.
- Force a power cycle: Press and hold the Power button (or Touch ID sensor) for 10 seconds until the screen cuts to complete black. Leave the power cord connected, wait 15 seconds, and power on.
2. Boot into Safe Mode to Bypass Problematic Kexts
Safe Mode restricts macOS to essential Apple-signed drivers, runs an automated directory integrity check on the boot volume, and flushes temporary kernel caches (including dynamic loader and font caches).
On Apple Silicon (M1, M2, M3, M4):
- Shut down the Mac completely.
- Press and hold the Power button. Continue holding it through the initial chime until the screen reads “Loading startup options”.
- Highlight your main boot volume (usually Macintosh HD).
- Press and hold the
Shiftkey, then click Continue in Safe Mode. - Release the
Shiftkey. The Mac will boot with “Safe Boot” visible in red in the top-right menu bar.
[Apple Silicon: Powered Off]
└── Hold Power Button Until "Loading startup options"
└── Select Macintosh HD > Hold Shift > "Continue in Safe Mode"
On Intel Macs:
- Turn on the Mac and immediately press and hold the
Shiftkey. - Release
Shiftas soon as the Apple logo and progress bar appear. - If the Mac loads into the desktop successfully, restart the machine normally from
> Restart. The clean rebuild of the kernel cache performed during Safe Mode often resolves the regular boot hang.
3. Run Disk Utility First Aid in Recovery Mode
If an update is interrupted during disk writes, the APFS container metadata can become desynchronized, causing the bootloader to reject the startup disk.
- Access macOS Recovery:
- Apple Silicon: Hold the Power button from a powered-off state until startup options appear, select Options, and click Continue.
- Intel: Power on and immediately hold
Command (⌘) + Runtil the spinning globe or Apple logo appears.
- Select Disk Utility and click Continue.
- In the top toolbar, click View > Show All Devices.
- Run First Aid in strict hierarchical order from top to bottom:
- The physical drive name (e.g., APPLE SSD AP0512M).
- The APFS Container (e.g., Container disk1).
- The System Volume (Macintosh HD).
- The Data Volume (Macintosh HD – Data).
- If First Aid returns “File system check exit code is 0”, the drive structure is healthy. If it reports an uncorrectable error, you must reinstall macOS.
4. Purge Broken Update Directories via Terminal
When a software update runs out of scratch space or encounters an interrupted download, it leaves behind an unsealed directory called
macOS Install Data. The bootloader will prioritize booting from this corrupted installer path rather than the stable root volume.- In macOS Recovery, go to the top menu bar and select Utilities > Terminal.
- Run the disk space utility to ensure the internal drive is not at 100% capacity:Bash
df -h(If theMacintosh HD - Datamount shows 0 bytes available, the operating system cannot allocate swap files to boot). - Mount the target storage volume if it is encrypted with FileVault:Bash
diskutil apfs unlockVolume /dev/disk1s1(Enter your FileVault user password when prompted). - Check for and remove corrupted installer staging files:Bash
cd "/Volumes/Macintosh HD" ls -la - If
macOS Install Datais present, delete it to force the bootloader back to the standard macOS kernel:Bashrm -rf "macOS Install Data" - Type
rebootand hit Enter.
5. Purge Stale NVRAM and SMC Registers (Intel Only)
On Intel machines, configuration parameters like the selected startup disk, display resolution, and kernel debugging flags are held in volatile NVRAM. Stale pointers from a previous macOS build can freeze the bootloader during early hardware setup.
- Reset NVRAM: Power on the Mac and immediately press and hold
Option + Command + P + R. Hold all four keys for a full 20 seconds. Release when you hear the startup chime twice or see the screen illuminate a second time. - Reset the SMC (System Management Controller):
- MacBooks with T2 Security Chip: Shut down. Hold
Control(left) +Option(left) +Shift(right) for 7 seconds, then hold thePower buttonalongside them for another 7 seconds. Release all keys, wait 5 seconds, and power on. - Desktop Macs (iMac, Mac mini, Mac Studio): Unplug the power cord from the wall. Wait 15 seconds. Plug the cord back in, wait 5 seconds, and press the power button.
6. Reinstall macOS (Overwrites System Without Losing Data)
If the update corrupted the Signed System Volume (SSV) beyond recovery, the bootloader will refuse to execute unsigned system files to protect against tampering. You can lay down a fresh operating system image without affecting your applications, desktop files, or user accounts.
- Boot into macOS Recovery (Hold Power on Apple Silicon; hold
Command + Ron Intel). - Select Reinstall macOS [Version Name] from the main utilities window and click Continue.
- Agree to the terms and select Macintosh HD as the destination disk (never select an external drive or a separate partition).
- Click Install.
Because modern versions of macOS utilize separate APFS volumes for system binaries (
Macintosh HD) and user data (Macintosh HD - Data), the installer wipes and reinstalls only the cryptographically sealed operating system container, leaving all personal files, configurations, and documents untouched.