Windows Update failures explained: Why they happen and how to fix them

A Windows Update failure is frustrating partly because the error messages rarely explain what actually went wrong. The update either hangs, rolls back, or throws an error code, and the system offers nothing useful about the cause. Understanding the underlying causes behind most Windows Update problems makes troubleshooting considerably more logical. Each points to a distinct set of fixes, applied in order from simplest to most involved.

1. Transient issues that a restart resolves

A significant number of Windows Update failures are caused by temporary system states: a previous update that downloaded but hasn’t been applied yet, a service that needs to restart to release a file lock, or a pending operation that is blocking the installation from proceeding. Windows needs a full restart to clear these states, and attempting another update without restarting first often produces the same failure.

After restarting, go to Settings > Windows Update and click Check for updates to trigger a fresh attempt. If the connection is working and no other issues are present, this step frequently solves the issue. 

Network issues operate the same way. Because Windows Update relies on a steady stream from Microsoft’s servers, subtle drops or proxy restrictions can stall a download without raising an obvious error. If a fresh reboot doesn’t work, test your internet stability or temporarily toggle off any active VPNs before moving to file system diagnostics. 

2. Insufficient disk space

Feature updates, in particular, require significant temporary storage during download and installation, often 10 to 15 GB for a major Windows 11 update. If the system drive is nearly full, the update will fail at the download or installation stage, frequently producing error code 0x80070070 or similar. The fix is freeing up space before reattempting.

Disk Cleanup (accessible through the Start menu or by right-clicking the drive in File Explorer and selecting Properties) can recover space from temporary files, the Windows update cache, and delivery optimization files. Uninstalling unused applications and clearing the Downloads folder are two more easy ways to free up space. Feature updates also require that the system is not currently running the Windows installation on a drive that is nearly full, so this is worth checking before troubleshooting anything more complex.

3. Corrupted update components

Windows stores downloaded update packages in the SoftwareDistribution folder and stores update package signatures in the catroot2 folder. If either of these becomes corrupted, subsequent update attempts will fail even when the connection is working and disk space is adequate. Corrupted system files can produce the same result.

Windows provides two tools for addressing this. System File Checker (SFC) scans for corrupted system files and repairs them using a cached copy. It runs from an elevated Command Prompt with the command sfc /scannow. The Deployment Image Servicing and Management tool (DISM) repairs the Windows system image itself, pulling replacement files from Windows Update when needed. Run it in the same elevated Command Prompt with DISM.exe /Online /Cleanup-Image /RestoreHealth after SFC completes. Restart after both tools finish, then retry the update.

For cases where the SoftwareDistribution folder itself is the problem, Windows Update services can be stopped temporarily, the folder renamed to force Windows to rebuild it fresh, and the services restarted. This is an advanced step; following Microsoft’s documented procedure or a verified IT reference for the exact command sequence is recommended.

4. Specific updates that consistently fail

Sometimes, a specific update repeatedly fails through standard channels even on an otherwise healthy PC. While this happens more frequently with optional updates and hardware drivers than critical security patches, it can affect any package. When it does, you can bypass the glitchy update pipeline entirely by going directly to the Microsoft Update Catalog (catalog.update.microsoft.com). Just search for the update’s KB number — found in your Windows Update history or error message — download the matching package for your system architecture, and run the installer.

Manual installation sidesteps the broken step in the background update process, applying the patch cleanly and updating your system’s error log in the process. 

When the problem is deeper

If these steps don’t solve the problem, you’re likely facing a deeper issue within Windows itself. An in-place upgrade reinstalls Windows while keeping all your files, apps, and settings intact, making it a great way to fix deep-seated update bugs without starting over. A clean install is the absolute last resort and requires backing up your data first. Keep in mind that heavy fixes like these are rarely necessary; the steps above clear up almost all Windows Update issues. 

If your business is dealing with persistent Windows Update problems across multiple devices, our team can diagnose and resolve update failures at scale and keep your systems current and protected. Get in touch.