Fixing Update Failures and Getting the Update to Finish

Most update failures come down to one of four things: the device is low on power, short on storage, offline or unstable on internet, or the update package is corrupted or blocked. Start with the safest checks first, then clear temporary blockers and retry once cleanly. If the same failure keeps coming back, it’s time to use repair or support instead of hammering the update again.

What the failure actually looks like

Update failures usually fall into a few patterns, and matching the pattern helps you choose the right fix.

- Download stuck at 0%, 1%, or another number for a long time
- Install starts, then stops with an error
- Device keeps restarting during the update and never finishes
- Update appears to complete, then rolls back to the previous version
- The same update prompt returns again and again

If the download never starts, focus on internet, storage, and account issues first. If the download finishes but installation fails, the problem is more often a corrupted file, a blocked service, or not enough free space. If the device reboots in a loop or rolls back, that points to a deeper install problem, and you should avoid repeated forced restarts unless the device is clearly frozen. A normal update can take a while, but it should still show signs of life, such as changing progress, activity lights, spinning icons, or a restart that eventually ends.

The exact message varies, so the symptom matters more than the wording. A stalled percentage, a restart loop, or a rollback are all different clues about where the update is failing: download, install, reboot, or verification.

When this guide applies and when it doesn’t

This approach fits most phone, computer, app, and operating system updates that fail during download, installation, restart, or rollback. It applies whether you are on a consumer device or a small-business device, as long as you can still open the normal settings screens that handle updates.

You usually need normal user access for the first checks, but some fixes require Administrator access on a computer or the equivalent elevated permission on a device. If the device is managed by work or school policy, you may need an administrator to clear the blocker for you.

If the update failure affects many devices at once, or the vendor is reporting an outage, the safest move may be to wait. A retry during a live outage often fails the same way.

Before you start, make sure you can leave the device plugged in or charging, and that you can wait without interrupting the process. If there’s anything you can’t afford to lose, back it up first. If the device is already booting badly, crashing, or showing signs of storage damage, stop after the safer checks and move to recovery or support sooner rather than later.

Safe checks to do first:

• Confirm the device has enough battery or is connected to power
• Confirm you have a stable internet connection
• Confirm there is enough free storage for the update to finish

Start with the safest checks

Start here because these checks are low-risk and often fix the problem by themselves.

1. Connect the device to power if it is a phone, tablet, or laptop. The update should not depend on a nearly empty battery. If the battery is low, charge it for a while before retrying.
2. Check free storage. Updates often need extra space beyond the size of the update file itself. Remove a few large downloads, old videos, or unused apps if storage is close to full.
3. Confirm the internet is stable. A download can stall or corrupt if Wi‑Fi drops in and out. If possible, use a reliable network and avoid switching networks mid-update.
4. Leave enough uninterrupted time. Some updates need a long stretch where the device stays awake, powered, and connected. If you know you’ll be interrupted, wait until later instead of forcing the update now.

If these checks don’t change anything, the update itself may already be partly downloaded or partly installed in a bad state. The next step is a clean restart, not repeated tapping on the same failed prompt.

Restart and try the update again

A restart clears temporary locks, stuck background tasks, and half-finished connections that can block an update. Use a normal restart first if the device still responds.

1. Save anything you can still save. If the device is responsive, close your apps and save open work.
2. Restart the device normally. Use the regular power menu, not a forced shutdown, unless the device is frozen.
3. After the restart, wait a minute before opening the update screen. This gives background services time to settle.
4. Go back to the update screen and try the update once more. Do not keep hammering the same button if it fails immediately. Let the device settle, then try a clean retry.

If the update now moves past the point where it failed before, the restart probably cleared the block. If it fails again in the same place, move on to clearing the common blockers instead of repeating the same cycle.

Clear the blockers that cause repeated failures

If the update fails over and over, something may be interfering with the download or install. The usual suspects are a bad cached update file, not enough space, a VPN, security software, background apps, or a permissions problem.

Start with the reversible items first:

• Turn off VPN or proxy software during the update
• Pause third-party antivirus or security tools on a computer if they are known to interfere with updates
• Close background apps that may be holding files open
• Free more storage if space is still tight
• Delete the partially downloaded update only if your device provides a clear built-in option to do so

On a phone or tablet, also check whether low-power mode or battery saver is limiting background activity. On a computer, make sure you are signed in with an account that can install updates, and that disk permissions are normal. If the update relies on a company-managed device policy, the blocker may be outside your control and need admin help.

