There is a special kind of frustration reserved for driver updates that fail in Windows Update day after day. The same Realtek audio driver, the same Intel graphics driver, the same error code — install, fail, retry, fail. Meanwhile your hardware works fine, which makes the whole thing feel pointless. But ignoring it is not ideal either, because a driver that cannot update is often a driver with a deeper conflict underneath.

The pattern is almost always the same: Windows Update downloads a driver, the installer hits something it does not expect — a newer version already present, a locked file, a corrupted driver store — and the whole thing rolls back. This guide breaks down the handful of causes behind repeat driver update failures and gives you a clear repair sequence, from the two-minute checks to the deeper driver-store cleanup that actually ends the loop.

Why this happens

  • A newer driver is already installed: Windows Update’s driver catalog lags behind manufacturers. If your OEM utility already installed a newer driver, the older Windows Update version fails its version check and aborts the install.
  • Corrupted driver store: Windows keeps every driver package in the driver store. If an entry there is damaged or partially removed, new installs of that driver fail until the store entry is cleaned up.
  • Third-party driver updaters interfering: Tools that aggressively manage drivers can replace files mid-install or roll versions back, which makes Windows Update’s installer fail with access or version errors.
  • Pending device restart: Some driver installs stage changes that only complete after a restart. If the restart never happens, the next attempt collides with the staged files and fails.
  • Corrupted update cache: The downloaded driver package itself may be incomplete. Windows Update retries the same broken file instead of re-downloading it, so the failure repeats identically.
  • Hardware ID mismatch: Occasionally Windows Update offers a driver whose hardware ID does not quite match your device revision. The installer correctly refuses it, but Windows Update keeps offering it anyway.
  • Antivirus blocking driver installation: Overzealous security software can quarantine driver installer components or block the kernel-mode driver load, turning a routine update into a failed install.

How to fix it

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

Fix 1: Identify exactly which driver is failing

Guessing wastes time. Windows Update history names the exact driver and version that failed, and Device Manager shows the version currently installed. Comparing the two tells you immediately whether you are fighting a version conflict or a genuine install problem.

  1. Open Settings, go to Windows Update, then Update history.
  2. Expand the failed driver entry and note its name, version, and error code.
  3. Open Device Manager, find the device, and check its installed driver version on the Driver tab.
  4. If the installed version is equal or newer, you can safely hide the update; if it is older, continue with the fixes below.

Fix 2: Hide the bad update and install the driver manually

When Windows Update keeps pushing a driver your system does not want, the pragmatic move is to block that specific update and get the driver from the source. Microsoft provides a Show or Hide Updates troubleshooter for exactly this, and your manufacturer’s support page almost always has a newer driver. For Dell owners, Dell’s official support site lets you enter your service tag and download the exact tested driver for your machine. When the failing item is a bundled driver package rather than a device driver, the walkthrough for driver updates failing inside Windows Update covers that specific variant.

  1. Download the correct driver from your laptop manufacturer’s support site.
  2. Install it following the manufacturer’s instructions and restart.
  3. Use the Show or Hide Updates troubleshooter to hide the failing Windows Update driver entry.
  4. Check Windows Update to confirm the failed entry no longer appears.

Fix 3: Clean the driver store entry for the failing device

A damaged driver store entry will defeat every install attempt until it is removed. The pnputil tool lets you enumerate and delete stale driver packages safely, forcing Windows to stage a completely fresh copy on the next attempt.

  1. Open Command Prompt as administrator.
  2. Run pnputil /enum-drivers and find the .inf name for the failing driver.
  3. Run pnputil /delete-driver oemXX.inf /uninstall, replacing oemXX.inf with the actual name.
  4. Restart the laptop, then check Windows Update to let it stage a fresh driver copy.

Fix 4: Reset the Windows Update components

When the failure is in the download or staging pipeline rather than the driver itself, resetting the update components clears the whole path. This stops the services, clears the SoftwareDistribution and catroot2 folders, and re-registers the update DLLs — the standard deep clean for stubborn update failures. Cumulative updates sometimes carry driver payloads, so a cumulative update that will not install can share this exact root cause.

  1. Open Command Prompt as administrator.
  2. Stop the services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old.
  4. Restart all four services with net start, then check for updates again.

Fix 5: Update the driver through Device Manager

Device Manager uses a slightly different install path than Windows Update, and it sometimes succeeds where the main update pipeline fails. It is worth trying before the heavier repairs, especially for network and audio drivers.

  1. Open Device Manager from the Start menu.
  2. Right-click the device and choose Update driver.
  3. Select Search automatically for drivers and let it complete.
  4. If it reports the best driver is already installed, the Windows Update entry was likely a version conflict you can ignore.

Fix 6: Check for blocking software and pending restarts

Before assuming system damage, rule out the simple blockers. A pending restart can hold a staged driver install hostage, and security software can silently block driver loading. Clearing both takes minutes and resolves a surprising share of repeat failures.

  1. Restart the laptop fully — not hibernate or sleep — to clear any staged installs.
  2. Temporarily disable third-party antivirus real-time protection.
  3. Retry the driver update from Windows Update.
  4. Re-enable your antivirus immediately after the test, whether or not the update succeeded.

Closing

Driver updates that fail on repeat are a loop, not a mystery: something structural — a version conflict, a damaged driver store entry, or a corrupted download — is defeating every attempt. Identify the exact driver, install it from the manufacturer when Windows Update will not cooperate, and clean the driver store when the conflict runs deeper. Do that, and the daily failure notifications stop for good.

Frequently asked questions

Why does the same driver update fail every day?
Windows Update retries failed updates on its normal schedule, so a driver that fails for a structural reason — a version conflict, a corrupted driver store entry, or a damaged download — will fail identically each time it retries. The loop only breaks when the underlying cause is fixed, which is why simply clicking Retry never helps. Identifying the driver and either updating it manually or cleaning its driver store entry ends the cycle.
Should I let Windows Update install drivers at all?
For most laptops, yes — Windows Update drivers are tested and stable. The exception is graphics drivers for gaming or creative work, where the manufacturer’s latest release is usually preferable. If a specific driver update keeps failing, installing that driver directly from the laptop or component manufacturer’s site is the recommended workaround, and you can hide the Windows Update version afterward.
Can a failing driver update damage my laptop?
Almost never. Failed driver installs roll back to the previous working driver, so your hardware keeps working with the old version. The risk is missing out on bug fixes and, rarely, accumulating a corrupted driver store entry that causes future installs to fail. The fixes in this guide clean that up safely without affecting your files or settings.
What does error 0x80070002 mean for driver updates?
Error 0x80070002 means the system cannot find a file the installer expected — usually a corrupted or incomplete download in the update cache. For driver updates specifically, resetting the Windows Update components and clearing the SoftwareDistribution folder resolves it in most cases. If it persists, the driver store entry for that device is the next place to look.