Server 2019 Install / Update Failure

Could you please perform the following steps in this order:

  1. Run the FRST64 script using fixlist.txt
  2. Run the SFCFix script using SFCFix.txt
  3. Run DISM again and then attach the CBS log
 

Attachments

Rich (BB code): 
2022-01-17 13:16:27, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #4464# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xf7782fb098->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_005b5a07a380674627e703eaa054326f_31bf3856ad364e35_none_413e516b7d4d45f5'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmap[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    ped disposition: 2016391772)[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    0000000a@2022/1/17:12:16:27.172 (F) onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-01-17 13:16:27, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #4463# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0xf7782fb5f8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_005b5a07a380674627e703eaa054326f_31bf3856ad364e35_none_413e516b7d4d45f5'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped dis[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    position: 2016392784)[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    0000000c (F) STATUS_OBJECT_NAME_NOT_FOUND #4462# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0xf7782fb880, key = NULL, disp = (null))[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #261# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd0000034]
2022-01-17 13:16:27, Error                 CSI    0000000e (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #260# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 3e0 (''), disp = 0)[gle=0x80070002]
2022-01-17 13:16:27, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-01-17 13:16:27, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Could you please run SFCFix using the the attached script and then run DISM again please? Afterwards, please zip up and provide all the logs found in the CBS logs folder. I just want to check the previous logs and see if we've missed any keys when the logs have rolled over.

The logs directory will be the following:

Rich (BB code): 
%systemroot%\Logs\CBS
 

Attachments

Thanks for providing the CBS logs, there appears to be another missing ComponentFamilies key again in the latest log. I'll take a look through the previous ones and check those too.
 
Could you please provide the following:

Step#1 - Export Winners
  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.


Once done please upload this file via Dropbox or OneDrive or SendSpace.
 
Thank you, the reasoning for asking for that particular key, is because I've been testing out a short program which I wrote last night which will hopefully find all the missing Component Families keys. Unfortunately, it seems that there is 11k+ missing keys and only really leaves us with two options: restore from an earlier backup which didn't have any Windows Update problems (if possible) or a clean install and then install the latest cumulative update (Jan 2022?).

"Healthy" Windows Server 2019 machine:

Rich (BB code): 
Subkey count for Winners: 21004
Subkey count for Component Families: 28283

Your machine:

Rich (BB code): 
Subkey count for Winners: 23410
Subkey count for Component Families: 12263
 
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