I had success with the following approach:
- mount Windows ISO again and run setup.exe.
- under "Change how Setup downloads updates" > select "Not right now".
- select keep all data and install Windows
- install all updates
I hope this helps someone.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Good day all
I have updated several servers from 2019 to 2022, which worked without any problems. But on one server, the message appears in the updates:
"There were some issues installing the updates, but we will try again later". If you keep seeing this message and want to search the web for information or contact support, this may help: (0x80073701)"
also below:
"We couldn't install this update, but you can try again (0x80073701).
2021-09 Cumulative Update for Microsoft Server Operating System Version 21H2 for x64-based Systems (KB5005619)"
I have already tried to install the update manually (windows10.0-kb5005619-x64_b9ba79a781de6520ef0fbae4baf79614f3f1ec75.msu). As well as the commands
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:C:\install.wim:4 /LimitAccess
sfc /scannow
as well as "chkdsk" all without success.
Does anyone have any idea how to fix this error?
Thanks and best regards
I had success with the following approach:
I hope this helps someone.
0x80073701 = ERROR_SXS_ASSEMBLY_MISSING which means there are some system files are missing, which caused the update installation failure. You can also try a repair install by running setup.exe from the root of the install.
I wouldn't hold much hope for this, time may be better spent standing up a new one, patch it fully and migrate the roles or applications over to it.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Dear Patrick
Thank you for the feedback. I have already tried that, unfortunately the installation via "setup.exe" does not bring anything either.
Is there any other tip to resolve this error, the system is configured very elaborately and unfortunately can not be taken over so easily...