Chris_Axper
New member
- Jun 12, 2025
- 2
Hello,
I am encountering an issue on Windows Server 2019 Standard Version 1809 (OS Build 17763.6659) where Windows Update cannot install updates and is instead giving error 0x80073712. Currently, the only update to be done is 2025-05 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5058392) which fails after being stuck on 20% for a while and then moving to 44% a short bit before failing. This happens every time I try to run Windows Update.
This problem started after what is believed to be a power outage that caused some corruption in low-level Windows components rendering Windows Update unable to do its job. I've been trying to fix this using DISM, but it always fails around the same point with Error 2 that the file specified cannot be found. This happens when using DISM online or offline, relying on Windows Update as fall back or not and even after generating an install.wim file from a new machine in an attempt to resolve. It seems the issue lies with a specific component that's missing from the install.wim and somehow cannot be obtained from Windows Update's fallback for DISM. I also do not have the original install media to attempt a repair from it, nor am I able to get my hands on one at this point.
I have isolated a section of the DISM log that seems relevant as it seems to be what causes issues every time:
Error STATUS_OBJECT_NAME_NOT_FOUND ...
\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.7313 (WinBuild.160101.0800)\ComponentFamilies\
amd64_microsoft-windows-c..ervices-certadm-dll_31bf3856ad364e35_none_a92d024447ce631d\v!10.0.17763.1697
As I understand, DISM is looking specifically for the component at version .1697 which is not present in my install.wim and is also no longer available through the Microsoft Update Catalog to have it installed on the machine I used to generate the install.wim to generate a new one with the required component version for the repair.
I am currently at a loss as to how I can resolve this and require assistance.
Let me know if you need more information and thank you for your time and consideration on my issue.
I am encountering an issue on Windows Server 2019 Standard Version 1809 (OS Build 17763.6659) where Windows Update cannot install updates and is instead giving error 0x80073712. Currently, the only update to be done is 2025-05 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5058392) which fails after being stuck on 20% for a while and then moving to 44% a short bit before failing. This happens every time I try to run Windows Update.
This problem started after what is believed to be a power outage that caused some corruption in low-level Windows components rendering Windows Update unable to do its job. I've been trying to fix this using DISM, but it always fails around the same point with Error 2 that the file specified cannot be found. This happens when using DISM online or offline, relying on Windows Update as fall back or not and even after generating an install.wim file from a new machine in an attempt to resolve. It seems the issue lies with a specific component that's missing from the install.wim and somehow cannot be obtained from Windows Update's fallback for DISM. I also do not have the original install media to attempt a repair from it, nor am I able to get my hands on one at this point.
I have isolated a section of the DISM log that seems relevant as it seems to be what causes issues every time:
Error STATUS_OBJECT_NAME_NOT_FOUND ...
\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.7313 (WinBuild.160101.0800)\ComponentFamilies\
amd64_microsoft-windows-c..ervices-certadm-dll_31bf3856ad364e35_none_a92d024447ce631d\v!10.0.17763.1697
As I understand, DISM is looking specifically for the component at version .1697 which is not present in my install.wim and is also no longer available through the Microsoft Update Catalog to have it installed on the machine I used to generate the install.wim to generate a new one with the required component version for the repair.
I am currently at a loss as to how I can resolve this and require assistance.
Let me know if you need more information and thank you for your time and consideration on my issue.