Fix Windows Update Showing the Same Failed KB on Every Scan
🔍 WiseChecker

Fix Windows Update Showing the Same Failed KB on Every Scan

When you check for updates in Windows 11 or Windows 10, the same KB update fails to install and reappears on every subsequent scan. This cycle wastes time, consumes bandwidth, and leaves your system missing a security or quality update. The root cause is usually a corrupted update cache, a stuck update component, or a broken system file that prevents the update from finalizing. This article explains why the failed KB keeps reappearing and provides step-by-step fixes to break the loop permanently.

Key Takeaways: Breaking the Failed Update Loop

  • Windows Update Troubleshooter > Run: Automatically detects and resets corrupted update cache and service states.
  • Stop and rename SoftwareDistribution and Catroot2 folders: Forces Windows Update to rebuild its download cache and component store.
  • DISM and SFC commands in an elevated Command Prompt: Repairs system file corruption that prevents updates from installing.

ADVERTISEMENT

Why the Same KB Update Fails Repeatedly on Windows 11

Every Windows update consists of a package identifier the KB number and a set of component files that must replace or modify existing system files. When an update fails, the Windows Update client marks the attempt as failed in the registry but does not remove the pending download files from the local cache. On the next scan, Windows sees the update is still applicable because the files were never fully replaced, so it attempts to install again. If the underlying corruption or service state has not been fixed, the update fails again, creating the loop.

Common triggers for this loop include:

  • A system file that the update needs to modify is corrupted or locked by another process.
  • The SoftwareDistribution folder contains a partially downloaded or corrupted update file.
  • The Windows Update service or the Background Intelligent Transfer Service BITS is stopped or misconfigured.
  • A third-party antivirus or security tool blocks the update from replacing protected files.

Understanding this mechanism helps you target the correct fix. You need to clear the failed download, repair the system files, and reset the update services rather than simply retrying the installation.

Steps to Stop the Failed KB from Reappearing on Every Scan

The following sequence repairs the most common causes of the update loop. Run each step in order and do not skip any steps unless a step explicitly succeeds and the issue is resolved.

Step 1: Run the Windows Update Troubleshooter

  1. Open Settings
    Press Windows + I to open Settings. Go to System > Troubleshoot > Other troubleshooters.
  2. Run the Windows Update troubleshooter
    Find Windows Update in the list and click Run. Follow the on-screen prompts. The tool will scan for common issues like stuck services, corrupted cache, and misconfigured proxy settings.
  3. Apply any fixes found
    If the troubleshooter reports issues, click Apply this fix. Restart your PC and check for updates in Settings > Windows Update. If the KB still fails, proceed to Step 2.

Step 2: Reset Windows Update Components Manually

  1. Open an elevated Command Prompt
    Press Windows + X and select Terminal Admin or Command Prompt Admin. Click Yes on the User Account Control prompt.
  2. Stop the update services
    Type each command and press Enter after each one:
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
  3. Rename the SoftwareDistribution and Catroot2 folders
    Type:
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\catroot2 Catroot2.old
  4. Restart the update services
    Type:
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver
  5. Close the Command Prompt and restart your PC
    After restarting, open Settings > Windows Update and click Check for updates. The failed KB should now download fresh files without the corrupted cache.

Step 3: Repair System Files Using DISM and SFC

  1. Open an elevated Command Prompt again
    Press Windows + X and select Terminal Admin.
  2. Run DISM to repair the component store
    Type:
    DISM /Online /Cleanup-Image /RestoreHealth
    This operation takes 15 to 30 minutes. Do not close the window.
  3. Run SFC to repair system files
    After DISM completes, type:
    sfc /scannow
    Let the scan finish. SFC will replace any corrupted or missing protected system files.
  4. Restart your PC
    After SFC completes, restart. Check for updates again in Settings > Windows Update.

Step 4: Manually Download and Install the Failed KB

  1. Find the KB number
    In Settings > Windows Update > Update history, locate the failed update. Note the KB number, for example KB5034441.
  2. Go to the Microsoft Update Catalog
    Open a browser and go to catalog.update.microsoft.com. Search for the KB number.
  3. Download the correct version
    Select the file that matches your system architecture x64 for most modern PCs. Click Download and save the .msu file to your desktop.
  4. Install the update manually
    Double-click the .msu file and follow the prompts. Restart your PC when prompted. If the installation succeeds, the update will no longer appear as failed on future scans.

ADVERTISEMENT

If the Failed KB Still Appears After the Main Fixes

The KB is blocked by a third-party antivirus

Some security suites lock system file access during an update. Temporarily disable real-time protection in your antivirus software, attempt the update through Settings > Windows Update, and re-enable protection immediately afterward. If the update succeeds, add an exclusion for the Windows Update process or contact your antivirus vendor for guidance.

The update requires a specific prerequisite

Some cumulative updates depend on a previous servicing stack update or a specific .NET Framework version. In Settings > Windows Update > Advanced options > Optional updates, look for any pending servicing stack updates or driver updates. Install all optional updates, restart, and then retry the failed KB.

The update is superseded by a newer KB

Microsoft sometimes releases a new cumulative update that replaces an older one. If the failed KB is older than the current month, check whether a newer cumulative update is available. Install the newer update first; it may include the fixes from the older KB and remove the failed entry from the update history.

Manual Reset vs Troubleshooter: When to Use Each Method

Item Windows Update Troubleshooter Manual Component Reset
Speed 2-5 minutes 10-20 minutes
Scope Detects service states, cache corruption, and proxy misconfiguration Renames and rebuilds the full SoftwareDistribution and Catroot2 folders
Best for First attempt when the loop just started Recurring failures after the troubleshooter has already been run
Risk Low no manual commands required Low but requires an elevated Command Prompt

Use the troubleshooter first because it is faster and safer. If the same KB still fails after running it, proceed to the manual reset to guarantee that all cached files are removed.

You now have a clear sequence of actions to stop the same failed KB from reappearing on every Windows Update scan. Start with the built-in troubleshooter, then reset the update components manually, repair system files with DISM and SFC, and if needed, download the update directly from the Microsoft Update Catalog. As an advanced tip, you can create a batch file containing the net stop, rename, and net start commands from Step 2 to automate the reset process for future update issues without retyping each command.

ADVERTISEMENT