Share via

KB5075906 Failing to Install on Windows Server 2022 – Error 0x80073701

Laxman singh 1 Reputation point
2026-03-10T07:45:18.5533333+00:00

Hello Team,

We are experiencing an issue installing KB5075906 on Windows Server 2022. The update repeatedly fails with error 0x80073701.

To troubleshoot the issue, I have already performed the following steps:

  1. Restarted Windows Update related services:
net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

Cleared the Windows Update cache:

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

Restarted the services again:

net start wuauserv
net start bits
net start cryptsvc
net start msiserver

Ran system repair commands:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

All commands completed successfully, but KB5075906 still fails to install.

Could you please advise:

What additional troubleshooting steps should be performed?

Is this a known issue with KB5075906 on Server 2022?

Are there any logs or specific components we should check further?

Any guidance would be appreciated.

Thank you.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Harry Phan 17,050 Reputation points Independent Advisor
    2026-03-10T08:51:48.1333333+00:00

    Hi Laxman,

    Error 0x80073701 on Windows Server 2022 indicates ERROR_SXS_ASSEMBLY_MISSING, meaning a required component in the WinSxS store is missing or corrupted. Since SFC and DISM /RestoreHealth completed successfully, check C:\Windows\Logs\CBS\CBS.log for entries showing missing assemblies or failed package deployment during the KB installation. If a component is missing, try installing the update manually from this link: catalog.update.microsoft.com. If the failure persists, the supported fix is an in-place repair upgrade using the latest Server 2022 ISO (setup.exe → Keep files and apps) to rebuild the component store. Currently there is no broadly documented issue specific to this update failing on Server 2022.

    I hope it's helpful. If it is, please give it a thump up or an accept answer, appreciate it :)

    Harry.

    0 comments
  2. Q&A Assist
    2026-03-10T07:45:46.58+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Error 0x80073701 indicates component store corruption that prevents the update from completing, even though basic repair and cache reset steps have already been run.

    Since the SoftwareDistribution/catroot2 reset and sfc/DISM /RestoreHealth have already been completed, use the following additional steps that are supported in the provided documentation:

    1. Check Event Logs and WindowsUpdateClient details
      1. Open Event Viewer → Application and Service Logs → Microsoft → Windows → WindowsUpdateClient → Operational.
      2. Identify the specific failure events for KB5075906 and confirm the exact error code and any related component or package names.
      3. Also review System and Application logs around the time of the failed installation.
      4. Use the failure code and update identity with the guidance in Common Windows Update errors or the Windows Update error reference linked from the troubleshooting checklist.
    2. Confirm there is no pending reboot
      1. Make sure the server has been restarted after previous update attempts.
      2. If any servicing operation is pending, reboot once more before retrying the update.
    3. Run DISM component cleanup specifically On the affected server, from an elevated Command Prompt: 
         dism /online /cleanup-image /startcomponentcleanup
      Wait for it to complete, then restart the server and try installing KB5075906 again. This is a documented mitigation for 0x80073701/0x800f0988-type component store issues.
    4. Use the Windows Update troubleshooter / reset components again if needed If the issue persists:
      1. Run the Windows Update troubleshooter for Windows Server as described in the Windows Server update troubleshooting guidance.
      2. If applicable, follow the documented procedure to reset Windows Update components (including BITS and Windows Update service checks) and then run: 
              wuauclt /detectnow
        to force detection.
    5. Verify Windows Update services and BITS health
      1. Confirm wuauserv is running: 
              sc query wuauserv
      2. If it is stopped, start it: 
              sc start wuauserv
      3. If BITS configuration is suspected to be corrupted and all other steps fail, follow the documented BITS repair procedure (only as a last resort) and then retry the update.
    6. Consider deeper repair if repeated installation errors continue If KB5075906 continues to fail with 0x80073701 after the above:
      1. Use the Windows Server update troubleshooting guidance to:
        • Confirm latest Servicing Stack Update is installed.
        • Run DISM again as per “Fix Windows Update errors by using the DISM or System Update Readiness tool”.
      2. If Event Viewer and DISM indicate unrepairable corruption, follow the guidance to repair the component store from another source (for example, using SFC/DISM with an alternate source as described in the referenced articles).
    7. Logs and components to focus on For further analysis, focus on:
      • Event Viewer → WindowsUpdateClient Operational log for KB5075906 failures.
      • CBS.log and DISM logs when running /startcomponentcleanup and /restorehealth.
      • Status of wuauserv, BITS, and related services.

    The provided context does not list KB5075906 as a known specific issue on Windows Server 2022, so treat this as a generic servicing/component store problem and follow the above Windows Update troubleshooting flow.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.