This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Dear Microsoft Support,
I am encountering an issue with the installation of KB5046616 on a server running Windows Server 2022 (OS version: 10.0.20348). The installation fails repeatedly with the following error:
Package KB5046616 failed to be changed to the Installed state. Status: 0x80073701.
Problem Details:
When using the DISM tool or the command line with administrative privileges (e.g., /online /add-package /packagepath), the installation fails to complete. The logs indicate missing assemblies (STATUS_SXS_ASSEMBLY_MISSING) and an incomplete package state.
According to the CBS log, the following errors were observed:
ERROR_SXS_ASSEMBLY_MISSING
ERROR_FILE_NOT_FOUND (for files such as pending.xml, pending.xml.bad)
Conflicts in packages, such as Microsoft-OneCore-VHD-WOW64-Package.
The following troubleshooting steps have been attempted:
System integrity checks: sfc /scannow, dism /online /cleanup-image /restorehealth
Stopping services: TrustedInstaller, Windows Update, CryptSvc, BITS
Renaming folders: PendingRenames, Sessions
Offline package installation: Using DISM on an offline image
The update has been repeatedly re-downloaded from the Microsoft Update Catalog.
Logs provided:
CBS log with detailed error information is attached.
Error summary: HRESULT=0x80073701 and related entries.
System Information:
OS Version: Windows Server 2022 Standard (build 20348)
Architecture: x64
Services: Firewall is disabled, and all other updates have been successfully applied except for KB5046616.
Request for Assistance:
I kindly request assistance in identifying the root cause of this issue and guidance on how to resolve it. If it is necessary to repair the CBS database or provide missing components, please advise on the required steps or tools.
Thank you for your time and support in resolving this matter.
Hynek Bošek
******@milsoft.cz
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Sorry, no. I'm really upset over Microsoft's "try again later" stance, since you can try forever without success. There are 36 other people who've reported the same problem -- this isn't a one-of-a-kind issue. There HAS to be a fix, but Microsoft can't be bothered. The update catalogue version still hasn't been updated since 11/12.
Am having a similar issue:
2024-11 Cumulative Update for Microsoft server operating system
version 21H2 for x64-based Systems (KB5046616)
Status: Some update files are missing or have problems. We'll try
to download the update again later. Error code:
(0x8007000d)
What good does retry do if the file is being downloaded from an update server? It will just keep downloading the same corrupted file over and over.
Hi Jeff,
I have exactly the same problem with the update and have tried everything.
Unfortunately, I can't perform a repair installation either, as this is an important server.
Have you been able to solve the problem in the meantime?
Greetings Thorsten
The update isn't the problem. There is corruption. You can try downloading the ISO of the server and use the dism command that points to that mounted location. A DISM alone won't cut it.
https://superuser.com/questions/870864/how-to-run-dism-against-a-local-source
Since none of the solutions I found on various online forums were successful, I decided to take the path of least resistance and reinstalled Windows Server 2022.
After the new installation, I applied all available updates, including the problematic KB5046616, which was successfully installed this time.
This reinstallation was prompted by the conclusions I drew from all the failed attempts to repair the original system.
Thank you for your time and support in resolving this matter.
