Lenovo laptops live in a slightly different driver world than generic Windows machines. Between the factory image, Lenovo Vantage, and Windows Update, you have three different systems that all think they’re in charge of your drivers — and they don’t always agree. The symptom is familiar: Windows Update downloads a driver, tries to install it, fails, and tries again tomorrow. Meanwhile Vantage sits there holding the correct, Lenovo-validated version of the same driver, wondering why you won’t just ask it.

This isn’t a Windows bug so much as a coordination problem. Lenovo validates drivers against specific BIOS versions and hardware revisions; Microsoft’s generic packages skip those checks and then fail Lenovo’s hardware-level ones. The fix is to put the right tool in charge of each driver category, clean up the conflicts, and stop the failing packages from retrying forever.

Why this happens

  • Generic vs. validated drivers: Windows Update offers generic drivers that fail Lenovo’s model-specific hardware checks.
  • Vantage already installed a newer version: The classic 0x80070103 — Vantage or the factory image is ahead of Windows Update’s catalog.
  • BIOS version dependencies: Lenovo drivers often require a minimum BIOS; Windows Update doesn’t check or install the BIOS first.
  • Dual management conflicts: Vantage and Windows Update fighting over the same device, each overwriting the other.
  • Corrupt DriverStore entries: Stale Lenovo OEM driver packages blocking new installs.
  • Lenovo System Update service issues: Vantage’s background service stalled, leaving driver state inconsistent.
  • Firmware-first ordering violated: Some drivers must install after their companion firmware — Windows Update doesn’t respect the ordering.

How to fix it

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

Fix 1: Check what Vantage says before touching Windows Update

Vantage knows your exact model, BIOS, and driver state. Its verdict outranks Windows Update’s for Lenovo hardware.

  1. Open Lenovo Vantage > System Update > Check for Updates.
  2. If Vantage offers drivers for the same devices Windows Update is failing on, install Vantage’s versions first.
  3. Pay special attention to BIOS, chipset, and Management Engine updates — these are prerequisites others depend on.
  4. Restart as prompted (BIOS updates need AC power).
  5. Recheck Windows Update afterward — many failures resolve once Vantage’s stack is current.
  6. For the general (non-Lenovo-specific) version of this problem, see our 24H2 driver update guide .

Fix 2: Identify the harmless failures (0x80070103)

On Lenovos, the most common “failure” isn’t a failure at all — it’s Windows Update offering an older driver than Vantage already installed.

  1. In Settings > Windows Update > Update history, find the failed driver and its code.
  2. 0x80070103 = newer driver already present. Verify in Device Manager > device Properties > Driver tab.
  3. If your driver date is newer than the offered one, this is working-as-designed.
  4. Hide the update with Microsoft’s “Show or hide updates” troubleshooter so it stops retrying.
  5. Don’t “fix” this by downgrading — the newer Vantage driver is the one you want.

Fix 3: Update the BIOS to unlock dependent drivers

This is the Lenovo-specific step most guides miss. Lenovo ties driver packages to minimum BIOS versions, and Windows Update neither knows nor cares.

  1. Check your BIOS version: in Vantage under Device Settings, or run wmic bios get smbiosbiosversion in Command Prompt.
  2. Look up your model on Lenovo support and compare with the latest BIOS.
  3. Install the BIOS update via Vantage (preferred) — AC adapter plugged in, battery charged, don’t interrupt.
  4. After the BIOS update completes and the system restarts, retry the failing driver updates.
  5. Thunderbolt, power management, and thermal drivers are the most BIOS-sensitive on ThinkPad and Legion models.

Fix 4: Clean the DriverStore of stale Lenovo packages

Old OEM driver packages accumulate in the DriverStore and can block new installs, especially after major Windows upgrades.

  1. Back up working drivers first — see our driver backup guide .
  2. Open Command Prompt as administrator and run pnputil /enum-drivers.
  3. Look for multiple versions of the same Lenovo driver (e.g., several oem*.inf entries for the trackpad).
  4. Remove obsolete ones with pnputil /delete-driver oemXX.inf /uninstall — only for drivers you can positively identify as superseded.
  5. Restart and let Windows Update retry with a clean store.
  6. When in doubt, don’t delete — a wrong removal is worse than a stale entry.

Fix 5: Repair Vantage’s update service

If Vantage itself shows errors or its System Update hangs, its background service needs attention.

  1. Press Win + R, type services.msc, and find Lenovo Vantage Service (or ImController service).
  2. Set startup to Automatic and restart the service.
  3. Open Vantage and retry System Update.
  4. If Vantage is damaged, uninstall it via Settings > Apps, reinstall from the Microsoft Store, and retry.
  5. Also check Lenovo System Update (the separate enterprise tool) isn’t running concurrently and conflicting.

Fix 6: Install problem drivers manually in the right order

When automation fails, manual installation with correct ordering succeeds. Firmware first, then chipset, then devices.

  1. From Lenovo support , download for your exact model: BIOS (if not done), chipset, then the specific failing driver.
  2. Install in that order, restarting between each.
  3. For graphics, prefer Intel, NVIDIA, or AMD direct downloads over Windows Update’s versions.
  4. After manual installation, Windows Update should recognize the driver as current.
  5. Hide the Windows Update package if it still offers the older version.

Fix 7: Set a single driver authority going forward

Prevent recurrence by ending the turf war between updaters.

  1. In Vantage settings, enable automatic driver/BIOS updates — make Vantage the authority for system drivers.
  2. In Settings > Windows Update > Advanced options, you can leave driver updates on for non-Lenovo components, but hide any that conflict.
  3. Don’t run third-party “driver updater” tools — they install unvalidated packages that trigger exactly these failures.
  4. Check Vantage monthly; check Windows Update’s optional drivers only when a specific device misbehaves.
  5. If driver failures coincide with broader update breakage, our update service repair guide covers the underlying pipeline.

Closing

Lenovo driver updates fail when the wrong tool is in charge. Give Lenovo Vantage authority over Lenovo hardware — BIOS, chipset, power, and model-specific drivers — keep the BIOS current so dependent drivers can install, and hide the generic Windows Update packages that can’t pass Lenovo’s hardware checks. One authority per device category, and the failure loop stops.

Frequently asked questions

Why do driver updates fail more often on Lenovo laptops?
Lenovo ships model-specific drivers validated against particular BIOS versions, thermal designs, and hardware revisions. Windows Update’s generic driver packages don’t account for these dependencies, so they fail hardware checks or conflict with Lenovo’s own driver stack. Using Lenovo Vantage as the primary driver source avoids most of these mismatches.
Should I let both Windows Update and Vantage install drivers?
It’s better to pick one primary source to avoid conflicts. Let Lenovo Vantage handle system drivers (chipset, BIOS, power, hotkeys, trackpad) and use Windows Update for everything else. Running both aggressively can cause version ping-pong, where each tool overwrites the other’s driver.
A driver update failed with 0x80070103. Is that bad?
No — 0x80070103 means a newer driver is already installed, which is common on Lenovos because Vantage and the factory image ship newer drivers than Windows Update offers. The failure is Windows correctly refusing a downgrade. Hide the update and move on.
Can a failed driver update break my working driver?
Almost never. Windows stages the new driver before swapping it in, and if staging or verification fails, the current driver stays untouched. Your Wi-Fi, graphics, or audio keeps working on the existing driver exactly as before the failed attempt.