You tap Settings > General > Software Update, hit Install Now, and then it sits there. The progress bar under “Preparing Update…” crawls or just freezes for twenty minutes. On iOS 17, this happens most often on iPhone XS and newer models with less than 10GB free, or right after a beta profile was removed. The update never finishes, and you're stuck.
What's actually happening
“Preparing Update” is the phase where iOS verifies the downloaded IPSW, unpacks it, and stages the files. That process needs two things you might not have: free storage and a clean temp folder. iOS 17 needs roughly 6–8GB just for the preparation, on top of the update itself. If your storage is tight, the system quietly fails to write temporary files and retries forever.
The other culprit is a corrupted cached update. If you've tried updating before, iOS keeps a partial download in /var/mobile/Library/Preferences/com.apple.SoftwareUpdate.plist and a stash in the system's OTA cache. That leftover data can conflict with the new one, so the preparation loop spins without progress.
The fix is simple in theory: clear that junk and give iOS room to breathe. But if you just delete the downloaded update from Settings, it doesn't always nuke the underlying cache. That's why most people still get stuck after retrying.
The fix that actually works
Skip the “Delete the update and retry” advice — you've probably tried that. Here's the sequence that forces a clean slate.
- Free up at least 10GB. Go to Settings > General &em; iPhone Storage. Delete videos, offload unused apps, clear Safari cache. The storage indicator should show green at the very top. You need 10GB+ because iOS 17's update package plus preparation takes that much.
- Remove the downloaded update file. In the same iPhone Storage screen, find the update listed under “Recommendations”. Tap it, choose Delete Update. This removes the IPSW but not the hidden cache.
- Force restart your iPhone. For Face ID models: press Volume Up, then Volume Down, then hold the Side button until you see the Apple logo. This clears the update daemon's stuck state and re-initializes the installation process.
- Turn off automatic updates temporarily. Settings > General > Software Update > Automatic Updates — switch off “Download iOS Updates”. This prevents the system from downloading anything in the background while you're trying to install manually.
- Now, re-download and install. Go back to Software Update, and if it shows a newer version, tap Download and Install. On iOS 17, you might see “Preparing Update” for a few minutes after the download finishes — that's normal. But if it hangs past 10 minutes, proceed to the next section.
The reason step 3 matters: the update daemon (running as nsurlsessiond) holds onto the old cache even after you delete the file. A force restart kills that daemon, so the next install starts from scratch.
If it still fails
Sometimes the storage issue isn't visible. Hidden system caches — from diagnostics, podcasts, or old mail attachments — can eat several GB without showing in the iPhone Storage list. Here's what to check:
- Offload unused apps (not just delete them). Offloading removes the app but keeps its data, so it's faster to restore. This frees app binaries, which are often large.
- Clear Safari's website data. Settings > Safari > Clear History and Website Data. That can free up a gig or two in cache.
- Check “Other” storage. On iOS 17, go to Settings > General > iPhone Storage. The “Other” section (often called “System Data”) should be under 5GB. If it's over 10GB, you've got a cache leak. The only way to clear that is a full restore via computer.
If you've done all the above and it still hangs, you're dealing with a controller-level issue. At that point, don't waste time — back up your iPhone, then do a DFU restore and set up as new. That's the nuclear option, but it always works because it reflashes the entire storage partition, eliminating any corrupted OTA state.
One more tip: if you're on a Mac (Sonoma or later), you can update wirelessly via System Settings > General > Software Update on the iPhone — but that uses the same backend, so it won't help if the issue is local storage.
So, before you panic: free the space, nuke the cache, force restart, and only then restore. That sequence has saved me more than a few bricked-feeling iPhone XS units.