Seeing a stubborn install error 0x80070103 during Windows Update is one of those annoyances that feels urgent but usually has a simple explanation: Windows Update is repeatedly trying to apply a driver that’s already present, or it’s offering a “new” driver that isn’t actually a better match for the hardware. The fastest repairs are low-risk and often finish in minutes; deeper fixes only become necessary when Windows’ update components or the local driver state are truly corrupted. This guide pulls together a practical escalation path—fast wins first, then the repair tools and policies that stop the loop for good—using vendor and Microsoft guidance plus community troubleshooting playbooks.
Background
Windows Update can present driver offers in several ways: as an optional driver under “Optional updates,” as a driver bundled in a monthly quality update, or as a separate package pushed from the Microsoft Update Catalog. When the update client misinterprets a driver’s metadata (version, device match, provider string), it may attempt to install a driver that is already present or incompatible with the precise hardware revision. That leads to the familiar install error 0x80070103—
“The file is not a better match than the file that is already installed.” Microsoft has explicitly documented cases where duplicate driver offers were re-published and re-offered (for example, in February 2023), causing many otherwise healthy systems to log repeated 0x80070103 failures; the fix in those incidents often came from republishing the correct catalog entries rather than local changes on the device.
Why this matters
A looping driver offer blocks other updates and clutters Update History, compounding user anxiety. More critically, systemic update failures can conceal genuine servicing or disk errors that require prompt action. The good news: if the failing item is only an optional driver and your hardware is functioning normally, the safest path is to stop the repeated offer and let Windows finish the rest of its updates.
What causes 0x80070103? (Plain language)
- Duplicate-driver offer: Windows Update thinks it has a newer driver but the installed package is effectively the same. This is the single most common trigger.
- Version/metadata mismatch: The catalog shows a different version or provider string, so Windows tries to “upgrade” even though the device already has an appropriate driver.
- Incompatible or unnecessary driver: The driver in the catalog doesn't match your exact hardware revision or is irrelevant to your machine.
- Update cache corruption: Corrupt downloads or cached metadata in SoftwareDistribution/catroot2 can force repeated retries.
- Underlying disk / system-file issues: File system errors or component-store corruption occasionally manifest as failed driver installs. DISM/SFC or CHKDSK are the right tools when these are suspected.
Because many community incidents were caused by the catalog or vendor metadata rather than the device itself, a local install failure does not always mean your PC is broken—often it simply means Windows Update is confused.
Quick wins — fixes that usually work in minutes
Start here. These are low-risk, safe to try on production machines, and solve the majority of repeat-driver offers.
1. Run the Windows Update troubleshooter (fast, recommended first step)
- Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run.
- Follow the prompts and reboot even if the troubleshooter reports it “fixed” the issue—a reboot makes the client re-evaluate offerings. This is Microsoft’s recommended starting point.
2. Pause updates, then resume (simple nudge)
- Settings → Windows Update → Pause updates (short pause) → wait ~30–60 seconds → Resume updates.
- Pausing briefly forces Windows Update to rebuild its check cycle and often drops a repeated driver attempt. Community runbooks frequently list this as a practical “insider” tip when the same driver returns immediately.
3. Check Optional updates and skip the driver
- Settings → Windows Update → Advanced options → Optional updates.
- If the driver shows here as an optional item (for example a repeated HEWLETT‑PACKARD USB entry in many reports), don’t install it unless you need that specific fix. Skipping optional drivers prevents the loop while letting security/quality updates proceed.
4. Hide or block the specific driver update
- Microsoft’s old Show or Hide Updates tool (wushowhide.diagcab) still works in many environments and lets you hide a particular driver package. Note: Microsoft has deprecated and removed some older diagnostic pathways, and the tool’s availability can vary by Windows 11 build—if the tool is unavailable, use the Optional updates page or Group Policy instead.
Steps (when wushowhide is available):
- Download and run wushowhide.diagcab.
- Choose “Hide updates.”
- Pick the offending driver package and confirm.
- Reboot and re-check Windows Update.
If the GUI tool won’t run on your build, the Group Policy setting described later gives admins a deterministic alternative.
When the quick fixes don’t stop the loop — advanced repair steps
If the driver keeps reappearing after the quick tips, escalate to these deeper repairs. Proceed in order—each step increases the scope of change.
Step A — Confirm your Windows build
Run winver to capture your Windows version and OS build. Some servicing fixes and behavioral changes are build-specific; for example, Microsoft’s Quick Machine Recovery feature appears on Windows 11 24H2 build 26100.4700 or later and may change certain recovery flows, so knowing your build matters before taking larger steps.
Step B — Reset the Windows Update cache (SoftwareDistribution + catroot2)
This is the most effective fix for corrupted update caches and stuck offers.
Open an elevated Windows Terminal or Command Prompt and run the commands below, one line at a time:
- Stop the services:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
- Rename the cache folders (safer than deletion):
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
- Restart the services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
- Reboot and retry Windows Update.
Renaming preserves the old data for rollback. Community runbooks and Microsoft guidance both describe this sequence as standard practice for stubborn update loops.
Step C — Repair the image and system files (DISM + SFC)
If resets don’t help, the servicing store or protected system files may be damaged. Run these elevated commands, in this order:
- DISM /Online /Cleanup-Image /CheckHealth
- DISM /Online /Cleanup-Image /ScanHealth
- DISM /Online /Cleanup-Image /RestoreHealth
- sfc /scannow
Allow time—DISM may download replacement files and can take 10–30 minutes or more on slow drives. Reboot after completion and retry updates. This flow is Microsoft’s documented remediation path for component-store corruption.
Step D — Run CHKDSK if you suspect disk errors
Corrupt file systems or failing sectors can interrupt update commits. For a non-blocking scan:
If the scan reports errors and recommends a fix, plan downtime and run:
For a full physical-sector check (long):
If CHKDSK reports repeated failures,
back up critical data immediately and consider professional recovery—repairing a failing disk can worsen data loss.
Manual driver install: when it’s the right move
If the device is actually misbehaving (USB drops, Wi‑Fi disconnects, audio failures), installing the manufacturer driver manually is usually the correct action.
- Identify the exact device: Device Manager → device → Properties → Driver tab (provider, date, version).
- Download the driver from your OEM or the device vendor, matching model and Windows version. Avoid third‑party driver sites.
- Install with the vendor’s installer, or Device Manager → Update driver → Browse my computer for drivers → point to the downloaded driver files.
- Reboot and re-check Windows Update.
Vendor support utilities can simplify this:
- HP Support Assistant (HP systems)
- Dell Command | Update (Dell systems)
- Intel Driver & Support Assistant (Intel components)
Use those tools when available, but verify the vendor package is recent and meant for your exact hardware.
Blocking driver updates at scale (Group Policy / MDM)
For managed environments or admins who prefer deterministic behavior, Windows offers a policy to exclude driver packages from quality updates:
- Policy name: Do not include drivers with Windows Updates
- Registry value: ExcludeWUDriversInQualityUpdate under Software\Policies\Microsoft\Windows\WindowsUpdate
- Location in GPO: Computer Configuration → Administrative Templates → Windows Components → Windows Update → Do not include drivers with Windows Updates
Enabling this policy prevents Windows Update from delivering driver packages as part of the daily quality update cycle (it does not prevent drivers included in feature updates or those where the OS provides the driver). Use this when you want vendor toolchains (Dell/HP/Intel) to be the single source for drivers in your fleet.
The Show-or-Hide tool: status and alternatives
Microsoft’s classic wushowhide.diagcab remains useful but has been partially retired or is unreliable on some Windows 11 builds. Microsoft’s answers and community threads show mixed availability: in many cases the tool still works; in others it fails or is blocked on newer builds. If the tool does not run, use Optional updates, Device Installation Settings, or the Group Policy to block driver updates. When available, wushowhide remains the most targeted, non-invasive way to hide a single driver offer.
Flag: treat the tool as a legacy workaround—its availability is build-dependent.
New recovery options: Quick Machine Recovery
Microsoft introduced
Quick Machine Recovery (QMR) for Windows 11 to help devices recover from widespread boot failures by fetching remediations from Windows Update while in WinRE. QMR is available on Windows 11 24H2 build 26100.4700 or later and can be configured by IT admins; it is not a direct fix for 0x80070103, but it represents the kind of cloud-based remediation pathway Microsoft is building for future systemic failures. Knowing whether QMR is enabled on your machine helps in recovery planning for serious issues that might otherwise require image-level fixes.
A practical escalation checklist (safe → aggressive)
- Run Windows Update troubleshooter and reboot.
- Pause updates → Resume updates once, then check Optional updates.
- Hide the specific driver (wushowhide) or skip Optional driver installs.
- Reset update cache (rename SoftwareDistribution & catroot2), restart services, reboot.
- Run DISM /RestoreHealth followed by sfc /scannow, reboot.
- Run chkdsk if disk errors are suspected. Back up before deep disk work.
- Manually install the correct driver from the vendor if hardware is failing.
- For managed fleets, enable the policy to exclude drivers from Windows Update.
- If servicing remains broken, use Microsoft Update Catalog to install the package manually or perform an in‑place repair (mount ISO → setup.exe → Keep personal files and apps).
When to call a pro
- CHKDSK reports repeated sector repairs or disk SMART shows failures—risk of data loss demands professional imaging.
- Multiple update errors across different KBs or services won’t start—enterprise escalation or Microsoft support is warranted.
- Device instability continues after driver reinstall (random reboots, persistent I/O errors)—consider vendor support or an authorized repair shop.
Common misconceptions and cautions
- “If Windows Update reports a failed driver, the hardware must be broken.” Not true—most 0x80070103 reports reflect a driver metadata mismatch or duplicate offer, not hardware failure.
- “Delete SoftwareDistribution to fix everything.” Renaming is safer. Deleting can remove helpful logs; renaming lets Windows rebuild the folder while preserving the original for inspection.
- Show-or-Hide is universally supported. It isn’t—use it when available, but rely on Optional updates or Group Policy when it’s not.
Flag: some public reports and third-party articles claim persistent, long‑running Microsoft inability to fully resolve 0x80070103 in certain rare cases; these claims should be treated with caution and verified for your particular build and KBs before drawing conclusions.
Preventive checklist that actually helps
- Keep at least 20–30 GB free on C: before major feature updates (staging space matters).
- Use vendor update tools for device drivers when possible (HP Support Assistant, Dell Command | Update, Intel DSA).
- Monitor Optional updates and skip driver installs unless they fix a real problem.
- If you manage devices, pilot updates and use Group Policy / Windows Update for Business to control driver delivery.
- Keep Windows Update components healthy—reset the cache early if failures start piling up.
Short FAQs (practical answers)
- What is install error 0x80070103?
It means Windows Update attempted to install a driver that’s already installed (or not a better match). You can usually ignore it if the device works, hide the update, or install the correct driver manually.
- Is it safe to hide the failing update?
Yes—if the device functions correctly, hiding the update prevents the loop and lets other updates complete. Use wushowhide when available or block driver updates via Group Policy for managed systems.
- Should I run DISM and SFC?
Yes, if cache resets don’t help. DISM repairs the component store and SFC validates protected system files—together they fix many stubborn servicing errors.
- Where do I get drivers safely?
From your PC vendor or the device maker’s official site, or from the Microsoft Update Catalog for specific KB packages. Avoid third‑party “driver download” sites.
Conclusion
Install error 0x80070103 is rarely a sign that your PC is dying—more often it’s an update catalog or metadata mismatch, a duplicate offer from Windows Update, or a corrupt local cache. Start with the built-in troubleshooter, then pause and resume updates, skip or hide the offending driver, and only then move to cache resets, DISM/SFC repairs, CHKDSK, or manual driver installs. For administrators, the
Do not include drivers with Windows Updates policy provides a clean, reliable way to control driver delivery at scale. When disk checks show repeated faults or servicing commands fail to repair the component store, back up your data and escalate to professional support rather than continuing trial-and-error repairs. The stepwise sequence above resolves the majority of cases quickly while preserving system stability and data safety.
Source: Editorialge
Quick Solutions for Install Error - 0x80070103 Revealed!