[SOLVED] SFCFix crashes

chucker · Feb 21, 2022

Windows Update is failing with 0x80073712, which sent me down a rabbit hole of…

Trying sfc /scannow:

Code:

Beginning system scan.  This process will take some time.

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

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Trying various variants of DISM /Online /Cleanup-Image /RestoreHealth (this fails to find the .wim, even when I specify one; I'm not entirely sure how to find out which exact ISO I need?).
Ultimately discovering SFCFix

However, that crashes, and I think it happens as it's trying to parse CBS.log. So I'm attaching that and the crash dump.

I'm a bit puzzled by the mechanisms here. CBS.log has lines like:

Code:

2022-02-21 17:36:17, Info                  CSI    00000100 [SR]
Cannot verify component files for Microsoft-Windows-ServicingStack-Installers-OneCore, version 10.0.19041.1371,
arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)

OK, so a bunch of manifests are damaged. But why can't it simply replace those with the original manifests from Microsoft, then?

Anyway, I'd appreciate any help repairing this — installing Windows all over again doesn't sound like a fun way to spend the weekend. :)

chucker · Feb 21, 2022

I see I need to attach the entire Logs\CBS folder. Here goes!

Maxstar · Feb 22, 2022

Hi and welcome to Sysnative,

I will look into your problem.
Note: I'm currently in training so my posts will need to be approved by the Sysnative instructors.

Maxstar · Feb 22, 2022

Hi,

Step 1. Run SFCFix again.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Reboot the computer and run the System File Checker.

Click the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator.
When command prompt opens, copy and paste the following command into it, and press enter.
Code:
```
sfc /scannow
```
Wait for this to finish before you continue
Now copy and paste the following command into it, and press enter.
Code:
```
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
```
This command will create cbs.txt on your Desktop. Zip this file and attach the zipped cbs.txt to your next post.

chucker · Feb 22, 2022

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-22 11:54:36.975
Microsoft Windows 10 Build 19043 - amd64
Using .zip script file at C:\Users\kuklau\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1371_none_6078e65f5a9e7590.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1371_none_5ecb42713261961f.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1371_none_ca83999d25b31307.manifest
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1371_none_37a2c565c02e2c73.manifest

Successfully copied file C:\Users\kuklau\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1371_none_6078e65f5a9e7590.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1371_none_6078e65f5a9e7590.manifest.
Successfully copied file C:\Users\kuklau\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1371_none_5ecb42713261961f.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1371_none_5ecb42713261961f.manifest.
Successfully copied file C:\Users\kuklau\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1371_none_ca83999d25b31307.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1371_none_ca83999d25b31307.manifest.
Successfully copied file C:\Users\kuklau\AppData\Local\niemiro\Archive\Manifests\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1371_none_37a2c565c02e2c73.manifest to C:\Windows\WinSxS\Manifests\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1371_none_37a2c565c02e2c73.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1371_none_6078e65f5a9e7590.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.19041.1371_none_6078e65f5a9e7590.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1371_none_5ecb42713261961f.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..formers-shell-extra_31bf3856ad364e35_10.0.19041.1371_none_5ecb42713261961f.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1371_none_ca83999d25b31307.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..gstack-boot-onecore_31bf3856ad364e35_10.0.19041.1371_none_ca83999d25b31307.manifest
Successfully restored ownership for C:\Windows\WinSxS\Manifests\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1371_none_37a2c565c02e2c73.manifest
Successfully restored permissions on C:\Windows\WinSxS\Manifests\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.19041.1371_none_37a2c565c02e2c73.manifest
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2022-02-22 11:54:38.720
Script hash: O408C43ZS3jE0l/R4RPFaCt+E7h1J9bGn9o9iuR9MyI=
----------------------EOF-----------------------

sfc /scannow output:

Code:

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.

chucker · Feb 22, 2022

That looked good to me, so I tried running Windows Update afterwards.

The update went further than before, but after a reboot, there's "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0xe0000100)"

Maxstar · Feb 22, 2022

Please run the following two commands in an elevated commandprompt and attach cbs.txt and Setupapi.dev.txt to your next reply.

Code:

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
copy %windir%\INF\setupapi.dev.log "%userprofile%\Desktop\Setupapi.dev.txt"

chucker · Feb 22, 2022

Here you go.

Maxstar · Feb 22, 2022

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Right-click on the file FRST64.exe and choose Run as administrator.

Copy and paste the following (code) into the Search box and click the Search Files button.

Code:

prnms002.inf

When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
Post the logfile Search.txt as attachment in your next reply.

chucker · Feb 22, 2022

(I looked at some of the paths that say "File not signed", and… yeah, those files seem garbled.)

Maxstar · Feb 22, 2022

Hi,

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFixScript.txt and save it to your desktop.
Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

chucker · Feb 22, 2022

SFCFix:

Maxstar · Feb 22, 2022

Run Windows Update again and let me know the result. If it fails perform the staps in post#7 and attach both logfiles in your next post...

chucker · Feb 22, 2022

(WU failed with 0xe0000100)

Maxstar · Feb 22, 2022

Export SBS hive

Click on the Start button and 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.
Code:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
```
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (.).
Name this file SideBySide (with no file extension) and save it to your Desktop.
Right-click on the saved file and choose Send > Compressed (zipped) Folder.
Attach the .ZIP file to your next post.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

chucker · Feb 22, 2022

SideBySide:

Maxstar · Feb 23, 2022

Hi,

Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
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.
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.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

chucker · Feb 23, 2022

COMPONENTS:

Maxstar · Feb 23, 2022

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFixScript.txt and save it to your desktop.
Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Reboot the system and run Windows Update again and let me know the result.

chucker · Feb 23, 2022

Hmm, I ran it (see attachment), but that script seems identical to post #11

[SOLVED] SFCFix crashes

Member

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments