SFCFix Crashes

lp1406

New member
Joined
May 23, 2022
Posts
2
Greetings,

Underlying symptom is that Windows 10 LTSB 1607 does not update.
SFC /scannow reports errors that it cannot fix.
DISM reports that the erros are repairable but then says that the system does not have enough storage to fix them. I'm running with 8Gb RAM on an LTSB system.

'Dism.exe /online /Cleanup-Image /StartComponentCleanup' corrected some errors so that Windows is now able to locate and install some very minor updates but nothing significant.

SFCFix reports " SFCFix Has Crashed Something has gone horribly wrong and SFCFix has crashed..." Screenshot attached

Attached files:
1. SFCFix crash report log
2. CBC.log from SFC /scannow. Essentially, the log appears to show problems with corrupted Windows Defender files
3. DISM log
4. SFCFix Crash Dump Report. Unfortunately, this is 59,642kb and the website reports that it is too large to attach. I have sent the report direct from the failure reporting process (as shown on screenshot)

Thanks for help and BR,

lp1406

1653329262714.png
 

Attachments

Hi and welcome to Sysnative,

Step 1. Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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 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
  • Take a screenshot of the commandprompt window and paste it into your next reply.


Step 3. Export CBS (Component Based Servicing) 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\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (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.
 

Attachments

Hello and thank-you, Maxstar.

I've followed your instructions - the following files are attached:
1. SFCFix.txt logfile
2. 2 screenshots of command prompt window showing results from 3 attempts at running sfc /scannow (see comments below)
3. Exported ComponentBasedServicing registry hive file

WHATEVER YOU HAVE DONE APPEARS TO ENABLED SFC /SCANNOW TO RUN SUCCESSFULLY - THANK YOU. I'd be delighted to know what youlve done to fix it.

Other info:
1. First attempt at running sfc /scannow (as per your instructions) resulted in the system hanging @ verification phase 9% complete - Screenshot attached. CPU, Memory and Disk usage stats were all satisfactory. CBS log shows:
At 16:34 hrs "TI: --- Initializing Trusted Installer ---"
At 16:39 hrs "Ending TrustedInstaller finalization"
At 17:55 hrs "TI: --- Initializing Trusted Installer ---" [THE SYSTEM APPEARS TO HAVE AUTOMATICALLY COMMENCED A NEW SESSION ~76 MINS AFTER PREVIOUS SESSION FINALIZED]
At 18:03 hrs "Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
By 19:15 hrs, CBS.log did not contain any additional entries so I manually closed the command prompt window at ~19:19 hrs.
2. Second attempt at running sfc /scanow @ ~19.25 hrs reported:
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Another servicing or repair operation is currently running.
Wait for this to finish and run sfc again.
It would appear that the operations kicked back into life around the time that I closed the cmd window
3. Third attempt at running sfc /scanow commenced at 20:10 hrs and completed successfully at 20:10 hrs. Attached CBS.log file.
4. Having successfully completed the above, the underlying symptom remains: Windows 10 LTSB 1607 does not update - it thinks the updates are not applicable to this computer.
 

Attachments

  • SFCFix.txt
    SFCFix.txt
    16.5 KB · Views: 3
  • Screenshot - scannow successful - 2022-05-31 202303.JPG
    Screenshot - scannow successful - 2022-05-31 202303.JPG
    24.6 KB · Views: 3
  • Screenshot - scannow stuck at 9% - 2022-05-31 183847.JPG
    Screenshot - scannow stuck at 9% - 2022-05-31 183847.JPG
    21.8 KB · Views: 2
  • ComponentBasedServicing.zip
    ComponentBasedServicing.zip
    59.3 KB · Views: 2
  • CBS.log
    CBS.log
    43.8 KB · Views: 1
Hi,

The Component Based Servicing hive is damaged beyond repair. The only way to resolve this issue is to perform a repair or clean install.

Windows 10 Repair Install
This will reinstall and update the operating system and fix any corruptions, without removing any file or program. But make always a backup of all your important data!
  • Go to this Microsoft page and under the title Create Windows 10 installation media press on Download tool now.
  • Save the tool on your Desktop and double click to run it.
  • On the License terms page, if you accept the license terms, select Accept.
  • On the What do you want to do page, select Create installation media (USB....) and then select Next.
  • Choose the ISO file option. Once the download is complete, right click the ISO and select the option Mount.
  • Open the Windows File Explorer and open mounted ISO, and run the setup.exe file.
  • Follow the instructions and click on the option Change what to keep.
  • Select the option Keep personal files and apps and click next.
  • Windows Setup will now start the in-place upgrade installation to repair Windows.
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top