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 No 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 No comments

99 additional answers

Sort by: Newest
  1. Anonymous
    2023-02-16T22:36:16+00:00

    There is no way I am going to do that resolve on my own. Microsoft can send a fix.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-02-16T20:59:55+00:00

    Sort of relieved that I'm not the only one getting this "install error" with a bunch of drivers.

    Is anyone else's touchpad reeeeally sluggish? Like it takes a whole quarter-second to register any touches. Any short strokes just completely don't register at all because of this. I have a Lenovo ThinkPad X13s which runs on ARM. I have to resort to the little trackpoint just because of this.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-02-16T20:52:50+00:00

    Hi scrappyz_21, and all the users who replied to the post,

    Welcome to Microsoft Community.

    I'm Hahn and I'm here to help you with your concern.

    Recently, we have been receiving a large number of Surface as well as other laptop devices experiencing an inability to install updates, specifically reporting error code 0x80070103.

    I'm sorry you're having this experience.

    We have given feedback to the relevant team and hope to resolve this issue as soon as possible.

    Microsoft takes every question from its users very seriously.

    You can give feedback on such issues through the Feedback Hub. More feedback can better collect and troubleshoot problems.

    Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

    In addition, you can also try the following method, which may help.

    1. In the search box on the taskbar, type command prompt, then select Run as administratorfrom the list of options. Select Yes. Next, in the window that appears, type the following commands one at a time, including the spaces as shown. After you type each command, press Enter. Then let each command complete before you type the next command.
      net stop bits
      net stop wuauserv
      ren %systemroot%\softwaredistribution softwaredistribution.bak
      ren %systemroot%\system32\catroot2 catroot2.bak
      net start bits
      net start wuauserv
    2. After all these commands are completed, close the Command Prompt window and restart your computer.

    If there is anything not clear, please do not hesitate to let me know.

    Your Sincerely

    Hahn - MSFT | Microsoft Community Support Specialist

    Aha. Another poster said to also do this at the beginning:

    net stop cryptsvc

    I added that command after the "net stop wuauserv"

    And I'm happy to report, it worked for me. Rebooted, went back to Windows Update, clicked on the update button a couple of times, and all the long list of bogus pending updates disappeared.

    (Question: do I have to do a net start cryptsvc now? All seems to work without me doing that step, I think. Answer: Looks like no need. After rebooting, I did try that "net start cryptserv" command and the command prompt said the service had already been started.)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-02-16T20:32:46+00:00

    I confirm that set a pause for 1 week and check for update some time later (I waited about 15 min) has resolved this issue. Nothing else helped in my case, I also tried to hide 3 drivers which show this error, but wushowhide.diagcab tool didn't work. Lenovo Legion 5 (Ryzen 5 4600), Windows 11 Pro 22H2 22621.1265.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments