Resolve Install Error - 0x80070103 Windows 11 Pro

Anonymous
2023-02-16T00:38:19+00:00

***UPDATE, I DID NOTHING AND TONIGHT MY COMPUTER NO LONGER SHOWS THESE ERRORS. MICROSOFT MUST HAVE FIXED IT***

Please help me to resolve this matter.

The troubleshooting steps I see listed do not work with an updated current Surface Laptop 4.

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
Reported
Anonymous
2023-02-17T18:57:53+00:00

Thank you to everyone for reporting this problem and providing feedback.

I am pleased to report that the Windows Update team at Microsoft was able to resolve this problem on 2/16/2023, at around 10:30am PST.

If you are still experiencing this problem, please report your issue to our engineering team via the Feedback Hub.

0 comments

99 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-02-16T15:41:10+00:00

    Looks like Microsoft fixed the problem this morning they are gone

    I wouldn't be so eager to say the issue is resolved. For me, it usually came off as the issue was fixed, but then suddenly the driver updates will just happen again.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-16T15:41:06+00:00

    Has not been fixed on mine yet. I am running a MSI with windows 11.....have kept it totally up to date otherwise.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-02-16T15:30:36+00:00

    Looks like Microsoft fixed the problem this morning they are gone

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-02-16T15:24:57+00:00

    You aren`t the only one waiting. I just spent 3 hours of my life trouble shooting this on my own laptop. Windows update keeps showing failed updates for drivers that were already sucessfully installed. This mess all started with the Windows KB5022845, KB5022497 as well as KB890930 updates on February 15th. Happy belated Valentines gift from Microsoft. Time for them to own up and fix the mess they caused.

    Was this answer helpful?

    0 comments