Windows Update Failure on January 9, 2024—KB5034129 (OS Build 20348.2227)

Question

Hi,

I have been encountering error: 0x80073701 on installing this KB. Please kindly advise based on logs.

Thanks

Steven

2 2008 5796 Handler *FAILED* [80073701] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\helper\osdeploymenthelper.cpp, line = 730

2024/01/10 08:30:01.1392731 2008 5796 Handler *FAILED* [80073701] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\installer\osinstaller.cpp, line = 1103

2024/01/10 08:30:01.1433846 2008 5796 Handler Install complete for update ID: 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1 Return code is 0x80073701. Requires Reboot:No

2024/01/10 08:30:01.1433867 2008 5796 Handler Enter deployment handler NotifyResult

2024/01/10 08:30:01.1435212 3132 984 Deployment Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Update 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1 failure delegate invoked.

2024/01/10 08:30:01.1435625 2008 5796 Handler Leave deployment handler NotifyResult

2024/01/10 08:30:01.1436432 2008 5796 Handler *FAILED* [80073701] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\installer\osinstaller.cpp, line = 339

2024/01/10 08:30:01.1436454 2008 5796 Handler *FAILED* [80073701] Leave deployment handler Install

2024/01/10 08:30:01.1439163 3132 5976 Deployment Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : NotifyClient (5976)(0) called for update id 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1, code = Update failed, percent complete = 100

2024/01/10 08:30:01.1439695 3132 5976 ComApi Deployment job proxy : deployment callback for top-level update 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1, reboot required = unspecified, commit required = No, mapped result = 0x80073701, unmapped result = 0x00000000

2024/01/10 08:30:01.1444587 3132 5976 ComApi Deployment callback complete for UpdateID = 287e4fd0-634d-4e23-b0f6-333c8c472a1a, callback code = 8, CallbackInfo cookie length = 0

2024/01/10 08:30:01.1500476 3132 2920 ComApi Deployment Job Proxy : Callback for inner update : 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1, top-level update 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1, reboot required = unspecified, commit required = No, callback info length = 0

2024/01/10 08:30:01.4410293 5352 8760 DownloadManager CloseUpdateInstallDirectory invoked for Update ID = 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1, serverID = 8B24B027-1DEE-BABB-9A95-3517DFB9C552, Update installation result = 0x80073701.

2024/01/10 08:30:01.7324492 5352 8760 DownloadManager CloseUpdateInstallDirectory successful for Update ID = 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1.

2024/01/10 08:30:01.7468682 5352 8760 DownloadManager Unlock the sandbox of update 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1 (session data: (null))

2024/01/10 08:30:01.7578177 3132 2920 Deployment Mutex will be closed. index = 0, HANDLE = 0000000000000834

2024/01/10 08:30:01.7578332 3132 2920 Deployment *FAILED* [80073701] Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Top level update id 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1, bundled update id 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1

2024/01/10 08:30:01.7578361 3132 2920 Deployment *FAILED* [80073701] Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Top level update id 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1

2024/01/10 08:30:01.7578393 3132 2920 Deployment Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Update 287e4fd0-634d-4e23-b0f6-333c8c472a1a.1 failure delegate invoked.

2024/01/10 08:30:02.0900910 5352 8760 Agent AddEventGroup: Adding non-pending event for update id 287E4FD0-634D-4E23-B0F6-333C8C472A1A.1

2024/01/10 08:30:02.0929561 3132 2920 Deployment Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Job complete delegate invoked.

2024/01/10 08:30:02.0929761 3132 2920 Deployment Deployment job Id 32F206F6-3D23-4CE6-8D0E-B5D6862F9265 : Ending deployment for updates, CallerId = MoUpdateOrchestrator, Exit code = 0x00000000

Answer 1

Hello,

Error code 0x80073701 usually indicates that there is a problem with the Windows Update components on your system. To resolve this issue, you can try the following steps:

1. Run the Windows Update troubleshooter. You can do this by going to Settings > Update & Security > Troubleshoot > Windows Update.
2. Reset the Windows Update components. You can do this by opening an elevated Command Prompt and running the following commands:

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

3. Perform a clean boot and try installing the update again. This will help you determine if any third-party software or services are interfering with the update process. Please refer to this link: How to perform a clean boot in Windows - Microsoft Support

4.Have you tried installing the update manually in Microsoft Update Catalog?

5.Check if there is enough disk space available on your system drive. If not, free up some space and try the update again.

Best Regards

Answer 2

@Xiuyun Lian

Problems also seen here: KB5034439

Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5034439).

This is critical and we do install before 1 week quality testing due to the Kerberos Security problem

MS Partner here with around 20+ WSUS Server and large number of endpoints all OS variants.

We also see this on a:

* 21H2, 20348.2227, Windows Server 2022, English, VL

* All BEFORE 01/2024 installed fine (Monthly on patch day)

* All patches 01/2024 BEFORE the KB5034439 patch install fine today

* Tried 5 times incl. Reboot and check of all

The SRV has NO Recovery Partition we thought those where NOT affected like the client Recovery Update patch which makes Problem with too small recovery partitions.

Also some KB table states that the KB will not be distributed through WSUS Server and that server hangs attached to a WSUS SRV 2022 (Self Update).

Do you check in the KB5034439 IF the OS has a Recovery Partition at start or just beginn and fail? ;-)

https://support.microsoft.com/en-gb/topic/kb5034439-windows-recovery-environment-update-for-azure-stack-hci-version-22h2-and-windows-server-2022-january-9-2024-6f9d26e6-784c-4503-a3c6-0beedda443ca

SRV 2022 affected and attached to WSUS Server 2022.

For you answer: We are aware on how to reset the WSUS client components but NEVER ever in the past 20 years had to do on a server.

Please provide info asap.

Thank you for helping

Greetings from Switzerland

Answer 3

I think, I guess that is the problem:

MA assumes that a SRV 2022 even in Large Enterprise has a RECOVERY Partition and that we waste Terabytes on such. As if someone would ever in such a box recovery a server with the Recovery Option except maybe a DC itself.

We brought some more info together on our blog. maybe this will help some persons.

https://www.butsch.ch/post/microsoft-patch-kb5034439-server-2022-also-fails-on-srv-2022-without-recovery-partition/

Greetings from Switzerland

Answer 4

It's an believable mess. I hope that Microsoft officially apologizes for this unprofessionally untested service pack. Took me the whole day to just find out what works and what is lost.