One of my Windows Server 2022 machines has failed to install updates for the past two months, including the July and August cumulative updates. It is a physical Dell PowerEdge server used as an NVR, and several nearly identical systems have updated successfully. The update fails with error 0x80073701. So far I have run DISM cleanup commands and SFC, stopped update-related services, renamed the SoftwareDistribution folder, downloaded and installed the August cumulative update manually, and tried deploying it through NinjaOne. What else should I check before considering a reinstall?
4 Answers
If the component store is genuinely damaged and DISM cannot repair it even with a matching installation source, an in-place repair install may be the least disruptive option. Back up the NVR configuration and data first, document the drivers and installed software, and confirm the repair media matches the current Windows Server release before proceeding.
Before reinstalling, compare the last successful updates with the current server’s build and installed roles. Check whether the failing package appears in the CBS or Windows Update logs and whether that specific cumulative update has a known prerequisite or compatibility issue. You can also try initiating the update from the built-in server configuration menu, but the logs should provide more useful information.
Start with C:WindowsLogsCBSCBS.log. Search for the update package that is failing and look for entries marked as error, missing, or corruption. That usually identifies the specific component instead of just showing the generic update code.
That error often points to corruption or a missing component in the servicing store. Try DISM /Online /Cleanup-Image /RestoreHealth, followed by sfc /scannow, and make sure DISM completes before running SFC. If Windows Update cannot provide the repair files, use a mounted install.wim from installation media matching the server’s exact build and edition as the repair source.
I would avoid manually copying individual files from another server’s WinSxS folder. Even similar machines may have different builds or package states, so an installation source and the CBS log are safer ways to repair it.
You can open the log in Notepad, Notepad++, or another text editor and search for terms like “error,” “failed,” and “0x80073701.” PowerShell’s Get-WindowsUpdateLog can also generate a more readable Windows Update log.