Get Windows Updates Installing Again
Windows Update installation errors can stem from interrupted downloads, low disk space, damaged system files, service failures, driver conflicts, or a problematic update package. This guide explains how to identify the failure, start with low-risk checks, run the built-in Windows Update troubleshooter, repair Windows system components with DISM and SFC, reset update components, and use the Microsoft Update Catalog when appropriate. It also covers when to pause and seek help, plus habits that reduce the chance of future update failures.
A Windows update that repeatedly fails to install is frustrating, especially when the same notification returns after every restart. The cause is not always the update itself. Interrupted downloads, insufficient storage, corrupted system files, disabled services, third-party security software, and incompatible drivers can all prevent installation. The safest approach is to begin with simple checks, record any error code, and escalate to repair steps only if the failure persists.
Start by identifying the update failure
Before changing anything, note the update’s KB number and any error code shown in Settings > Windows Update. A KB number identifies a specific Microsoft update; an error code can point to download, servicing, storage, or installation problems. Also check whether the update is a cumulative update, a feature update, a driver update, or a Microsoft Defender definition update, because the appropriate response can differ.
Restart the PC once before troubleshooting. A restart clears pending operations that may block the servicing stack. Then return to Windows Update and select Check for updates.
- Keep the device connected to reliable power, particularly on a laptop.
- Use a stable, non-metered internet connection if possible.
- Disconnect nonessential USB devices, external drives, docks, and printers temporarily.
- Ensure that the date, time, and time zone are correct.
- Write down the exact KB number and error code rather than relying on a screenshot alone.
Complete the low-risk checks first
Storage shortages are a common and easily overlooked reason for unsuccessful updates. Windows needs room not only for the downloaded package but also for temporary files, rollback data, and installation staging. Free space on the system drive, usually C:, by removing temporary files or moving personal files to another location.
Open Settings > System > Storage and review Temporary files. Avoid deleting files you need, such as items in Downloads, unless you have checked them first. If your PC has very little available space, aim to free several gigabytes before retrying a large cumulative or feature update.
Also review recent changes. A newly installed antivirus suite, VPN client, disk utility, hardware driver, or system-tuning tool can interfere with update services. Do not disable security permanently, but you may temporarily remove or disable a known conflicting utility according to its vendor’s instructions, then enable it again after testing.
Run the Windows Update troubleshooter
Windows includes a troubleshooter that checks common update settings and attempts straightforward repairs. In Windows 11, go to Settings > System > Troubleshoot > Other troubleshooters, then run Windows Update. In Windows 10, go to Settings > Update & Security > Troubleshoot > Additional troubleshooters and select Windows Update.
When it finishes, restart the computer even if the tool reports no changes. Try the update again afterward. The troubleshooter may not solve every servicing problem, but it is a sensible first repair because it avoids manually altering system folders and service settings.
Repair Windows component files with DISM and SFC
If the update still will not install, repair the Windows image and protected system files. These commands are built into Windows and should be run from an elevated terminal. Save your work first, keep the PC online, and do not close the window while a scan is running.
- Right-click the Start button and choose Terminal (Admin), Windows PowerShell (Admin), or Command Prompt (Admin).
- Run
DISM /Online /Cleanup-Image /RestoreHealthand wait for completion. - Run
sfc /scannowafter DISM completes. - Restart the PC and try Windows Update again.
DISM can use Windows Update to retrieve healthy component files, so it may take time and needs a working connection. SFC then verifies protected files against the repaired component store. If either command reports that it repaired files, the restart is important.
Do not treat a successful download as proof that an update is healthy. Windows must still validate packages, stage files, service components, install changes, and complete a restart sequence. A failure at any stage can produce a different error code.
Reset the Windows Update download cache
A corrupted or incomplete download cache can cause the same update to fail repeatedly. Resetting the update components makes Windows recreate its download folders. This is more invasive than running the troubleshooter, but it does not remove your personal documents or installed applications.
Open an elevated Terminal or Command Prompt and run the following commands one line at a time:
net stop wuauservnet stop bitsnet stop cryptsvcren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.oldnet start cryptsvcnet start bitsnet start wuauserv
Restart Windows and check for updates again. If a command says a service was not started, continue with the remaining commands unless another error prevents the process. The renamed folders can consume disk space temporarily; after updates work normally, Windows can manage the newly created cache.
Choose the right next action for the symptom
| Symptom | Likely first action | What to avoid |
|---|---|---|
| Update stays at 0% or will not download | Check the connection, restart, run the troubleshooter, then reset the update cache. | Repeatedly forcing shutdowns during an active download. |
| Installation reaches a percentage and rolls back | Run DISM and SFC; disconnect nonessential peripherals; review recently added drivers. | Deleting system files or registry entries from unverified guides. |
| A single KB update fails repeatedly | Search the Microsoft Update Catalog by KB number and install the matching package manually. | Installing a package for the wrong Windows version or system architecture. |
| Feature update fails near the end | Free storage, update key drivers, and consider Microsoft’s installation assistant or in-place repair path. | Ignoring backup needs before a major version change. |
| PC will not boot after an update | Use Windows Recovery Environment options such as Startup Repair or Uninstall Updates. | Continuing to restart forcefully if the disk activity indicates work is still underway. |
Use a standalone package only when it fits
For one recurring cumulative update, the Microsoft Update Catalog can be useful. Search using the KB number, then carefully select the package that matches your Windows release and architecture, such as x64 or ARM64. Close open applications before installation and restart when prompted.
This option is best for a clearly identified update. It is not a universal cure for broader servicing issues, and it should not be used to install updates intended for a different Windows version. If the standalone installer also fails, return to the repair steps rather than downloading packages from third-party sites.
When to use recovery options or get help
If the computer starts normally but updates keep failing after the steps above, a repair install may be appropriate. An in-place repair installation can reinstall Windows system components while preserving personal files and many settings, provided you choose the correct option. Back up important files before any major repair or feature update.
If Windows no longer boots after an update, enter the Windows Recovery Environment. From there, options may include Startup Repair, System Restore, and Uninstall Updates. Start with the least disruptive option. Business-managed devices may have update policies or endpoint security controls that require an IT administrator to investigate.
Seek professional or vendor support if you see disk errors, repeated blue-screen crashes, BitLocker recovery prompts you cannot satisfy, or hardware-related error messages. These signs may indicate a problem beyond Windows Update itself.
Reduce the chance of future failures
Leave sufficient free space on the system drive, restart periodically, and avoid interrupting an update once the installation phase has begun. Keep device firmware and critical drivers current through the PC manufacturer’s official support channel. For desktops and laptops, use dependable power during updates; a power interruption in the middle of servicing can damage the installation.
It is also sensible to create regular backups. Updates are important for security and reliability, but no update process is completely risk-free. A current backup turns a difficult recovery scenario into a manageable one.
