Windows (Cumulative) Updates failing to install [Server 2016]

S

sfranssen

Well-known member
Joined
Jun 29, 2021
Posts
61
Hi guys,

we are running into issues where installing the Cumulative Windows Updates are failing.

The error code: 0x80073701

Any help on repairing it would be greatly appreciated!

After trying to repair the server be myself, i tried to repair the server with the SFCfix.exe tool. Also this tool could not repair the server. I uploaded the SFCfix.exe log and the CSB folder in the attachment.
Can you guys help me out with this problem?

I hope to here from you soon.

Kind Regards,
 

Attachments

Rich (BB code): 
2022-05-05 13:56:10, Info                  CSI    00000009@2022/5/5:11:56:10.212 CSI Transaction @0x1c4da454500 destroyed
2022-05-05 13:56:10, Info                  CBS    Repr: No owner found for component amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_10.0.14393.4583_none_76e4ae5aa95741a4, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-05-05 13:56:10, Info                  CBS    Not able to get CBS component onwers for component amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_10.0.14393.4583_none_76e4ae5aa95741a4 [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-05-05 13:56:10, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble
2022-05-05 13:56:10, Info                  CBS    Repr: No owner found for component amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_10.0.14393.4583_none_16fad4e2daadfef7, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-05-05 13:56:10, Info                  CBS    Not able to get CBS component onwers for component amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_10.0.14393.4583_none_16fad4e2daadfef7 [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-05-05 13:56:10, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble

Export CBS hive
  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • 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\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.
 
Hi,

so great you took this topic so quick!
Here the attached registry file.

So grateful you progress with this. Its awesome you have the knowledge and willingness to help!

Waiting patient for you possible help.
 

Attachments

Thank you, could you please provide your COMPONENTS hive and your SideBySide 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.

Export SideBySide
  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
  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.
 
Rich (BB code): 
HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_none_054fc4877123fa63\v!10.0.14393.4583

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_none_96a6d1b24f36c8e8\v!10.0.14393.4583

It seems that the above subkeys may be corrupt, I'm going to need to install a VM with the same CU installed as you do. I'll respond back with a fix after I've set one up.
 
SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
    [/LIST]
    Afterwards, please open an elevated command prompt and enter the following command:

    [code=rich]DISM /Online /Cleanup-Health /RestoreHealth[/code]

    If it fails, then please provide the latest CBS log.
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-05-10 07:59:16.095
Microsoft Windows Server 10 Build 14393 - amd64
Using .txt script file at \\asp.stadlander.nl\DFS\Userhome\Administrator\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_none_054fc4877123fa63\v!10.0.14393.4583.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_none_96a6d1b24f36c8e8\v!10.0.14393.4583.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_none_054fc4877123fa63\v!10.0.14393.4583.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_none_054fc4877123fa63\v!10.0.14393.4583.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_none_96a6d1b24f36c8e8\v!10.0.14393.4583.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_none_96a6d1b24f36c8e8\v!10.0.14393.4583.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_none_054fc4877123fa63\v!10.0.14393.4583.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.14393.4650 (rs1_release.210908-1813)\ComponentFamilies\amd64_39be549da278e1ef3b5e19ea2d606ed5_31bf3856ad364e35_none_96a6d1b24f36c8e8\v!10.0.14393.4583.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2022-05-10 07:59:19.543
Script hash: FQrJoY9X0aABbeW9gmopOWyF4x6blzSARSn4yGQlSiU=
[LIST=1]
[*]----------------------EOF-----------------------[/LIST]
 
Run command DISM and the system was healthy.

Try to run the windows updates. This fails again with error code 0x80073701.

The CBS is included.
 

Attachments

Rich (BB code): 
2022-05-10 09:08:45, Error                 CSI    00000012@2022/5/10:07:08:45.967 (F) onecore\base\wcp\componentstore\storelayout.cpp(2617): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  MissingFileSystemResource on resource '\winsxs\manifests\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_10.0.14393.4583_none_76e4ae5aa95741a4.manifest'[gle=0x80004005]

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-05-10 13:12:32.023
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at \\asp.stadlander.nl\DFS\Userhome\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Manifests\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_10.0.14393.4583_none_76e4ae5aa95741a4.manifest to C:\Windows\WinSxS\Manifests\amd64_201a850cf153a6c1ef2fe6cda97ed07b_31bf3856ad364e35_10.0.14393.4583_none_76e4ae5aa95741a4.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2022-05-10 13:13:41.497
Script hash: /Fht1PQUp1wsiUOZPJT+LauGUV6afWqtiD4GSocDVB4=
----------------------EOF-----------------------
 
Could you please open an elevated command prompt and then enter the following command:

Rich (BB code): 
sfc /scannow
 
I'm going to assume that DISM still returns no errors so let's get a ProcMon trace while attempting to update.

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
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