Server 2019 Install / Update Failure

Could you please try running the following command from an elevated command prompt:

Rich (BB code): 
Dism /Online /Cleanup-Image /RestoreHealth
 
Thanks for providing the log, just waiting for my fix proposal to be approved.
 
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Thanks, could you please try Windows Update again and it fails, then please attach the CBS log as before.
 
Could you please run:

Rich (BB code): 
Dism /Online /Cleanup-Image /RestoreHealth

You'll likely get another error message, if so, then please attach the CBS log. I suspect there is registry key left behind which will need to be removed.
 
Rich (BB code): 
2022-01-13 07:36:05, Error                 CSI    00000007 (F) STATUS_OBJECT_NAME_NOT_FOUND #3081# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x8cbd87aec8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_001c15ad3592bdc4260e00412c245ff1_31bf3856ad364e35_none_ca053e30fb4a552b'; a:(OBJ_CASE_INSENSITI[gle=0xd0000034]
2022-01-13 07:36:05, Error                 CSI    VE)}, disp = Unmapped disposition: 3179785384)[gle=0xd0000034]
2022-01-13 07:36:05, Error                 CSI    00000008@2022/1/13:06:36:05.175 (F) onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)

Looks like we've gone full circle with a different key this time. Could you please provide a fresh COMPONENTS hive using the following instructions:

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.
 
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:4464455
  4. Let me know if it says it was successful or if there are any errors.
If it fails, then could you please do a registry search as we did in post #9, however, this time you'll need to search for KB4464455.
 
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

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Afterwards, please run the following command:

Rich (BB code): 
Dism /Online /Cleanup-Image /RestoreHealth

If it fails, then please attach the CBS log.
 

Attachments

Rich (BB code): 
2022-01-14 21:20:45, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #4182# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x2fcad7ae68->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_003ecb43095412b7775c99b44cd15c13_6595b64144ccf1df_none_308fa21e7f1b6c95'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmap[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    ped disposition: 3403132972)[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    0000000a@2022/1/14:20:20:45.924 (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-14 21:20:45, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #4181# from Windows::Rtl::SystemImplementation::CBufferedRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS), oa = @0x2fcad7b3c8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_003ecb43095412b7775c99b44cd15c13_6595b64144ccf1df_none_308fa21e7f1b6c95'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped dis[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    position: 3403133984)[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    0000000c (F) STATUS_OBJECT_NAME_NOT_FOUND #4180# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_ALL_ACCESS), oa = @0x2fcad7b650, key = NULL, disp = (null))[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #261# from CCSDirect::EnumStoreCorruptions(...)[gle=0xd0000034]
2022-01-14 21:20:45, Error                 CSI    0000000e (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #260# from Windows::COM::CStorePendingStoreRepairTxn_IStorePendingStoreRepairTransaction::Detect(Flags = 4, cancelEvt = 3f0 (''), disp = 0)[gle=0x80070002]
2022-01-14 21:20:45, Error                 CBS    Rept: Failed to call CSI detect. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-01-14 21:20:45, Info                  CBS    Failed to check CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Unfortunately, there appears to be another missing key from KB5003171. Fortunately, since we removed the other remnants of the update earlier, we'll just need to remove the associated Components subkey.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Afterwards, please run the following command:

Rich (BB code): 
Dism /Online /Cleanup-Image /RestoreHealth

If it fails, then please attach the CBS log.
 

Attachments

Rich (BB code): 
2022-01-15 14:46:18, Error                 CSI    00000007 (F) STATUS_OBJECT_NAME_NOT_FOUND #4232# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x77128fb0d8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[190]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2170 (WinBuild.160101.0800)\ComponentFamilies\amd64_003f5e12ffde430b3f5f525311f492b8_31bf3856ad364e35_none_a82fd9666e4e609f'; a:(OBJ_CASE_INSENSITI[gle=0xd0000034]
2022-01-15 14:46:18, Error                 CSI    VE)}, disp = Unmapped disposition: 311406264)[gle=0xd0000034]
2022-01-15 14:46:18, Error                 CSI    00000008@2022/1/15:13:46:18.201 (F) onecore\base\wcp\sil\ntsystem.cpp(5348): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)

Could you please perform a FRST64 registry search for KB5004244?
 
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