Update error: 80073712. sfcfix crashing

M

mzup

Active member
Joined
May 22, 2020
Posts
28
Hi

Unable to install updates on a windows 2016 server. sfc /scannow runs through and shows corrupt files but unable to fix.
I ran sfcfix.exe and it crashes. I attached the cbs.log and the sfcfix.txt files. I tried running DISM but it got stuck at 34% for over 2 hours.

Not sure what my next step should be.
 

Attachments

This morning the DISM was still stuck at 34%. I ended it and uploaded the log along with a link to components file here

Thanks for any help possible.
 

Attachments

Hello mzup :-) ,

I've looked at your cbs.log file and can see that there are errors associated with some file hash mismatches for three manifest files:

Code: 
2021-08-15 06:52:14, Info                  CSI    000000d7 Manifest hash for component [l:93 ml:140]'amd64_077700722e134a31a2753c1d4362dcba_31bf3856ad364e35_10.0.14393.3930_none_266ace314ad67ee2' does not match expected value.
 Expected:{l:32 b:ee562c65c4955a9e5fcad01ebae8aaf9e015657d3f9fb5870a861145329c06bd}
 Found:{l:32 b:7f9c1656c2dc184b2b4898cef2eae78536242136f28821255a420d1aa031b870}.
2021-08-15 06:52:14, Info                  CSI    000000d8 Looking for manifest in Backup Dir...
2021-08-15 06:52:14, Error                 CSI    000000d9 (F) Unable to load manifest for component [l:93 ml:140]'amd64_077700722e134a31a2753c1d4362dcba_31bf3856ad364e35_10.0.14393.3930_none_266ace314ad67ee2'[gle=0x80004005]
2021-08-15 06:52:14, Error                 CSI    000000da@2021/8/15:10:52:14.442 (F) onecore\base\wcp\componentstore\storelayout.cpp(2581): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource '\winsxs\manifests\amd64_077700722e134a31a2753c1d4362dcba_31bf3856ad364e35_10.0.14393.3930_none_266ace314ad67ee2.manifest'[gle=0x80004005]

2021-08-15 06:54:43, Info                  CSI    000007b6 Manifest hash for component [l:93 ml:140]'amd64_51ffd42e4f2193b4d347a3d808636a19_31bf3856ad364e35_10.0.14393.3930_none_86fe2a6b480e02d5' does not match expected value.
 Expected:{l:32 b:134b27784d1bb8c3510ed7d2c34d3389bc3c509b39c415e0410a174f95408c3f}
 Found:{l:32 b:2a7a3fe8b0bde08c9a0b6131d2b675aa9d00e28ea7473c5864105fad32183aa4}.
2021-08-15 06:54:43, Info                  CSI    000007b7 Looking for manifest in Backup Dir...
2021-08-15 06:54:43, Error                 CSI    000007b8 (F) Unable to load manifest for component [l:93 ml:140]'amd64_51ffd42e4f2193b4d347a3d808636a19_31bf3856ad364e35_10.0.14393.3930_none_86fe2a6b480e02d5'[gle=0x80004005]
2021-08-15 06:54:43, Error                 CSI    000007b9@2021/8/15:10:54:43.540 (F) onecore\base\wcp\componentstore\storelayout.cpp(2581): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource '\winsxs\manifests\amd64_51ffd42e4f2193b4d347a3d808636a19_31bf3856ad364e35_10.0.14393.3930_none_86fe2a6b480e02d5.manifest'[gle=0x80004005]

2021-08-15 06:56:56, Info                  CSI    00000958 Manifest hash for component [l:93 ml:140]'amd64_6163b5aa9db5402db88f06474983ca78_31bf3856ad364e35_10.0.14393.3926_none_da320c20b6fb862f' does not match expected value.
 Expected:{l:32 b:28020e51f74ae77be9382251464342ac2f98b095c87cbc90e678426dcab59565}
 Found:{l:32 b:91553d34b3e85153d8ff1b503fd3b296de22a7f65d32433fd101c1cac1de76a4}.
2021-08-15 06:56:56, Info                  CSI    00000959 Looking for manifest in Backup Dir...
2021-08-15 06:56:56, Error                 CSI    0000095a (F) Unable to load manifest for component [l:93 ml:140]'amd64_6163b5aa9db5402db88f06474983ca78_31bf3856ad364e35_10.0.14393.3926_none_da320c20b6fb862f'[gle=0x80004005]
2021-08-15 06:56:56, Error                 CSI    0000095b@2021/8/15:10:56:56.286 (F) onecore\base\wcp\componentstore\storelayout.cpp(2581): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource '\winsxs\manifests\amd64_6163b5aa9db5402db88f06474983ca78_31bf3856ad364e35_10.0.14393.3926_none_da320c20b6fb862f.manifest'[gle=0x80004005]

I have sourced new manifest files with the correct hashes to replace the ones causing the error and the following fix will add them to your system:

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. Attach this file into your next post for me to analyse please.

Follow this by running a new SFC /scannow and let me know what the outcome is.
Then repeat the DISM restorehealth scan.
If more analysis is required zip up and post the CBS Folder or share it via OneDrive.
 

Attachments

Here is the sfcfix.txt file and a link to the cbs folder. DISM got to 89% and failed at unable to find source.
 

Attachments

The 9 payload corruptions need to be fixed. The manifest corruptions I think are due to old updates not being uninstalled properly.

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. Attach this file into your next post for me to analyse please.

Follow this by running a new SFC /scannow and then repeat the DISM restorehealth scan.
If more analysis is required zip up and post the CBS Folder or share it via OneDrive.
 

Attachments

Sorry I was off on Friday and have not gotten to it. I will today and get back to you.
 
DISM failed again. I went and tried to run update just to see if it would work and it also failed with error 0x800f0900

Here is the cbs log file
 

Attachments

I believe the problem this time is that your system is trying to find old updates which are no longer available. To stop this happening I will need to find and delete the registry keys which are causing this behaviour. The first step is to search your registry for possible keys.

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4580346;KB4577015 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop as a file named SearchReg.txt.
 
Should this be taking over an hour and half to run? It is still searching.
 
mzup said:
Should this be taking over an hour and half to run? It is still searching.
Click to expand...
No it should not take that long. Please check in task manager where you should be able to stop the process.
 
Where you able to complete this? I have a feeling that by asking for the two searches in one go it overwhelmed the system. Please repeat the attempt with just one KB number search at a time and see if this helps. As long as you can see the process is working (via task manager) and not frozen then let the search continue. The search result files generated can be very large.
 
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