How to Fix a Failed or Stuck iOS Update

Published August 28, 2026 · Last reviewed September 2, 2026

Problem 1: not enough storage

The installer needs free space for the download and for unpacking it, which is more than the download size shown. iOS offers to temporarily delete apps to make room; that works, but it is worth doing a real clear-out instead so the problem does not recur.

Action

Free several gigabytes by deleting downloaded video and podcast episodes, then offloading unused apps.

Why it helps

These are the largest and most easily reclaimed categories, and none of it is data you would miss.

Verification

iPhone Storage shows enough free space and the update proceeds.

Action

Update via a computer instead, if freeing space is genuinely difficult.

Why it helps

A computer-based update needs much less free space on the phone, because the unpacking happens on the computer.

Verification

The update completes with the phone still nearly full.

Problem 2: the update does not appear

Three ordinary explanations before you assume a fault:

• Staged rollout. Apple releases updates to devices in waves, so an update can take days to reach yours. Nothing is wrong.
• Your model is not supported. If a newer major release exists but is never offered, your device may have reached the end of its support.
• A configuration profile or beta profile is installed and is holding the device on a different update track. Check for profiles in Settings under General.

Forcing an update to appear is rarely worth it. Waiting a few days is the correct response to a staged rollout.

Problem 3: stuck on the progress bar or the Apple logo

1. Wait at least an hour before doing anything. A large update genuinely can sit at a near-complete progress bar for a long time, and interrupting it is riskier than waiting.
2. If it has genuinely not moved for over an hour, force restart: press and release Volume Up, press and release Volume Down, then hold the Side button until the Apple logo appears.
3. If it boots normally, check the iOS version and re-run the update.
4. If it returns to the same stuck state, connect it to a computer and use recovery mode — choosing Update, never Restore.

In recovery mode, Update reinstalls iOS while keeping your data; Restore erases the device. Read the dialogue before tapping. If the Update download takes more than 15 minutes the phone may exit recovery mode — simply repeat the sequence and choose Update again.

Problem 4: “Unable to Verify Update”

This almost always means the phone could not reach Apple's servers to verify the download, not that anything is damaged. In order: check the network connection, confirm the date and time are set automatically in Settings › General › Date & Time, restart, and delete the downloaded update from iPhone Storage before downloading it again. A VPN or a filtered corporate network is a common cause — turn the VPN off and retry.

Problem 5: the update finished but something is wrong

Restart first, then update your apps, then wait for the first point release. Do not restore from a backup as a first response to a post-update bug — it is a long process and it rarely helps, because the backup restores your data onto the same new iOS version that has the problem.

What to do before any of this happens

Take a verified backup, and keep enough free storage that an update is never a crisis. Both are unremarkable and both convert a stressful evening into a routine one.

How it works

An iOS update runs in stages: download, verify, prepare, and install. Each stage fails in its own way, which is why the symptom identifies the cause. A storage failure occurs at preparation, because the compressed image has to be unpacked before it can be written — this is why the installer needs more free space than the download size suggests, and why updating through a computer works on a nearly full phone: the unpacking happens on the computer.

“Unable to verify” is a signature check failing. Every update is cryptographically signed, and the device confirms with Apple's servers that the version is still being signed before installing it. That check needs a working network path and a correct system clock, so a VPN, a filtered corporate network, or a wrong date all produce the same message — none of which indicates a damaged device or a corrupted file.

A stuck progress bar is usually not stuck. The final stage writes the new system and migrates data, and the progress indicator is an estimate rather than a measurement, so it can sit at the same position for a long time while real work continues. Interrupting during a write is the one action that can leave the device in a genuinely broken state, which is why the correct response is to wait an hour first — and why recovery-mode Update, which reinstalls the system without touching the data partition, is the right recovery rather than an erase.

Worked example

A 64 GB iPhone with 3.1 GB free, refusing an update that needs more space. iOS offers to temporarily remove apps; the owner declines, because the same problem would recur at the next release.

A storage pass instead. A podcast app is holding 7 GB of downloaded episodes, most already played; deleting them and enabling automatic deletion returns 7 GB. Setting Messages to keep one year returns another 4 GB. Offloading nine apps not opened in a year returns 2 GB. Free space goes from 3.1 GB to about 16 GB, and the update downloads without complaint.

The install then appears to hang: the progress bar sits at roughly 80% for 41 minutes. The owner's instinct is to force restart, which is exactly the wrong move during a system write. They wait. At the 52-minute mark the bar moves, and the phone completes normally at 58 minutes.

One further problem afterwards: a corporate VPN was left on, and a subsequent smaller update returned “Unable to Verify Update”. Turning the VPN off and retrying resolved it in one attempt — a signature check that could not reach Apple's servers, not a damaged download.

Nothing was erased at any point, and the storage clear-out means the next update will not hit the same wall.