Hi,
I have an odd issue with a device that cannot install cumulative updates. Running SFCFix (no errors), ComponentScanner (no errors), DISM /RepairImage (online and with a WIM provided), Windows Update troubleshooter and a plethora of other alternatives did not fix the problem for me, so I got to some digging. I traced the issue down to missing manifest files, as shown in CBS.log:
There's about 50 or so such entries, and I have checked these files on the target device at "C:\Windows\WinSxS\Manifests" and all are missing. Now, I have checked the following guide on how to fix the issue:
How to fix Windows Update errors using DISM (DISM.log) or the System Update Readiness Tool / SURT (CheckSUR.log)
and managed to find most of the exact filenames in a fresh install.wim image. However, I am still searching for 4 that are missing (still checking if they are found in other images or in cumulative updates):
Two questions:
- Will replacing the .manifest files address such an issue? I saw the note on the guide I linked about placing them in %SystemRoot%\Temp\CheckSur\winsxs\Manifests, so this leads me to believe this is indeed a fix for such a problem.
- Where and how can I obtain these missing manifest files? Is there some general repository or at least some article that may offer additional leads?
I have an odd issue with a device that cannot install cumulative updates. Running SFCFix (no errors), ComponentScanner (no errors), DISM /RepairImage (online and with a WIM provided), Windows Update troubleshooter and a plethora of other alternatives did not fix the problem for me, so I got to some digging. I traced the issue down to missing manifest files, as shown in CBS.log:
Code:
...
2023-05-30 10:42:48, Info CBS Repr: No owner found for component amd64_microsoft-windows-r..sl-events-component_31bf3856ad364e35_10.0.19041.1_none_0c4ab3fe7315028d, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2023-05-30 10:42:48, Info CBS Not able to get CBS component onwers for component amd64_microsoft-windows-r..sl-events-component_31bf3856ad364e35_10.0.19041.1_none_0c4ab3fe7315028d [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2023-05-30 10:42:48, Info CBS Repr: Non CBS installed component found, ignore it since it is not repairble
2023-05-30 10:42:48, Info CBS Repr: No owner found for component amd64_microsoft-windows-r..er-events-component_31bf3856ad364e35_10.0.19041.1_none_34d95c6894b18210, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2023-05-30 10:42:48, Info CBS Not able to get CBS component onwers for component amd64_microsoft-windows-r..er-events-component_31bf3856ad364e35_10.0.19041.1_none_34d95c6894b18210 [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2023-05-30 10:42:48, Info CBS Repr: Non CBS installed component found, ignore it since it is not repairble
...There's about 50 or so such entries, and I have checked these files on the target device at "C:\Windows\WinSxS\Manifests" and all are missing. Now, I have checked the following guide on how to fix the issue:
How to fix Windows Update errors using DISM (DISM.log) or the System Update Readiness Tool / SURT (CheckSUR.log)
and managed to find most of the exact filenames in a fresh install.wim image. However, I am still searching for 4 that are missing (still checking if they are found in other images or in cumulative updates):
Code:
amd64_microsoft-windows-s..iencehost.appxsetup_31bf3856ad364e35_10.0.19041.1320_none_52db864c6a9f0d04.manifest
amd64_microsoft-windows-wpd-shellextension_31bf3856ad364e35_10.0.19041.1566_none_85ce506c7c135c61.manifest
amd64_microsoft-windows-s..rity-spp-pkeyconfig_31bf3856ad364e35_10.0.19041.1682_none_c05bfba5215c49a1.manifest
amd64_microsoft-windows-s..iencehost.appxsetup_31bf3856ad364e35_10.0.19041.1320_none_52db864c6a9f0d04.manifestTwo questions:
- Will replacing the .manifest files address such an issue? I saw the note on the guide I linked about placing them in %SystemRoot%\Temp\CheckSur\winsxs\Manifests, so this leads me to believe this is indeed a fix for such a problem.
- Where and how can I obtain these missing manifest files? Is there some general repository or at least some article that may offer additional leads?