Windows Update Stuck or Failing: How to Fix It

A Windows update that sits at the same percentage for an hour, or that downloads, installs, reboots and then rolls itself straight back, is one of the most stressful faults to deal with because you cannot tell whether interrupting it will break the machine. The good news is that Windows is far more resilient about this than it used to be, and most stuck updates come down to one of a small number of causes: not enough free disk space, a corrupted download in the update cache, a damaged system file, or a driver the update refuses to install alongside. Here is how to work through it safely.

First, make sure it is actually stuck

Large feature updates genuinely can sit on the same figure for a long stretch, particularly on a mechanical hard drive or an older processor. A percentage that has not moved for twenty minutes is normal. One that has not moved for several hours, with no disk activity and no drive light flickering, is a different matter.

Never pull the power during the configuring stage after a reboot if you can avoid it. Give it time first, and check for signs of life before you do anything drastic.

  1. Look at the drive activity light on the case or laptop body. If it is flickering, work is still happening.
  2. On a desktop, listen for the hard drive. On a laptop, feel whether the underside is warm.
  3. If you can still reach the desktop, open Task Manager and check whether processes with Update or Trusted Installer in the name are using processor or disk time.
  4. Leave a stuck feature update alone for at least two hours before intervening. Overnight is safer still.
  5. If nothing has moved after that and there is no disk activity at all, hold the power button for ten seconds, then power back on. Windows will usually roll the update back and return you to a working desktop.

Free up disk space before trying again

Feature updates need a substantial working area on the C drive, well beyond the size of the download itself, because Windows keeps a copy of the old installation so it can roll back. On a laptop with a small drive this is the most common reason updates fail repeatedly with no obvious explanation.

Aim for at least 25GB free before you retry a large update. Cumulative security updates need much less, but space is still the cheapest thing to rule out.

  1. Open Settings, then System, then Storage.
  2. Click Temporary files, tick Windows Update Cleanup and Delivery Optimisation Files, then remove them.
  3. Empty the Recycle Bin and your Downloads folder.
  4. Move large video and photo folders to an external drive or OneDrive if you are still short.
  5. Restart, then try the update again from Settings, Windows Update.

Run the built in Windows Update troubleshooter

This is not the token gesture it once was. The troubleshooter resets the update services, clears a stalled queue and repairs common permission problems on the update folders. It fixes a genuine share of cases and takes a couple of minutes.

Run it, restart, and then retry the update before moving on to anything more involved.

  1. Open Settings, then System, then Troubleshoot, then Other troubleshooters.
  2. Find Windows Update in the list and click Run.
  3. Let it finish and apply anything it offers to fix.
  4. Restart the computer even if it does not ask you to.
  5. Go back to Settings, Windows Update, and click Check for updates.

Repair the system files behind Windows Update

If the same error code keeps returning, the component store that Windows Update relies on is probably damaged. Two built in commands repair it. They are safe to run, they do not touch your personal files, and they are the standard first move for any technician facing a repeating update failure.

The first command repairs the component store from Microsoft servers, so you need to be online. The second checks and repairs protected system files. Run them in this order and be patient, because the first one often pauses for a long time around twenty per cent.

  1. Click Start, type cmd, right click Command Prompt and choose Run as administrator.
  2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter, then wait for it to reach 100 per cent.
  3. When that finishes, type sfc /scannow and press Enter.
  4. Wait for the verification to complete and read the result it prints.
  5. Restart the computer and try the update again.

Deal with a specific update that will not install

Occasionally a single update is the problem, usually because of a driver conflict on older hardware. Rather than fighting it forever, you can pause updates, install the rest, and address the awkward one separately.

Note the error code shown next to the failed update in Settings. It matters, because the fix for a 0x800f error is quite different from the fix for a 0x80070 error. Write it down before you retry anything.

  1. Open Settings, then Windows Update, and note the exact error code and the KB number of the failed update.
  2. Click Update history to see whether the same KB has failed more than once.
  3. Use Pause updates for one week to stop the machine retrying the same failing update every day.
  4. Update your graphics, chipset and network drivers from the laptop or motherboard manufacturer support page.
  5. Unpause updates and retry. If the same KB still fails, that is the point to ask for help.

When to get help

Update problems are close to ideal for remote support. Provided the machine reaches the desktop and can get online, we can run the repair commands, clear the update cache by hand, check the update logs for the real reason behind the error code, and install the correct drivers, all in one session while you watch. Nothing needs to leave your house or your office.

The exception is a computer that no longer boots into Windows at all, or one that loops through a failed update and a rollback without ever reaching the desktop. That needs recovery media and hands on the machine, so it becomes a workshop job. If you are unsure which situation you are in, ring us on 028 9623 7853 and describe what you see on screen.

Frequently Asked Questions

Is it safe to force a restart during a Windows update?

It is a last resort, not a first move. Give the update at least two hours with no visible progress and no disk activity before holding the power button. Windows will normally detect the interruption at the next boot, roll the update back and return you to a working desktop, but doing this repeatedly increases the risk of leaving the installation damaged.

What does it mean when an update installs then undoes itself?

That rollback message means Windows hit a problem partway through and put the previous version back to keep the machine usable. It is a protective measure rather than a failure of your hardware. The usual causes are an incompatible driver, damaged system files or not enough free space.

Can I just stop installing updates?

We would not recommend it. Security updates close holes that ransomware and malware actively use, and an unpatched machine is a genuine risk if you bank or shop online. Pausing for a week to work around one bad update is reasonable. Turning updates off permanently is not.

Do you charge if the update still will not install?

Remote support is no fix no fee. If we cannot get your updates working we will explain what we found and what it would take to put right, and you do not pay for the session.

Let us fix it remotely

If you would rather not work through this yourself, we can connect to your computer over the internet and fix it while you watch. Most problems in this guide are sorted in a single session, and remote support is no fix no fee.

Need Immediate Remote Support?

Jump right into a remote support session with our expert technicians. Quick, efficient, and hassle-free.

1-hour session
Expert assistance
Secure connection
£35
per session

Related guides