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

difun

difun

Member
Joined
Aug 10, 2022
Posts
14
Hi,
got this error on every try. Other Windows Updates can be installed.
sfc /scannow - ok
Dism /Online /Cleanup-Image /RestoreHealth - ok
SFCFix runs up to Dism and doesn't terminate with logfile.

I hope you can help. I want to avoid a completely new installation.

Many Thanks!
 

Attachments

Rich (BB code): 
2022-08-11 11:31:20, Info                  CSI    00000007 Warning: Unable to repair manifest for component ([l:93 ml:140]'amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-11 11:31:43, Info                  CSI    00000008 Warning: Unable to repair manifest for component ([l:93 ml:140]'amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_10.0.17763.2510_none_c8bcf1cfe91e3b53') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-11 11:32:00, Info                  CSI    00000009 Warning: Unable to repair manifest for component ([l:93 ml:140]'amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_10.0.17763.2510_none_6ca9f63174ec5c5a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-11 11:32:22, Info                  CSI    0000000a Warning: Unable to repair manifest for component ([l:93 ml:140]'amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-08-11 11:33:00, Warning               CBS    Current tick count: 800 lower than last tick count: 1049. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-08-11 11:33:00, Error                 CSI    0000000b@2022/8/11:09:33:00.818 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2022-08-11 11:33:00, Info                  CSI    0000000c@2022/8/11:09:33:00.881 Corruption detection complete. numCorruptions = 4, Disp = 1.

Rich (BB code): 
2022-08-11 11:33:01, Info                  CBS    Repr: No owner found for component amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Not able to get CBS component onwers for component amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble
2022-08-11 11:33:01, Info                  CBS    Repr: No owner found for component amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_10.0.17763.2510_none_c8bcf1cfe91e3b53, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Not able to get CBS component onwers for component amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_10.0.17763.2510_none_c8bcf1cfe91e3b53 [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble
2022-08-11 11:33:01, Info                  CBS    Repr: No owner found for component amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_10.0.17763.2510_none_6ca9f63174ec5c5a, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Not able to get CBS component onwers for component amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_10.0.17763.2510_none_6ca9f63174ec5c5a [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble
2022-08-11 11:33:01, Info                  CBS    Repr: No owner found for component amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Not able to get CBS component onwers for component amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2022-08-11 11:33:01, Info                  CBS    Repr: Non CBS installed component found, ignore it since it is not repairble

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 WeTransfer and then just provide the link in your reply.
 
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.

Afterwards, please attempt to update again and attach the latest CBS logs if it fails.
 

Attachments

Update error persists unfortunately.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-18 07:29:54.141
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\XXX.XXX\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_10.0.17763.2510_none_6ca9f63174ec5c5a.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_10.0.17763.2510_none_c8bcf1cfe91e3b53.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_10.0.17763.2510_none_6ca9f63174ec5c5a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_10.0.17763.2510_none_c8bcf1cfe91e3b53.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.3100 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2980 (WinBuild.160101.0800)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_none_c7fd12e4decab46f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_c2e9564e7802ad35b7d619dc556851c0_31bf3856ad364e35_none_38cb6e6c67c397e5\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_none_4318fffb42f7257f\v!10.0.17763.2452.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474\v!10.0.17763.2510.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies\amd64_6f403e168a541a5086d1c16a5ceb74a4_31bf3856ad364e35_none_2236b541b02fd474.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\10.0.17763.2744 (WinBuild.160101.0800)\ComponentFamilies.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 23 datablocks.
Finish time: 2022-08-18 07:30:01.719
Script hash: W4Rh+2GqYMTVVmjTS/VR0fIfoONqu+pZqjhqooN4XxI=
----------------------EOF-----------------------

Thanks!
 
Rich (BB code): 
2022-08-18 08:09:27, Error                 CSI    000016ab@2022/8/18:06:09:27.375 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3604): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3'[gle=0x80004005]

The same instructions as before please!
 

Attachments

Same error as before. Tried update installation 2x, first after SFCFixScript, second after reboot.
New CBS.zip

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-18 10:29:15.674
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\XXX.XXX\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 24 datablocks.
Finish time: 2022-08-18 10:29:15.846
Script hash: J58Z49z+2ZMSA05gTIR9/wKAM695aX2gCCtbuE7u//s=
----------------------EOF-----------------------
 
Rich (BB code): 
2022-08-18 10:55:19, Error                 CSI    00001693 (F) HRESULT_FROM_WIN32(14098) #6826956# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_EnumMissingComponents(Flags = 0, ppe = NULL, disp = 0)[gle=0x80073712]
2022-08-18 10:55:19, Error                 CSI    00001694 (F) HRESULT_FROM_WIN32(14098) #6826955# from Windows::ServicingAPI::CCSITransaction_ICSITransaction::EnumMissingComponents(flags = 0, enum = NULL, disp= 0)
[gle=0x80073712]
2022-08-18 10:55:19, Info                  CBS    Failed to get enumerator for missing components. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-08-18 10:55:19, Error                 CBS    Failed to complete component closure [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

It's a different error this time though, one which usually means there's potentially lots of missing subkeys from your COMPONENTS hive. Could you please try and update your system again but with a Process Monitor trace running? Please see the instructions below.

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.
 
Thanks, there seems to be about 2.3k missing component subkeys and 1.7k missing deployment subkeys. It will take far too long for SFCFix to repair it itself so could you please provide your latest COMPONENTS hive and then I'll give you the repaired version afterwards?
 
Yes of course, but how can something like that happen?
I ran sfc /scannow today, now errors are detected but not repaired. I hope this ist not a problem, new cbs.log attached. I did'nt tried windows update installation.
 

Attachments

Thank you, I'll take a look into this for you.

dfunke said:
Yes of course, but how can something like that happen?
Click to expand...
There could be lots of different reasons: improper shutdowns; crashes during an update or a servicing stack operation; third-party clean up programs including defragmentation software; anti-virus software (usually avast) crashing during an update; failing HDD/SSD.
 
Please create a suitable backup of your current COMPONENTS hive and then replace your hive with the attached one. Once replaced, then please open an elevated command prompt and then enter the following command:

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

Please ensure that you do this while you have a Process Monitor trace running. Once complete either successfully or not, then please upload the CBS log(s) along with the Process Monitor log file.
 

Attachments

Rich (BB code): 
2022-08-22 07:28:54, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d
2022-08-22 07:28:54, Info                  CBS    Repair failed: Missing replacement manifest.
2022-08-22 07:28:54, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3
2022-08-22 07:28:54, Info                  CBS    Repair failed: Missing replacement manifest.
2022-08-22 07:28:54, Info                  CBS    (p)    CSI Manifest Corrupt    (n)            amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d
2022-08-22 07:28:54, Info                  CBS    Repair failed: Missing replacement manifest.

I've also made significant repairs to your COMPONENTS hive again so DISM will probably throw far more errors on your next run. Please follow these steps:
  1. Replace your current COMPONENTS hive with the one attached
  2. Please run the attached SFCFix, this will replace the corrupted/missing manifest files shown above
  3. Run the same DISM command as before (/RestoreHealth) and then attach: your latest COMPONENTS hive, the CBS log(s) and the latest Process Monitor log
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

I did the steps as specified.
Now DISM RestoreHealth stopped at 90.0% with error 0x800f0954.
CBS, PMLogfile, COMPONENTS

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-08-23 09:13:31.540
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\XXX.XXX\Desktop\SFCFix.zip [0]




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

Successfully copied file C:\Users\XXX.XXX\AppData\Local\niemiro\Archive\Manifests\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d.manifest to C:\Windows\WinSxS\Manifests\amd64_086e424970790424a57d8ce48f12b8e4_31bf3856ad364e35_10.0.17763.2452_none_52080a8d45a0d82d.manifest.
Successfully copied file C:\Users\XXX.XXX\AppData\Local\niemiro\Archive\Manifests\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d.manifest to C:\Windows\WinSxS\Manifests\amd64_faf64bb5157a1cce76a4fd2e703d1e01_31bf3856ad364e35_10.0.17763.2452_none_c66596e3c010de9d.manifest.
Successfully copied file C:\Users\XXX.XXX\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-font-fms.resources_31bf3856ad364e35_10.0.17763.2510_bg-bg_619d420904084be3.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 25 datablocks.
Finish time: 2022-08-23 09:14:11.962
Script hash: l2htC4v367wpdp8I2WvJgfqmUa8f5CfFnbzossidR08=
----------------------EOF-----------------------
 
Is there still a chance to fix the update error quickly? Otherwise I would start with the new installation asap.
Thanks!
 
Unfortunately, I can only repair what is shown in the CBS log(s) and sometimes make some educated assumptions if there is a pattern to the errors. Here's the latest SURT log section from your CBS log:

Rich (BB code): 
2022-08-23 09:27:42, Info                  CBS    Summary:
2022-08-23 09:27:42, Info                  CBS    Operation: Detect and Repair 
2022-08-23 09:27:42, Info                  CBS    Operation result: 0x800f0954
2022-08-23 09:27:42, Info                  CBS    Last Successful Step: Entire operation completes.
2022-08-23 09:27:42, Info                  CBS    Total Detected Corruption:    6136
2022-08-23 09:27:42, Info                  CBS        CBS Manifest Corruption:    0
2022-08-23 09:27:42, Info                  CBS        CBS Metadata Corruption:    0
2022-08-23 09:27:42, Info                  CBS        CSI Manifest Corruption:    230
2022-08-23 09:27:42, Info                  CBS        CSI Metadata Corruption:    0
2022-08-23 09:27:42, Info                  CBS        CSI Payload Corruption:    5906
2022-08-23 09:27:42, Info                  CBS    Total Repaired Corruption:    0
2022-08-23 09:27:42, Info                  CBS        CBS Manifest Repaired:    0
2022-08-23 09:27:42, Info                  CBS        CSI Manifest Repaired:    0
2022-08-23 09:27:42, Info                  CBS        CSI Payload Repaired:    0
2022-08-23 09:27:42, Info                  CBS        CSI Store Metadata refreshed:    True

I'll be able to provide you with all of those files in one fix, however, I'm going to attach it to my Google Drive since it is too large for a forum post. Your COMPONENTS hive seems to be much better, I can't see any additional errors this time. I'm waiting for files to finish gathering on my VM and then I'll provide you with the Google Drive link. DISM may fail afterwards because of the corrupted manifest files, however, if it does fail, then it should be the final DISM fix at least.
 
The fix script is about 823MB in size so it will take some time for SFCFix to complete. Once complete, then please run DISM again and then attach the CBS log(s).

The fix is available from my Google Drive and simply called SFCFix.zip.
 
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