There is a special frustration reserved for a driver update that fails, gets offered again tomorrow, fails again, and repeats forever. Windows Update is not being stubborn to annoy you — it genuinely believes the driver applies to your hardware, and it will keep trying until something changes. Your job is to change something: fix the real reason the install fails, install the right driver yourself, or tell Windows Update to stop offering the package.

This guide covers the full loop-breaking playbook. If you are dealing with one specific error code on a single driver, the 0x800f020b walkthrough is the targeted companion. Here we handle the repeating pattern itself.

Before diving in, calibrate your expectations about what “fixed” looks like. For a driver your hardware does not need, “fixed” means Windows Update stops offering it \u2014 the hide-the-update ending is a complete victory, not a compromise. For a driver your hardware genuinely needs, “fixed” means the manufacturer’s version installed and working. Only the third case \u2014 a needed driver that will not install from any source \u2014 is a real problem, and it is the rarest. Most people stuck in this loop are fighting case one while assuming case three.

Why this happens

  • Version conflict with manufacturer drivers: Your laptop maker’s utility installed a newer driver; Windows Update’s older package fails the downgrade check every time.
  • Hardware mismatch in the catalog: Windows Update misidentifies a hardware variant and offers a driver the installer rejects — repeatedly, since the misidentification persists.
  • Corrupt cached package: The same damaged download is reused for every attempt until the cache is cleared.
  • Disconnected or removed devices: Drivers for printers, docks, or USB gear you no longer use fail because the device is gone — and keep being offered because the stale device record remains.
  • Blocked driver installation policy: Group Policy or MDM settings (common on work laptops) that forbid driver installs make every driver update fail identically.
  • Component store damage: A damaged servicing store fails driver payloads with varying codes, making the loop look random when the cause is singular.
  • Antivirus intercepting installs: Security software that kills the driver installer process produces the same failure on every attempt.
  • Insufficient staging space: A nearly full system drive fails driver staging repeatedly — the same space pressure behind cumulative updates failing every time .

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Map the loop — which drivers, which codes

  1. Open Settings, Windows Update, Update history, and list every failing driver update with its error code.
  2. Note the pattern: one driver failing means a package problem; all drivers failing means a pipeline problem.
  3. For single-driver failures, note the device name — you will need it for the manufacturer lookup in Fix 3.

Fix 2: Clear the update cache

Break the corrupt-package cycle first since it is fast.

  1. Open an elevated Command Prompt.
  2. Run net stop wuauserv, net stop bits, net stop cryptsvc.
  3. Delete the contents of C:\Windows\SoftwareDistribution.
  4. Restart the services, reboot, and check for updates. If the loop was a corrupt package, it ends here.

Fix 3: Get the driver from the manufacturer

  1. Identify your exact laptop model.
  2. Download the driver for the failing device from the manufacturer’s support site (Dell, HP, Lenovo, or the component maker).
  3. Install it and restart. A current manufacturer driver typically makes Windows Update withdraw its older offering permanently.

Fix 4: Reinstall the device cleanly through Device Manager

  1. Open Device Manager, find the device, right-click, and choose Uninstall device.
  2. If you have the manufacturer’s driver ready, tick “Attempt to remove the driver for this device” to clear the old one fully.
  3. Restart — Windows redetects the hardware.
  4. Install the manufacturer driver, then check Windows Update.

Fix 5: Hide the updates you do not need

  1. Run Microsoft’s wushowhide.diagcab troubleshooter and hide each persistently failing driver for a working device.
  2. Verify on the next update scan that they no longer appear.
  3. Revisit hidden updates only if the device develops issues — hiding is reversible.

Fix 6: Check for blocking policies and security interference

  1. Temporarily disable third-party antivirus and retry one failing driver.
  2. On Pro/Enterprise, check gpedit.msc under Windows Update policies for driver installation blocks.
  3. In Settings, Windows Update, Advanced options, verify driver-related toggles are at sensible defaults.

Fix 7: Repair the pipeline for system-wide failures

  1. If every driver fails, run DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow in an elevated Command Prompt.
  2. Free at least 20 GB on the system drive.
  3. Restart and retry. For persistent multi-driver loops, the deeper diagnostic pass in troubleshooting driver update failures walks through per-package isolation. Official component-reset documentation lives at the Microsoft Windows support hub .

Fix 8: Audit background programs that touch drivers

Some utilities reinstall or “update” drivers on their own schedule.

  1. Review installed programs for third-party driver updaters, system optimizers, and “gaming boosters” \u2014 uninstall any you do not actively trust.
  2. Check Task Scheduler for tasks with names referencing drivers or updates from unknown vendors, and disable them.
  3. In services.msc, look for non-Microsoft services with driver-related names set to Automatic; set them to Manual.
  4. Retry Windows Update with these quieted. If the loop breaks, you have found a program that was fighting Windows Update for control of your drivers.

Closing

The driver update loop ends when you stop letting Windows Update retry a doomed package and start deciding each driver’s fate deliberately. Diagnose the pattern, clear the cache, install the right driver from the manufacturer, audit the background programs fighting over your drivers, and hide what you do not need. A quiet Update history is not just cosmetic \u2014 it means your bandwidth and attention are no longer being spent on a fight Windows was never going to win by repetition.

Frequently asked questions

Why does Windows Update keep offering a driver that always fails?
Because Windows Update re-evaluates available drivers on every scan and keeps reaching the same conclusion: the package applies to your hardware. Until the underlying reason for the failure is fixed — or the update is hidden — the cycle repeats on every check, sometimes daily. Windows Update has no memory of past failures influencing future offers; each scan starts fresh.
Are failed driver updates harming my laptop?
No. A failed install leaves the existing working driver in place — Windows rolls the attempt back cleanly before anything changes. The harm is purely annoyance: notification spam, wasted download bandwidth, and the nagging feeling that something is broken when usually nothing is. Your hardware keeps running on its current driver exactly as before.
Should I let Windows Update manage my drivers at all?
For most users, yes for the basics — Windows Update drivers are tested and stable. But for graphics cards, laptop-specific hardware, and peripherals, the manufacturer’s drivers are usually better. A hybrid approach works well: let Windows handle the routine ones, get critical drivers from the manufacturer.
What if every driver update fails, not just one?
That points to a pipeline problem rather than a package problem: a corrupt update cache, a damaged component store, or a policy blocking driver installs. When every driver fails identically, stop troubleshooting individual drivers and repair the shared machinery instead — the cache clear and DISM repairs in this guide address exactly that pattern.