Windows Update error - 0x80073701

Hello Ramchandra Mishra

You should first verify the specific missing component by examining the CBS log located at C:\Windows\Logs\CBS\CBS.log. Search for the string "SXS_ASSEMBLY_MISSING" or the error code "0x80073701" to identify the exact package name. Once identified, the most effective resolution for Windows Server 2022 is to perform an in-place repair using a mounted ISO of the exact same build version. Insert or mount the Windows Server 2022 installation media and run the following command from an elevated prompt: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\Sources\Install.wim:1 /LimitAccess (replacing D: with your drive letter and ensuring the index number matches your Standard Edition). This forces DISM to pull healthy files from known good media rather than relying on the corrupted local store or Windows Update servers.

If the error persists after an offline repair, the "Some settings are managed by your organization" notification in your screenshot suggests that Group Policy Objects (GPOs) may be restricting update behaviors or pointing to a local WSUS server that lacks the necessary metadata for KB5073457. Ensure that the registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate is not enforcing a specific target version or blocking the download of optional features. If you are in a managed environment, try bypassing the local WSUS by setting the "Don't connect to any Windows Update Internet locations" policy to "Disabled" or manually checking for updates against Microsoft's public servers via the "Check online for updates from Microsoft Update" link.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Hello again Ramchandra Mishra,

Just following up with your issue. To recap, to resolve this on a production Windows Server 2022, you must provide a valid, external repair source that contains the healthy versions of the missing assemblies. You need to obtain the official Windows Server 2022 installation media (ISO) that matches your server's exact OS build and language. Mount this ISO (for this example, let's assume it mounts as drive D:). You first need to identify the correct index for "Standard Edition" (usually Index 2 for Desktop Experience) by running dism /Get-WimInfo /WimFile:D:\sources\install.wim. Once confirmed, run the following command in your elevated prompt: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:2 /LimitAccess. The /LimitAccess switch is mandatory here because your screenshot shows "Some settings are managed by your organization," implying Group Policies are active. This switch prevents DISM from attempting to contact Windows Update or your local WSUS (which likely lacks the repair files) and forces it to pull strictly from the mounted ISO.

If the DISM source repair completes successfully, immediately restart the Windows Modules Installer service and attempt the update again. However, if DISM still fails with 0x80073701 or 0x800f081f even with the source media, the component store corruption is likely too deep for granular file replacement. In this scenario, the industry-standard "best practice" to restore system integrity without rebuilding from scratch is to perform a repair install (In-Place Upgrade). Run setup.exe directly from the mounted ISO while logged into the server, and verify that "Keep personal files and apps" is selected. This process rewrites the entire Windows directory and Component Store with healthy files from the media while preserving your domain join, IP configuration, installed roles, and data.

If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP