Hi,
a possible solution of an Windows Update Errors 0x8007371B.
sfc /scannow
and dism /online /cleanup-image /restorehealth
run without any errors but windows updates failed to install.
C:\windows\logs\CBS\CBS.log has some STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE errors:
2019-11-14 10:59:41, Info CSI 00000036 Changelist shadowed missing its manifest - Microsoft-Windows-ServicingStack-Inetsrv-Extra, version 10.0.17134.881, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2019-11-14 10:59:41, Error CSI 00000037@2019/11/14:09:59:41.119 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2019-11-14 10:59:41, Error CSI 00000038@2019/11/14:09:59:41.119 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1306): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]
2019-11-14 10:59:41, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
Check if Windows component store points to the latest version. Note: The registry value has not the full length of the name(Microsoft-Windows-ServicingStack-Inetsrv-Extra -> ..ft-windows-s..stack-inetsrv-extra..).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_none_8e6f3b7ef623f7ff
Get all installed versionsof a component
dir C:\Windows\WinSxS\Manifests\*Inetsrv-Extra* Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 12.10.2019 02:12 209 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.1000_none_f3bf53e743ca2923.manifest ------ 12.11.2019 08:30 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.1063_none_f3c5114b43c50e10.manifest ------ 13.11.2019 16:53 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.1120_none_f3b6848f43d077c2.manifest -a---- 11.04.2018 23:04 202 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.1_none_1eb0a7310ad43353.manifest -a---- 11.10.2018 18:11 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.281_none_1aab2abaf7e095c3.manifest -a---- 13.12.2018 15:38 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.400_none_1b00ad9cf7a09732.manifest -a---- 10.01.2019 08:10 209 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.464_none_1ac3cf3cf7cda434.manifest -a---- 14.03.2019 07:57 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.580_none_1aaa3022f7e173e1.manifest -a---- 27.06.2019 10:59 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.760_none_1abfd3c6f7d1364d.manifest -a---- 14.08.2019 13:18 210 amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.881_none_1aab361ef7e084ad.manifest -a---- 11.04.2018 23:04 198 x86_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364e35_10.0.17134.1_none_c2920bad5276c21d.manifest
and check the pointer (default value)
PS D:> dir HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-s..stack-inetsrv-extra_31bf3856ad364 e35_none_8e6f3b7ef623f7ff Name Property ---- -------- 10.0 10.0.17134.1 : {1} (default) : 10.0.17134.1120 10.0.17134.281 : {1} 10.0.17134.400 : {1} 10.0.17134.464 : {1} 10.0.17134.580 : {1} 10.0.17134.760 : {1} 10.0.17134.881 : {1} 10.0.17134.1120 : {1} 10.0.17134.1063 : {1}
Michael
Wow, I encountered this 4 years after you post the blog on build 22621, solved by your method successfully, thanks!
Wow, it happens on my PC with build 22621, solved by the method you offered 4 years ago…anyway, thanks!
can anyone expand on what you did to fix this. i have a similar issue. do you edit the registry to match the correct version number?