Where to check

Update or System Update screen
Storage settings
Power or Battery settings
Network, VPN, or Proxy settings
Security or Antivirus settings on a computer

Don’t manually delete system update files unless the device’s own settings or support instructions tell you to. Removing the wrong file can make the next attempt worse.

If the update still fails after you clear these blockers, the cached package or system component handling the update may be damaged. At that point, the next step is usually to force a clean download from the built-in update screen or use the platform’s repair option.

If the update is stuck at one percentage

A frozen percentage can mean two different things: the update is still working slowly, or it has genuinely hung. The difference matters because interrupting a live install can do more harm than waiting a bit longer.

If the number hasn’t changed for only a short time, wait. Some updates sit at the same percentage while they verify files, unpack packages, or prepare a restart. If the device is still warm, the activity light is changing, or you can see signs of background work, give it more time.

If the percentage has been frozen for a very long time and the device shows no other activity, try a normal restart only if the device remains responsive. If it is not responsive, use the platform’s safe forced restart method, not a random power cut. Then retry the update once after the device comes back up.

If the same percentage freezes every time, that usually points to a damaged package, a problem file, or a blocker that survives restarts. Repeatedly forcing the same update is a bad idea at that point. Clear the cached update, make more space, remove temporary interference, and then try again from the update settings screen.

How to tell whether it worked

Don’t trust the progress bar alone. Confirm that the update actually finished and stuck.

Check for these signs:

• The version number changed in the update or about screen
• The device boots normally without returning to the update screen
• The same update prompt does not reappear after a restart
• Apps, settings, and sign-in still work as expected

Use the device’s version screen to confirm the new build or update number. If the screen still shows the old version, the update didn’t complete even if part of the process looked successful. If you were expecting a restart as part of the install and the device instead rolls back or returns to the previous version, treat that as a failed update, not a successful one.

If everything looks normal but the update prompt keeps coming back, the device may have downloaded the update but not installed it cleanly. In that case, clear the cached package if the device offers a safe built-in way to do that, then try again.

How to avoid the same failure next time

A few habits make update failures less likely:

• Keep some free storage open instead of running the device nearly full
• Update while connected to stable power on a phone, tablet, or laptop
• Use a steady Wi‑Fi connection for large downloads
• Leave the device alone until the update finishes
• Avoid running VPNs or security tools during the install if they’ve caused trouble before

If a specific app keeps failing, make sure that app is allowed to update in the background and that it has enough storage and permissions. If the same operating system update fails every time, note exactly where it fails. That detail helps separate a connection problem from a corrupted download or a device-specific issue.

When to use repair mode or support

Stop doing normal retries when the same update fails after you’ve checked power, storage, internet, restart, and the common blockers. That is the point where repair mode, recovery tools, manufacturer support, or a technician is the safer move.

Use a repair or recovery option if:

• The device won’t boot normally after the failed update
• The update rolls back every time
• You can’t free enough space without risking important files
• The update screen is frozen and the device is no longer responsive
• The system says the install files are corrupted and keeps failing again

If the device holds data you can’t replace, back it up before trying a repair or recovery option whenever the device still allows it. Some repair paths keep data, but not all do.

If the vendor provides a repair install that keeps your data, that is usually the next safest step after basic troubleshooting. If even that fails, contact support with the exact failure point, the device model, the current version, and what you already tried. That gives you a better shot at the right fix without more guesswork.

Conclusion

If the update is still failing after the safe checks, stop repeating the same attempt and switch to the next least risky option: clear the blockers, retry once cleanly, and then move to repair or support if the failure keeps coming back. If you still can’t confirm a clean finish, don’t keep forcing it; get help before the device gets less stable or you risk data loss.

Frequently Asked Questions

How long should I wait before calling an update stuck?

If the device is still showing signs of work, wait longer. If the percentage has not changed for a long time and there is no activity, treat it as stuck and move to a clean restart or the next troubleshooting step.

Should I force restart during an update failure?

Only if the device is frozen or completely unresponsive. If it still responds, use the normal restart first. A random power cut can make a partially installed update worse.

Why does the same update keep failing again after I retry it?

That usually means the problem is not the retry itself. A corrupted download, not enough storage, a blocked service, a VPN, or security software can keep causing the same failure until you clear the blocker or remove the bad update file.