[SOLVED] Windows Server 2019 Cumulative Update KB5015811 Error 0x80073712

DISM RestoreHealth fails as you assumed to. Now with error 2 at 4.5%.
 

Attachments

Rich (BB code): 
2022-08-25 08:18:41, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #2398# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0x60db77b338->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_none_31f4062603e3901e\v!10.0.17763.3165'; a:(OBJ_CASE_INSENSIT[gle=0xd0000034]
2022-08-25 08:18:41, Error                 CSI    IVE)}, disp = Unmapped disposition: 3682055056)[gle=0xd0000034]
2022-08-25 08:18:41, Error                 CSI    0000000c (F) STATUS_OBJECT_NAME_NOT_FOUND #2397# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0x60db77b5c0, key = NULL, disp = (null))[gle=0xd0000034]
2022-08-25 08:18:41, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #261# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd0000034]
2022-08-25 08:18:41, Error                 CSI    0000000e (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #260# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 608 (''), disp = 0)[gle=0x80070002]
2022-08-25 08:18:41, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-08-25 08:18:41, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Afterwards, please attempt to run DISM again and attach the latest CBS log(s).
 

Attachments

Rich (BB code): 
2022-08-25 16:09:35, Info                  CSI    00000007 Warning: Unable to repair payload file ([l:11]'iiscore.dll') for component ([l:101 ml:140]'amd64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_10.0.17763.3165_none_e2ac623cf7a82e94') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-25 16:09:35, Info                  CSI    00000008 Warning: Unable to repair payload file ([l:8]'w3dt.dll') for component ([l:101 ml:140]'amd64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_10.0.17763.3165_none_e2ac623cf7a82e94') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-25 16:09:35, Info                  CSI    00000009 Warning: Unable to repair payload file ([l:12]'hwebcore.dll') for component ([l:101 ml:140]'amd64_microsoft-windows-i..rewebenginebinaries_31bf3856ad364e35_10.0.17763.3165_none_e2ac623cf7a82e94') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-25 16:09:39, Error                 CSI    0000000a (F) STATUS_OBJECT_NAME_NOT_FOUND #37220# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xab28facc8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[201]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-msxml30_31bf3856ad364e35_none_82bc90dc691f0b04\v!10.0.17763.2989'; a:(OBJ_CAS[gle=0xd0000034]
2022-08-25 16:09:39, Error                 CSI    E_INSENSITIVE)}, disp = Unmapped disposition: 2995759784)[gle=0xd0000034]
2022-08-25 16:09:39, Error                 CSI    0000000b@2022/8/25:14:09:39.684 (F) onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)

Unfortunately, it seems that DISM is failing far too early to provide anything useful and therefore I would recommend that you attempt to install the failing update with Process Monitor running again.
 

Attachments

I got the same update error on a W10 Master Image. We use Citrix PVS and I could go back to the previous version and tried again. So I found a solution with the following steps.
  1. DISM /Online /Cleanup-Image /AnalyzeComponentStore
  2. DISM /Online /Cleanup-Image /StartComponentCleanup, some packages could be released
  3. Install latest Windows Updates
  4. DISM /Online /Cleanup-Image /StartComponentCleanup, some more packages could be released
Then I searched and found a backup of the server before the error occurred first, tried the steps and it worked!

Could you please check CBS logs for me? Could I continue working with this version?
 

Attachments

Your latest CBS log appears to be okay, if you're happy with your backup image then I would continue to use the server as you normally would.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top