How to handle Install error - 0x80070103

Anonymous
2022-12-06T05:53:11+00:00

How to handle Install error - 0x80070103

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2023-03-14T17:21:42+00:00

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,

Was this answer helpful?

1100+ people found this answer helpful.
0 comments

164 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-02-16T05:51:16+00:00

    Yes Josh, you were correct in assuming that it was just a bug. There is this other user "JeffInDFW" who also suggested the same thing and it did work (atleast for me).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-16T05:49:50+00:00

    Thank you so much JeffInDFW. Your approach worked.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-02-16T05:42:27+00:00

    Forget the complicated stuff posted. HERE is what actually works, (no joke).

    Simply scroll down in the Windows Updates, and: 1. click on pause updates for 1 week. 2. resume updates again

    Thanks a million! This finally fixed it for me.

    I ran the Windows Update Troubleshooter first (from Windows Settings | System | Troubleshoot | Other troubleshooters). It took a very long time to complete, but it found (and fixed) a problem with WaaSMedicService. After that, I went to see in Windows Update if the errors had gone away, but all of them were still there, and clicking on the button to retry to install them still didn't make them go away. Next, I ran sfc /scannow just to be sure that system files were not corrupt, but this didn't report any integrity violations. Next, I rebooted, and I went to see in Windows Update again, but the errors were still there, same as before. (They all appeared as 0x80070103 in Windows Update, but I can see that they all appear as 0x8024200B when I run perfmon /rel and select the right column on the graph before clicking on View technical details for each failed update.) But anyway. They're gone now. Until the next time.😄

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-02-16T05:42:26+00:00

    Yes, you maybe correct as well. We can't say for sure, but the main concern is (based on my limited knowledge), these incomplete/pending updates may leave our system vulerable which (is likely/ but hopefully should not) might be a security issue.

    Lets just hope that Microsoft tends to this at the earliest possible, becasue based on this thread of communication it seems that many people have started facing this issue starting yesterday or today, and surprisingly enough Windows rolled out their regular Quality Update yesterday, which I believe many of us have installed (including me), and (just a hunch) but it might have led to this issue.

    Was this answer helpful?

    0 comments