![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi all, I am revisiting this thread to provide a more comprehensive view of this error. Much of this detail came from a Microsoft Technical Advisor who works closely with the product teams.
The error message 0x80070103 will appear when a device attempts to install a driver that is already present.
When the version of a driver reported by the device and the current version published in the Windows Update catalog are different, Windows Update offers the device the newer driver published in the catalog. If the customer attempts to install the re-offered driver they will see the 0x80070103 error.
Here is a recent example of this in the Community: Windows Update keeps telling me to install updates that are already - Microsoft Community
On Feb 15, Windows Update began re-offering drivers to devices which already had the driver installed. Many customers saw the duplicate drivers, attempted to install them, and saw the 0x80070103 error. The solution was Microsoft re-publishing the catalog. Nothing on the impacted devices could be done to “fix” the condition because nothing was “wrong” on the devices.
For this thread that began in December, it looks like that included some HP drivers. Those devices had version X, Windows Update got version Y from HP, and re-offered the driver to the device. It was actually the same version and thus the error. The solution for this set of customers would come when HP fixes the driver versioning and republish to Windows Update. Customers could not resolve this on their device, it could only be resolved by HP taking particular actions. The customer could suppress the event by “pausing” updates, but that is not solving it. It is only hiding the error temporarily.
There was a similar issue in February detailed here: Resolve Install Error - 0x80070103 Windows 11 Pro - Microsoft Community
Looking to the future, this may provide a general approach that can be used when this error pops up again due to publishing mistakes by RandomOEMName. Windows Update is the delivery mechanism for drivers from hundreds/thousands of companies, and Microsoft works with them to fix issues highlighted by this error. Since this is out of the control of customers to fix, the best approach is to report the error via the Feedback Hub and be patient as Microsoft works with the company and team who wrote the errant driver to correct the problem.
I hope this helps provide a deeper understanding of what causes this error and the best approach to resolve it.
Respectfully,