[SOLVED] SFCFix.exe crashes every time I run it.

[tnarduzzi]

I am having a problem with a manifest corruption that DISM cannot seem to repair. I keep getting DISM error 0x800f081f "The source files could not be found.".

I tried running SFCFix.exe without any scripted file, just the base exe as downloaded here: SFCFix Official Download - Repair Windows Update

On first run SFCFix errored out on stage 1, then proceeded through stages 2 to 5, and then encountered an unhandled exception on stage 6 and completely shut down with this message:

SFCFix Has Crashed


Something has gone horribly wrong and SFCFix has crashed. Would you like SFCFix
to submit a crash report to the developer so that this problem can be fixed?
Type "y" for yes or "n" for no and press enter to continue:

Ever since this first run during which crashed, now when I open SFCFix.exe it crashes each time immediately upon launch. The same error appears:

SFCFix Has Crashed


Something has gone horribly wrong and SFCFix has crashed. Would you like SFCFix
to submit a crash report to the developer so that this problem can be fixed?
Type "y" for yes or "n" for no and press enter to continue:

Please help.
I have provided an excerpt below of the errors I am seeing in CBS.log after I run "DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:"E:\Sources\Install.wim":1 /limitaccess".

CBS.log after running DISM:


=================================
Checking System Update Readiness.

(p)    CSI Manifest Corrupt            x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_10.0.14393.3750_en-gb_315b74dbcd2b012c
Repair failed: Missing replacement manifest.
(p)    CSI Manifest Corrupt            wow64_microsoft-windows-directui.resources_31bf3856ad364e35_10.0.14393.3750_zh-tw_5184c287599677d7
Repair failed: Missing replacement manifest.
(p)    CSI Manifest Corrupt            amd64_microsoft-windows-comdlg32.resources_31bf3856ad364e35_10.0.14393.3750_ar-sa_cbd78c7d05ab8a8e
Repair failed: Missing replacement manifest.
(p)    CSI Manifest Corrupt            x86_microsoft-windows-b..ager-pcat.resources_31bf3856ad364e35_10.0.14393.3750_el-gr_38898793c88b11ba
Repair failed: Missing replacement manifest.

Summary:
Operation: Detect and Repair
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption:    4
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    4
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    0
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Total Operation Time: 886 seconds.

 

[tnarduzzi]

My results as per the instructions here: Windows Update Forum Posting Instructions


STEP 1: Run SFC

C:\>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

STEP 2: Run DISM

C:\>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.3241

Image Version: 10.0.14393.3241

[===========================91.6%=====================     ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

STEP 3: Run ComponentsScanner

Text output attached.


STEP 4: Export CBS logs

ZIP file attached.

 

[Gary R]

Hi I'm Gary R,

I'm a Security Analyst, and a Windows Update Trainee, and I'd like to help you with your problems.

As a trainee, any instructions I give you must first be checked by a qualified update expert, before I post them. This will by necessity introduce some delay to any of my replies, so please be patient.

I am looking over your logs now, and will be back as soon as I've finished analysing them.

 

[tnarduzzi]

Thank you Gary. To update, the following actions seem to have resolved the final 4 remaining CSI manifest corruptions and allowed updates to install without error.


Actions taken:

- ran Microsoft Office 2016 ProPlus "repair" function via the GUI available at appwiz.cpl > Office 2016 > Change > Repair, and then allowed the wizard to complete without error

- restarted computer

- ran cmd as admin:

sfc /scannow

- SFC result:

C:\>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

- deleted registry key:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate

- ran cmd as admin:

net stop wuauserv
net start wuauserv

- ran cmd as admin:

DISM /Online /Cleanup-Image /RestoreHealth

- DISM result:

C:\>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

- CBS.log after DISM result:

2022-09-30 02:37:38, Info                  CBS   
=================================
Checking System Update Readiness.


Summary:
Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:    0
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    0
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Total Operation Time: 947 seconds.

It appears all corruptions are now resolved - the computer is accepting updates via SCCM without further error.

If I had to guess I would wager that the 4 corrupt manifests were perhaps for MS Office language packs or something similar? And perhaps repairing Office provided the source? If not Office related, then deleting the WU registry key allowed DISM to retrieve the corrupt manifest from MS servers directly? Tbh I am not sure which was the true answer as both happened at once.

 

[Gary R]

Glad to hear you were able to resolve your problem. I'll mark this topic as resolved.

Corrupted manifest files were all from update KB4561616 and it's not entirely clear to me what their exact purpose was, though they were certainly language related.