Server 2019 Install / Update Failure

MBr

Member
Joined
Nov 23, 2021
Posts
22
Location
Germany Stuttgart
Hello together,
I think I need some help...
the Problem showed up first when I tried to install a new Version of the Tivol Storage Manager Backup Software, it aborted with an assembly error. To solve the Problem, I checked the update section and there where several failed attempts to Install the KB5007206 with the error 0x8007371b. sfc /scannow gives back a "Windows Resource Protection could not start the repair service" also in save mode. Dism /Online /Cleanup-Image /RestoreHealth gives back an error 2 also SFCfix. Even an inplace upgrade failed.
By checking the log files, the error points to an folder in WinSxS where are some files, but also a lot are missing, for me it looks like that something with went horribly wrong with the service stack 10.0.17763.2170 update. If I run winver it gives back 1809 (Build 17763.2114)
Now I've made the Steps as mentioned earlier and in the Manual described again with a clean cbs file.

I hope someone is able to solve this and help me. I'am not really in the mood the install the whole machine new...

Thanks in advance and thanks for all the support you provide to us
Markus
 

Attachments

Hi @MBr,

I apologise for the delayed response, I'll have a look at the log files for you. Please note I'm still new to Windows Update issues so I may request assistance from a more experienced helper.
 
I'm posting these errors for reference:

Rich (BB code):
2021-11-23 08:57:59, Error                 CSI    0000007f (F) STATUS_OBJECT_NAME_NOT_FOUND #64436# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x6db30fb378->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_001179c8ba13805f8cd9990cb5eca93e_6595b64144ccf1df_none_ed1f846e6fced5c4'; a:(OBJ_CASE_INSENSIT[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    IVE)}, disp = Unmapped disposition: 3004150104)[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    00000080@2021/11/23:07:57:59.630 (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]
2021-11-23 08:57:59, Error                 CSI    00000081 (F) STATUS_OBJECT_NAME_NOT_FOUND #64435# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x6db30fb378->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_001179c8ba13805f8cd9990cb5eca93e_6595b64144ccf1df_none_ed1f846e6fced5c4'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unma[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    pped disposition: 3004151100)[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    00000082@2021/11/23:07:57:59.630 (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]
2021-11-23 08:57:59, Error                 CSI    00000083 (F) STATUS_OBJECT_NAME_NOT_FOUND #64434# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0x6db30fb8d8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_001179c8ba13805f8cd9990cb5eca93e_6595b64144ccf1df_none_ed1f846e6fced5c4'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped di[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    sposition: 3004152112)[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    00000084 (F) STATUS_OBJECT_NAME_NOT_FOUND #64433# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0x6db30fbb60, key = NULL, disp = (null))[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    00000085 (F) STATUS_OBJECT_NAME_NOT_FOUND #62458# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd0000034]
2021-11-23 08:57:59, Error                 CSI    00000086 (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #62457# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 5a0 (''), disp = 0)[gle=0x80070002]
2021-11-23 08:57:59, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2021-11-23 08:57:59, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Rich (BB code):
2021-11-23 08:55:55, Error                 CSI    00000069@2021/11/23:07:55:55.04 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2021-11-23 08:55:55, Error                 CSI    0000006a@2021/11/23:07:55:55.04 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1264): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]
2021-11-23 08:55:55, Error                 CSI    0000006b (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #45534# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024]
2021-11-23 08:55:55, Error                 CSI    0000006c (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #45533# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024]
2021-11-23 08:55:55, Error                 CSI    0000006d (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #45532# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150024]
2021-11-23 08:55:55, Error                 CSI    0000006e (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #45531# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150024]
2021-11-23 08:55:55, Error                 CSI    0000006f (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #43585# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x8007371b]
2021-11-23 08:55:55, Error                 CSI    00000070 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #39571# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 102, pSink = NULL, disp = 0)[gle=0x8007371b]
2021-11-23 08:55:55, Error                 CSI    00000071 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #39570# 257383 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000066, pSink = NULL, disp = 0)
[gle=0x8007371b]
2021-11-23 08:55:55, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2021-11-23 08:55:55, Info                  CBS    Setting RollbackFailed flag to 0
2021-11-23 08:55:55, Info                  CBS    Clearing HangDetect value
2021-11-23 08:55:55, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2021-11-23 08:55:55, Error                 CBS    Exec: Failed to commit CSI transaction to execute changes. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2021-11-23 08:55:55, Info                  CBS    Perf: InstallUninstallChain complete.
2021-11-23 08:55:55, Info                  CSI    00000072@2021/11/23:07:55:55.011 CSI Transaction @0x1bf5e9ee100 destroyed
2021-11-23 08:55:55, Info                  CBS    Failed to execute execution chain. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2021-11-23 08:55:55, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]
2021-11-23 08:55:55, Info                  CBS    WER: Generating failure report for package: Package_for_ServicingStack_2262~31bf3856ad364e35~amd64~~17763.2262.1.2, status: 0x8007371b, failure source: Execute, start state: Staged, target state: Installed, client id: UpdateAgentLCU
2021-11-23 08:55:55, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
 
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Thanks, I've requested some help with this thread as I'm still undergoing WU training.
 
Remove Update Manually
  1. Click on the Start button and in the search box, type Command Prompt.
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:5003171
  4. Let me know if it says it was successful or if there are any errors.
 
I tried to remove the Update as you told me. Unfortunately,the System started to search and told me then, that KB5003171 is not installed...
 
FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Server Manager or Windows Features dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.

  6. Right-click on the file FRST64.exe and choose Run as administrator.
  7. Copy and paste KB5003171 into the Search box and click the Search Registry button.
  8. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  9. You may close any remaining open windows now.
 
Thanks, I've attempted to generate a fix and have asked for someone more experienced to check it over to ensure that it's correct.
 
Could you please export the following as a registry hive:

Rich (BB code):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Thanks a lot so far. The only Problem was, that with the fixlist it ran into the 60min limit of FRST without processing all the files. So I started a second run, stupidly I didn't save the first fixlog and it was overwritten. In the zip package are serveral files. The fixlog from the 2nd run. The Registry Hive before the first and after the 2nd run as .txt. A new cbs and dism file after the 2nd run. And a search registry run after the 1st and after the 2nd run. And a components file after the 2nd run. I hope it helps to find and solve the Problem.
 

Attachments

Thanks, could you please execute the following fix script using the same instructions as before?
 

Attachments

Thank you, appears that those keys were successfully removed. Could you please do another registry search using FRST again? You can use the same instructions from post #9.
 

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

Back
Top