Windows: Update installation errors (Feb. 2023)

Windows[German]Windows 11 users reported an "update installation jam" on Microsoft Answers – tens of updates were listed, but could not be installed. Some received the installation error 0x80070103. This error seems to have been corrected by Microsoft on its update servers. In addition, Windows Server 2012 R2 users are receiving update installation error 0x800F0922. Here is an overview of these issues.


Advertising

Windows 11 update installation error 0x80070103

Barb Bowman alerted me the other night on Twitter (thx) about an exploding thead on the US Microsoft Answers forum where Windows 11 users are complaining about updates not installing. One user is asking Microsoft to fix the following installation error:Windows 11: Windows Update meltdown (Feb. 2023)

Resolve Install Error – 0x80070103 Windows 11 Pro

Please help me to resolve this matter.

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

On his Surface Laptop 4, a larger list of updates showed up, all of which threw installation error 0x80070103 and did not install. The thread, dated February 17, 2023, has over 4000 views and 8 pages so far – so it's hitting a lot of Windows 11 users – even on desktop systems.

The error code 0x80070103 stands for ERROR_NO_MORE_ITEMS (No more data is available.), so it's an indication that the update loop is still looking for data for the updates, but it can't find it. The usual troubleshooting hints that Microsoft offers in Windows Update via hyperlinks do not lead any further.

On Twitter, a user pointed out that users are increasingly complaining about the error 0x80070103 with Microsoft Update. Microsoft employee ariaupdated wrote in a reply that the error is known and that they are working on a fix. Is anyone from the readership affected? In this case you should be patient – the thread creator from MS-Answers writes that the error has fixed itself "automatically". Possibly Microsoft has fixed it.


Advertising

Install error 0x800F0922 with KB5022899

On February 14, 2023, update KB5022899 (Monthly Rollup for Windows 8.1 and Windows Server 2012 R2) was also released. During my installation tests on Windows 8.1, I received installation error 0x800F0922 on various packages. Have attributed this to expired support, but this is probably not true. In the comments to my German blog post Microsoft Security Update Summary (14. Februar 2023), user Liton confirms the error for Windows Server 2012 R2:

I can also confirm the problem with KB5022899:
With kb5022899 on a bare metal system running Windows 2012 R2 Essentials, I keep getting error 0x800F0922.
No chance to install the update. It goes up to 96% and then a rollback occurs.

In the Patch Tuesday megathread (Feb 14, 2023) on reddit.com, error 0x800F0922 is mentioned for update KB5022899, but with a reference to my German blog post. The error code is an indication of problems with the download (not enough memory, no connection to the update server, etc.). EaseUS lists some reasons and solutions to fix it here.Currently, I don't have Windows Server 2012 R2 to test on. Is anyone from the readership affected by the bug?

Addendum: See my follow up post Windows Server 20212 R2 (Essentials): Feb. 2023 updates drops install error 0x800F0922 for further details.

Similar articles:
Microsoft Security Update Summary (February 14, 2023)
Patchday: Windows 10 Updates (February 14, 2023)
Patchday: Windows 11/Server 2022 Updates (February 14, 2023)
Windows 7/Server 2008 R2; Server 2012 R2: Updates (February 14, 2023)
Patchday: Microsoft Office Updates (February 14, 2023)
Exchange Server Security Updates (February 14, 2023)

Windows Server 2022: February 2023 Patchday and the ESXi VM Secure Boot Issue
February 2023 Patchday: EWS problems after Exchange Server security update
Microsoft's February 2023 Patchday: Incorrect updates in WSUS, Exchange and Windows


Cookies helps to fund this blog: Cookie settings
Advertising


##1

This entry was posted in issue, Update, Windows and tagged , , . Bookmark the permalink.

4 Responses to Windows: Update installation errors (Feb. 2023)

  1. broland says:

    I am also having the same problem installing KB5022899 on a Windows Server 2012R2 Essentials physical server. Scouring the CBS.log file says the problem is the Extended Support Update check:

    Installer name: [38]"Extended Security Updates AI installer"
    2023-02-16 18:33:26, Info                  CSI    0000005c Performing 1 operations; 1 are not lock/unlock and follow:
      (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:871196115f42d90134000000b4019001} pathid: {l:16 b:871196115f42d90135000000b4019001} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.3.9600.20821_none_59d19e7ff626dfcd" pid: 1b4 starttime: 133210638955739993 (0x01d9425ecf427b59)
    2023-02-16 18:33:26, Info                  CSI    00000001 ESU: Product = 50 (0x00000032).
    2023-02-16 18:33:26, Info                  CSI    00000002 ESU: Pre IMDS checks failed, Not Eligible:HRESULT_FROM_WIN32(1605)
    2023-02-16 18:33:26, Info                  CSI    0000005d Performing 1 operations; 1 are not lock/unlock and follow:
      (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:aa379d115f42d90136000000b4019001} pathid: {l:16 b:aa379d115f42d90137000000b4019001} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.3.9600.16384_none_cd3183f2deb856d2" pid: 1b4 starttime: 133210638955739993 (0x01d9425ecf427b59)
    2023-02-16 18:33:26, Error      [0x01805c] CSI    0000005e (F) Failed execution of queue item Installer: Extended Security Updates AI installer ({4e9a75dd-0792-460c-a238-3f4130c39369}) with HRESULT HRESULT_FROM_WIN32(1605).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
    2023-02-16 18:33:27, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
  2. JP says:

    Same issue on my Windows 10 22H2 (not just Windows 11). I hid the drivers that gave this fault code with wushowhide.diagcab and they never showed up again.

Leave a Reply

Your email address will not be published. Required fields are marked *