A stuck Windows Update is one of the most common reasons machines land on our Edinburgh workbench — usually a laptop that's been sat on "Working on updates 32%" for half a day, or a desktop that reboots, fails, and rolls back in a loop. The good news is that most stuck updates clear with a methodical reset rather than a fresh install. This guide walks through the steps we use in the workshop, in the order we try them.
If the machine boots far enough to use the desktop, you can work through these checks yourself. If it's stuck in a restart loop or won't reach the sign-in screen, skip to the last section — that's where it stops being a DIY job and starts being one for our software troubleshooting team.
1. Be Patient — Then Decide It's Really Stuck
Big feature updates and cumulative patches on slower drives can genuinely sit at 30% or 75% for over an hour. Before you do anything drastic, give the machine at least 60–90 minutes from the last visible change. Watch the hard-drive activity light: if it's still blinking, leave it alone. If the screen has been frozen and the drive light has been silent for twenty minutes solid, it's stuck. Don't power-cycle inside the first hour unless you're certain — pulling the plug mid-update is the single most common way customers in Newington and Stockbridge create a much bigger problem.
2. Run the Built-In Windows Update Troubleshooter
If you can reach the desktop, this is the first thing to try. On Windows 11, go to Settings > System > Troubleshoot > Other troubleshooters and run the Windows Update troubleshooter. It resets the queue, checks for stalled services, and clears a surprising number of low-level snags without you touching a command prompt. It is not magic — it will not fix a corrupted update file — but it costs five minutes and rescues maybe a third of the stuck-update cases we see.
3. Check Disk Space and Time/Date
Two embarrassingly common culprits. Feature updates need roughly 20 GB of spare space on the C: drive; if you're under that, the update will fail at preparation. Open Settings > System > Storage, run Storage Sense, empty the Recycle Bin, and clear old Windows.old folders. Then check that the system clock is right — a wrong date breaks the SSL handshake with Microsoft's update servers and produces baffling error codes. We've seen this on machines that have been unplugged for a few months in Bathgate offices where the CMOS battery had died.
4. Reset the Windows Update Components
This is the proper fix, and it clears most stubborn errors like 0x80073712, 0x800f0922 and 0x80070002. Open Command Prompt or PowerShell as Administrator and run these in order:
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserverren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.oldnet start wuauservnet start cryptSvcnet start bitsnet start msiserver
Reboot and try Windows Update again. Renaming the SoftwareDistribution folder forces Windows to redownload every pending update from scratch — slow on a copper line in Corstorphine, but it fixes a corrupted cache nine times out of ten.
5. Repair System Files With SFC and DISM
If the update still fails, the system image itself may be damaged. From an elevated Command Prompt, run sfc /scannow first, then DISM /Online /Cleanup-Image /RestoreHealth. DISM in particular pulls fresh component files from Microsoft and patches the local image, which clears the "this update isn't applicable" family of errors. Our full walkthrough is in our guide on repairing Windows 11 with SFC and DISM.
6. Pause Updates, Then Try One at a Time
If a single optional driver or feature update keeps poisoning the queue, pause updates for a week (Settings > Windows Update > Pause), then uncheck optional updates and try only the cumulative quality update on its own. Driver updates pushed through Windows Update — particularly graphics and Wi-Fi drivers — are responsible for a fair chunk of the rollback loops we see, and grabbing the driver directly from Intel, NVIDIA or your laptop maker's site is often quicker and more reliable.
7. Use the Manual Catalogue or the Update Assistant
For a specific KB that refuses to install, you can download the standalone .msu file from the Microsoft Update Catalog and run it manually. For a stalled feature update (Windows 11 23H2 to 24H2, for example), the Windows 11 Installation Assistant on Microsoft's site usually works when Windows Update itself has given up. Make sure your important files are safely backed up to OneDrive or an external drive before you start — our data recovery team would rather you backed up first than visited us afterwards.
8. When to Stop and Bring It In
If the PC is stuck in a restart-roll-back loop, blue-screening during the update, or won't reach the sign-in screen at all, stop. Repeatedly forcing a failed update can wreck the registry or the boot configuration, and the fix turns from a fifteen-minute reset into a full reinstall with data recovery on the side. We see this every week from Livingston, Dunfermline and Glenrothes customers who pushed it one reboot too far.
At that point a clean repair install or an in-place upgrade — keeping your files and apps — is usually the cleanest route, and our OS installation service handles it without losing your data. If you can't get to the workshop, our remote support team can drive the recovery from your sofa, provided the machine can reach the desktop in Safe Mode.
Edinburgh Update Help, Same Day
Windows Update problems are nearly always fixable without losing your files, but they get harder the longer the loop runs. If your PC has been spinning on the same percentage all morning, bring it in or book a remote session and we'll get it back to you patched, current, and quiet again.