[SOLVED] sfc stuck at 70%

Adityakumar

Adityakumar

Windows Update Trainee
Joined
Jun 18, 2024
Posts
42
Hello @Maxstar ,

Please help me resolve the sfc stuck at 70%.
I found issues with CBS logs as
2024-07-15 14:45:30, Info CSI 0000539d [SR] Cannot repair member file [l:16]'ServiceModel.mof' of NetFx4-ServiceModel_mof_files, version 4.0.15744.1141, arch amd64, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, hash mismatch

Thanks
 
Sure,

Please find all the details below as attached.

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2016 Standard x64 (10.0.14393.7159)
Start time: 2024-07-16T14:04:26
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 244151
Number of values: 611413

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None


Storing 0KB in C:\Users\administrator.IFT\AppData\Local\Sysnative\ComponentsScanner

Finish Time: 2024-07-16T14:42:33. Corruption scan time: 2242.669896s
===========================EOF===========================
 

Attachments

Hi,

Step 1. Download
6530fbb0f4101-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.
650c22f99662d-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. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

Rich (BB code): 
2024-06-21 15:50:00, Error                 CSI    00004eef@2024/6/21:19:50:00.919 (F) onecore\base\wcp\componentstore\deltastore.cpp(3065): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed
[gle=0x80004005]

Please run the System File Checker again with Process Monitor running.

Step1. Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the System File Checker just like you have in the past.
3. Stop Process Monitor a minute after as it fails. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.

Step 2. Upload your COMPONENTS hive.
  • 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.
 
Here's the next fix.

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.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 

Attachments

Hi,

You're welcome. Glad to hear the probldem has been fix, I will mark this thread as solved..(y)
 
Thank you so much!
Just being curious to learn, how we drove this to a resolution. Like analyzing the component file and ProcMon logs and sharing back the registry hive.
 
You must log in or register to reply here.
Back
Top