Ask about failing driver updates in any PC community and you will get the same story: cumulative updates install fine, but one driver — the GPU, the Wi-Fi card, the fingerprint reader — fails in Windows Update every time, sometimes with a hex code, sometimes with nothing at all. The threads all converge on the same diagnosis, and it is worth understanding: Windows Update is a mediocre driver delivery service wearing a good OS-update uniform.

Driver packages fail for reasons OS updates never encounter: hardware-ID mismatches, vendor packaging errors, and signature checks against your specific machine. The fix is not to fight Windows Update harder but to route around it. This guide follows the community-tested order: identify the failing driver, stop Windows Update from mangling it, and install the correct driver from the source that actually built it.

Understanding why vendor packages fail through Windows Update makes the community advice click. Hardware vendors submit drivers to Microsoft, which repackages them for the Update catalog — and that repackaging is where things break: wrong hardware IDs, stale versions, or signatures that do not match your configuration. The vendor’s own installer skips that entire pipeline and talks to your hardware directly. That is the whole secret behind the forum consensus. It is not superstition; it is supply-chain mechanics.

Why this happens

  • The driver package does not match your hardware revision. A vendor submits a driver whose hardware IDs do not cover your specific card revision, and the installer rejects it.
  • Windows Update offers an older driver than you have. Version comparison fails and the install aborts — or worse, it downgrades a working driver.
  • The vendor’s packaging is broken. Corrupted or misconfigured .inf packaging from the manufacturer fails Microsoft’s install checks.
  • A previous partial install left conflicting state. Half-installed driver files block every retry of the same package.
  • Signature or certification problems. The driver package’s signature does not validate on your machine’s configuration.
  • Concurrent installs from vendor utilities. GeForce Experience, Lenovo Vantage, or Dell SupportAssist installing the same driver simultaneously collides with Windows Update.
  • Metered or managed driver policies. Group policy or registry settings block driver installation while allowing OS updates.

How to fix it

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

Fix 1: Identify the exact failing driver

You cannot fix what you have not named.

  1. Open Settings > Windows Update > Update history and find the failed driver entry.
  2. Note the device name and any error code.
  3. Open Device Manager, find that device, and check its current driver version and date.
  4. If the device works fine right now, the update is optional — remember that before investing hours.

Fix 2: Pause driver delivery from Windows Update

Stop the bleeding before treating the wound.

  1. Open System Properties > Hardware > Device Installation Settings.
  2. Choose No, let me choose what to do / No to stop automatic driver replacement.
  3. In Settings > Windows Update > Advanced options, you can also pause updates briefly while you work.
  4. This prevents Windows Update from reinstalling the broken package while you fix things manually.

Fix 3: Hide the specific failing update

The official pressure valve for one bad package.

  1. Download the official wushowhide troubleshooter package from Microsoft’s support site.
  2. Run it, select Hide updates, and check the failing driver.
  3. Confirm it no longer appears in Windows Update.
  4. You can unhide it anytime; hiding is reversible and safe.

Fix 4: Install the driver from the manufacturer

The fix the community recommends because it works.

  1. Identify your exact hardware: GPU, Wi-Fi card, or device model.
  2. Get the driver from the vendor: NVIDIA , AMD , or the Intel DSA .
  3. For laptop-specific devices, prefer your laptop maker’s own support site over the generic package — Dell, HP, and Lenovo all publish model-specific drivers.
  4. Install with the clean-install option where offered, then restart.

Fix 5: Clean out the old driver state first

When the manufacturer’s installer also fails, stale driver state is blocking it.

  1. In Device Manager, uninstall the device with Attempt to remove the driver checked.
  2. Run Display Driver Uninstaller (DDU) from Safe Mode for GPU drivers that refuse to clear.
  3. Restart and install the manufacturer driver on the clean slate.
  4. Verify in Device Manager that the new version and date are active.

Fix 6: Reset Windows Update components

For cases where the failure corrupted the update pipeline itself.

  1. Stop wuauserv, cryptSvc, bits, and msiserver in an elevated Command Prompt.
  2. Rename SoftwareDistribution and catroot2.
  3. Restart the services.
  4. Check for updates — OS updates should flow normally with the bad driver hidden. Related: Windows Update service not running .

Fix 7: Check group policy and registry blocks

The last resort for machines where driver installs are policy-blocked.

  1. Run gpedit.msc and check Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update.
  2. Look for Do not include drivers with Windows Updates — note its state rather than flipping it blindly.
  3. In the registry, check HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate for driver-related values.
  4. Corporate or school machines may be managed — in that case, the IT admin owns this setting, not you. For the in-24H2 variant of this problem, see driver updates failing in 24H2 .

Fix 8: Install via Device Manager’s manual driver picker

When even the vendor installer balks, hand Windows the driver files directly.

  1. Download and extract the vendor driver package (use 7-Zip if it is an exe).
  2. In Device Manager, right-click the device > Update driver > Browse my computer.
  3. Choose Let me pick from a list, click Have Disk, and point at the extracted .inf.
  4. This bypasses both Windows Update and the vendor’s installer — the last mile of manual control.

Closing

Driver updates fail in Windows Update for vendor-side reasons that no amount of retrying will fix. The community wisdom is correct: identify the driver, hide the bad package, and install the manufacturer’s driver directly. Windows Update remains excellent at OS updates — just stop asking it to be your driver manager, and the failures stop with it.

Frequently asked questions

Why do driver updates fail when regular updates succeed?
Because driver packages come from hardware vendors through Microsoft’s pipeline, and they fail vendor-side applicability checks that OS updates never face. A driver whose hardware ID, version, or signature does not match your machine is rejected at install time while cumulative updates sail through.
Is it safe to ignore failing driver updates?
Often yes, if the hardware already works. A failing optional driver update for a device with no symptoms can be safely hidden. But failing drivers for your GPU, Wi-Fi, or chipset deserve attention, since they may carry stability or security fixes.
Why does Reddit recommend installing drivers manually?
Because the community has collectively learned that vendor-direct drivers bypass the exact failure point: Windows Update’s packaging and applicability checks. Thousands of threads converge on the same conclusion — the manufacturer’s installer succeeds where the WU package fails. The pattern repeats across thousands of threads: vendor installer succeeds, Windows Update package fails, every time.
Will hiding a driver update break anything?
No. Hiding only stops Windows Update from offering that specific version. Your current driver keeps working, and you can unhide it later or install a newer version manually whenever you choose. The wushowhide tool is Microsoft’s own utility, and unhiding is a one-click reversal.