Driver updates failing in Windows Update is a special kind of frustration: the OS patches install fine, but the driver packages fail, retry, and fail again — sometimes for months. The loop persists because Windows keeps offering the same package, and the same package keeps hitting the same wall.

The key insight is that Windows Update is often the wrong delivery vehicle for the driver in question. Manufacturer drivers — from Dell, HP, Lenovo, Intel, NVIDIA, AMD — are newer, better matched to your hardware, and install through their own installers that handle the edge cases Windows Update chokes on. The sequence below first tries to fix the Windows Update path, then shows you when to abandon it for the manufacturer’s package. The post-24H2 driver failure guide covers the version of this problem tied to the 24H2 upgrade.

Why this happens

  • Hardware ID mismatch: The offered driver does not quite match your hardware revision.
  • Driver signature issues: Signature validation fails on the package.
  • Locked driver files: The currently loaded driver cannot be replaced while in use.
  • Corrupted driver cache: Damaged staged files fail verification.
  • Manufacturer driver newer: Your manually installed driver is newer than the offered one, confusing the installer.
  • Pending restart state: A previous install left the driver stack in limbo.
  • Antivirus blocking: Security software intercepting the driver installation.
  • Insufficient permissions: The installer lacking rights to write to the driver store.

How to fix it

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

Fix 1: Identify the failing driver

You cannot fix what you have not named.

  1. Open Settings > Windows Update > Update history and find the failed driver update — note its exact name.
  2. Open Device Manager and locate the corresponding device.
  3. Check the device’s Driver tab: note the current version and date.
  4. If the device shows a warning icon, the failed install left partial state — uninstall the device (keeping the driver) and restart first.
  5. With the driver named, you can now target the fix.

Fix 2: Install the manufacturer’s driver directly

This resolves most cases — the manufacturer’s installer handles what Windows Update cannot. Intel’s driver detection tool automates this for Intel components.

  1. Go to your laptop manufacturer’s support site (or the component vendor: NVIDIA, AMD, Intel, Realtek).
  2. Download the latest driver for your exact model and the specific device.
  3. Run the manufacturer’s installer — use its clean-install option if offered.
  4. Restart the laptop.
  5. Check Windows Update: with the current driver installed, the failing update usually disappears from the queue.

Fix 3: Clear the driver download cache

If you want the Windows Update path to work, clear its staging area.

  1. Open an elevated Command Prompt.
  2. Run net stop wuauserv and net stop bits.
  3. Delete the contents of C:\Windows\SoftwareDistribution\Download (leave the folder itself).
  4. Run net start wuauserv and net start bits.
  5. Check for updates — the driver downloads fresh.

Fix 4: Install in Safe Mode or clean boot

A locked driver file cannot be replaced while the driver is loaded.

  1. Boot into Safe Mode (Settings > Recovery > Advanced startup, or via msconfig).
  2. In Safe Mode, open Device Manager and uninstall the problematic device, checking delete the driver software if the option appears.
  3. Restart normally — Windows loads a basic driver.
  4. Now install the manufacturer’s driver from Fix 2 onto the clean slate.
  5. Restart once more and verify in Device Manager.

Fix 5: Hide the problematic update

When the driver works fine and you simply want the loop to stop, hide the update. Microsoft documents this on the Windows support hub .

  1. Download Microsoft’s show/hide updates troubleshooter package (wushowhide).
  2. Run it and choose Hide updates.
  3. Select the failing driver update from the list.
  4. Windows Update stops offering it — the loop ends.
  5. Revisit in a few months; a newer driver version may install cleanly.

Fix 6: Check for signature and permission issues

Deeper causes for drivers that fail even from the manufacturer’s installer.

  1. Open an elevated Command Prompt and run sfc /scannow.
  2. Check that Secure Boot settings have not changed unexpectedly (driver signature enforcement ties into this).
  3. Ensure you are installing as an administrator — driver installation requires elevation.
  4. Temporarily disable third-party antivirus during the install.
  5. Retry the manufacturer installer with these blockers removed.

Fix 7: Reset the update components fully

The nuclear option for the Windows Update path — full component reset. If driver updates keep failing even on 24H2 , this reset is the common denominator fix.

  1. Open an elevated Command Prompt.
  2. Stop all four services: wuauserv, bits, cryptsvc, msiserver.
  3. Rename both SoftwareDistribution and catroot2.
  4. Restart all four services and reboot.
  5. Check for updates — the driver queue rebuilds from scratch.

Fix 8: Reinstall the device cleanly

When a specific device’s driver will not update by any path, remove the device entirely and let Windows rediscover it.

  1. In Device Manager, right-click the device and choose Uninstall device, checking delete the driver software if offered.
  2. Shut down (not restart) and, for USB devices, unplug and replug the hardware.
  3. Power on — Windows detects the device and installs its inbox driver.
  4. Install the manufacturer’s latest driver on top of the clean detection.
  5. Verify in Windows Update that the failing driver entry is gone.

Closing

Failing driver updates in Windows Update are a delivery problem far more often than a driver problem — the package is usually fine, but Windows Update’s installer cannot handle your specific hardware state. The manufacturer’s installer can, which is why Fix 2 ends the cycle for most people. And remember the philosophical point: a driver that works does not need updating. If the hardware is healthy and the manufacturer has nothing newer worth installing, hiding the update is a legitimate, stable resolution — not a workaround.

Frequently asked questions

Why do driver updates fail when Windows updates succeed?
Driver updates go through a different validation path than OS updates. They must match your exact hardware ID, pass driver signature checks, and install without conflicting with the currently loaded driver. Any mismatch — a wrong hardware revision, a signature problem, or a locked driver file — fails the driver update while OS patches sail through.
Should I even install driver updates from Windows Update?
For most users, yes — they are tested and safe. But they are optional in the truest sense: if your hardware works, you do not need them. The best practice is to get critical drivers (GPU, chipset, Wi-Fi) from the manufacturer and let Windows Update handle the rest. If a Windows Update driver keeps failing, installing the manufacturer’s version usually ends the cycle.
Can a failing driver update break my working driver?
Rarely. Failed driver updates roll back to the previous driver, so your hardware keeps working with the old version. The risk case is a partially installed driver, which Device Manager usually flags with a warning icon. If you see that, uninstall the device and let Windows reinstall the last known-good driver.
Why does the same driver update reappear after failing?
Because Windows Update considers it still needed — the failed install did not register as completed, so the update stays in the queue and retries. This is the loop you are seeing. Breaking it means either installing the driver successfully from another source (which satisfies the requirement) or hiding the update so Windows stops offering it.