Windows Update Stuck on Windows 11? Fix

Check your laptop’s disk activity light before you touch anything. If it’s blinking steadily, the update is actually doing something — even if the percentage on screen hasn’t moved in twenty minutes. Cumulative updates are 1.5-2.5GB and on a spinning hard drive with a mediocre connection the download alone can take over an hour. If the light hasn’t blinked in thirty minutes or more, the update is genuinely stuck.

A nurse called us at 11pm during her overnight shift — hospital laptop stuck on “installing updates” for almost six hours. She was terrified of force-shutting down because IT had drilled into staff that interrupting updates breaks Windows. I asked about the activity light. Hadn’t blinked in over an hour. We held the power button, restarted, Windows came back and reported “We couldn’t complete the updates. Undoing changes.” Twenty minutes of rollback later she was at her desktop with the update reverted. Ran it again on her day off, completed in forty minutes without issue.

The “don’t turn off your computer” warning is there to prevent people from interrupting updates that are progressing normally. When an update is genuinely stuck with no disk activity for an hour, force-shutting down is safer than waiting indefinitely. Windows is much better at rollback than most users realize — less than 5% of force-shutdowns during updates cause issues serious enough to need a clean install. If the same monthly update keeps failing or breaking things here, you can pause or turn off automatic updates until Microsoft ships a fixed build.

Clear the Software Distribution Folder

This is the standard fix and it resolves about 65% of stuck downloads. It clears Windows Update’s local cache and forces a fresh download attempt.

Open services.msc (Win+R, type it, Enter). Find Windows Update, right-click, Stop. Also stop Background Intelligent Transfer Service and Cryptographic Services while you’re there. Navigate to C:\Windows\SoftwareDistribution\Download in File Explorer and delete everything in the folder. If a file refuses to delete because it’s in use, you didn’t fully stop the services — go back and make sure they’re all stopped. Then restart all three services in services.msc and retry the update through Settings, Windows Update, Check for updates.

Five minutes start to finish. If the update was stuck because the partial download was corrupted — which is the most common cause — it downloads fresh and installs cleanly.

If it fails again at the download stage, your connection itself might be the issue. Switch from WiFi to a wired ethernet connection if you can, or try a different network. Windows Update’s download resume is fragile and intermittent WiFi drops during a multi-gigabyte download cause the exact kind of cache corruption that the Software Distribution reset fixes. If your WiFi keeps disconnecting, fix the connection stability first — the update will keep failing until the underlying network problem is resolved.

SFC and DISM

If clearing the cache didn’t help, the Windows components that the update process depends on might be corrupted.

Right-click Start, Terminal (Admin). Run sfc /scannow first — takes 10-15 minutes, scans every protected system file against factory copies and replaces anything corrupted. If it reports problems it can’t fix, run DISM /Online /Cleanup-Image /RestoreHealth next — this takes 15-30 minutes and contacts Microsoft’s servers to re-download pristine copies of Windows components. After DISM finishes, run sfc /scannow one more time because now SFC has clean source files to work with. Our SFC guide covers reading the CBS.log when SFC reports unfixable corruption.

Restart and retry Windows Update after both commands complete.

If updates download and install fine but fail at the “Configuring update 99%” stage after the reboot, you likely have a driver conflict rather than file corruption. The update tries to install a new driver but an existing one blocks the change. GPU drivers and third-party antivirus are the most common culprits. Temporarily uninstall the suspected driver or disable the antivirus real-time protection, run the update, then reinstall afterward. The 24H2 updates were particularly bad for this — they broke Bluetooth drivers on a huge number of machines. If 24H2 refuses to install at all rather than failing late, that’s a different problem with its own fixes — see Windows 11 24H2 not installing.

Manual Install From Microsoft Update Catalog

If Windows Update keeps failing on a specific KB, you can download the standalone installer and bypass the Windows Update service entirely.

Find the KB number of the failing update in Settings, Windows Update, Update history. Go to catalog.update.microsoft.com in your browser, search for that KB number, download the .msu file that matches your Windows version and architecture (almost always x64). Double-click the file to install — Windows handles it like any standalone update, without going through the update service.

Manual installs sometimes succeed where the normal path fails because they don’t depend on the Windows Update service being in a clean state. About 15% of stuck updates that resist all other fixes install cleanly this way.

If even the manual install fails with an error code, you’re looking at system corruption deep enough that piecemeal repair won’t recover it. A clean Windows reinstall is the realistic path at that point. A related side effect to watch for: cumulative updates that fail partway through sometimes leave the Start menu broken or the machine noticeably slower — those guides cover the specific fixes. If a printer driver update is the specific KB failing, our printer offline guide covers the manual manufacturer-driver install that often bypasses the broken Windows Update path, and if the update installed but then everything froze, we can pull Event Viewer logs and CBS.log remotely to identify exactly which component failed.