How to Fix Windows Update Stuck Downloading or Installing

Windows Update is the backbone of system security and feature parity on your PC, but the process frequently freezes mid-download or hangs at the installation phase. When the progress bar stops moving, your screen displays a spinning circle, or the update counter drops backward, the update pipeline has likely encountered a corrupted cache, a stalled service, or a driver conflict. Rather than force-restarting your machine and risking file system corruption, you can run through a structured recovery sequence that targets the exact component causing the bottleneck.

Before You Start: Ensure your PC is connected to a stable internet connection and plugged into power. If you are running Windows 11 Enterprise or Windows 10 Enterprise LTSC, some automatic update behaviors are controlled by your organization’s group policies, which may limit which steps you can perform.

Step 1: Pause and Resume the Update

Navigate to Settings > Windows Update. Open the Start menu, type Settings, and select the gear icon to launch the system preferences panel. From the left sidebar, click Windows Update to reveal the update dashboard.
Click Pause for one week. Locate the pause toggle and select it to halt all active downloads. This action forces the update service to release its current file handles and prepares the pipeline for a fresh request.
Wait thirty seconds, then click Resume. Allow the system to register the pause command before reactivating the download. Watch the progress bar to see if it begins moving forward again. If the status reverts to stuck immediately, proceed to the next step.

Step 2: Clear the Windows Update Cache

Stop the Windows Update service. Press Win + R, type services.msc, and press Enter. Scroll to Windows Update, right-click it, and select Stop. This action prevents the system from locking the cache files while you delete them.
Delete the SoftwareDistribution folder contents. Open File Explorer and navigate to C:\Windows\SoftwareDistribution\Download. Select all files inside the folder and press Delete. These files contain the partially downloaded update packages, and removing them forces Windows to fetch fresh copies from Microsoft servers.
Restart the Windows Update service. Return to the Services window, right-click Windows Update, and select Start. The service will rebuild its index and begin a clean download cycle.

Step 3: Run the Windows Update Troubleshooter

Open the troubleshooter settings. Go to Settings > System > Troubleshoot > Other troubleshooters. This centralized hub contains built-in diagnostic scripts designed to detect and repair common update failures.
Launch the Windows Update troubleshooter. Click the Run button next to Windows Update. The diagnostic tool will scan your update components, check for service misconfigurations, and attempt automatic repairs.
Apply any recommended fixes. Review the results window and click Apply fixes for each detected issue. Restart your PC afterward to allow the repaired services to initialize correctly.

Step 4: Reset Windows Update Components via Command Prompt

Open an elevated Command Prompt. Right-click the Start button, select Terminal (Admin) or Windows Terminal (Admin), and confirm the User Account Control prompt. Administrative privileges are required to modify system services and register components.
Stop the related update services. Paste the following commands one at a time and press Enter after each: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver. These commands halt the update agent, cryptographic verifier, background installer, and Windows Installer engine.
Rename the cache and registration folders. Run ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Renaming these folders preserves the original data while forcing Windows to create fresh directories.
Restart the services. Execute net start wuauserv, net start cryptSvc, net start bits, and net start msiserver. Finally, close the terminal and return to Windows Update to check for updates.

Step 5: Check for Conflicting Third-Party Software

Identify active security or optimization tools. Open Settings > Apps > Installed apps and review your list for antivirus suites, firewall programs, or system cleaners. These applications often intercept update traffic or lock system files during installation.
Temporarily disable real-time protection. Open your third-party security app and toggle off real-time scanning or firewall rules. Leave the program running in a paused state rather than fully uninstalling it.
Retry the update. Return to Windows Update and trigger a fresh download. If the process completes successfully, re-enable your security software and consider adding an exclusion for the C:\Windows\SoftwareDistribution folder.

Pro Tip: If you manage multiple PCs or prefer automated recovery, save the Command Prompt commands from Step 4 into a text file named ResetUpdate.cmd. Right-click the file and select Run as administrator whenever the update pipeline freezes again.

Troubleshooting: Common Failure Points

Update fails with error code 0x80070003 or 0x800f0954. These codes typically indicate a permissions issue or a corrupted component store. Run sfc /scannow in an elevated terminal to repair system files, followed by DISM /Online /Cleanup-Image /RestoreHealth to fix the underlying Windows image.
Download completes but installation rolls back immediately. This usually points to insufficient disk space or a pending reboot conflict. Free up at least 20 GB on your system drive, open Task Manager, and end any processes named setuphost.exe or TiWorker.exe before trying again.
Progress bar disappears or shows 0% after hours. The background download agent has likely timed out. Toggle your network adapter off and on via Settings > Network & internet, or switch to a wired connection to eliminate Wi-Fi handshake failures that stall large payload transfers.

Windows Update relies on a tightly coordinated chain of services, caches, and network handshakes. When one link breaks, the entire process halts. Following this recovery sequence addresses the most frequent breakdown points without requiring advanced system manipulation. Keep your recovery commands saved, monitor your disk space, and report any persistent error codes to your IT administrator if you are on a managed device.

Over to you: Which error code has caused the most trouble during your update attempts?