[SOLVED] SFC stopped at 77%

Herve

Herve

Contributor
Joined
Apr 29, 2020
Posts
32
Location
France, Dinan
Hi all,

I need your expertise.
My server is running Windows Server 2019 Datacenter version 1809 and sfc command stopped at 77%.
I have followed the steps (Windows Update Forum Posting Instructions).
And the results of these one are there : TSTV3-pb sfc - Google Drive
In the shared folders, you can find :
- "cbs.7z"
- "SFCFix.txt"
- "Logfile-sfc stopped at 77pc.PML" (result of Process Monitor)
Thanks for your help.
 
FYI : Process Monitor has been stopped as SFC has stopped at 77% in order to reduce the size of the log file (that remains huge)
 
How long did you let SFC run for? Could you please provide your COMPONENTS hive using the following instructions:

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Thanks, I would have let SFC run for a little longer than that, sometimes it can take a little while to complete. There does seem to be a problem with one of your files though, however, it will be difficult to pinpoint which one if SFC wasn't able to complete properly.
 
OK, I'm going to run again sfc and waiting for 2 minutes after the end of sfc before to stop Process Manager
 
I would let it run for around 15 minutes after it has appeared to become stuck. There's no need to get a Process Monitor trace the second time.
 
I'm not sure to have given to you the right information. sfc doesn't stuck but stops like this :
C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.
Click to expand...
So, here is the cbs files : CBS-new.zip
 
Last edited:
Thanks and that makes much more sense now. I'll have a look into the error for you.
 
Rich (BB code): 
2022-04-12 17:29:14, Error                 CSI    00005c60@2022/4/12:15:29:14.891 (F) onecore\base\wcp\componentstore\deltastore.cpp(3065): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed
[gle=0x80004005]

SFCFixScript.txt

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 attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

    Afterwards, please try and run SFC again.
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-22 19:32:59.242
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\hvmadm\Desktop\ProcessMonitor3.53\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 15 datablocks.
Finish time: 2022-04-22 19:33:00.212
Script hash: DJyuJyG7WmUhZ5vYlSivlnxjtGdKxCzY8kfuHxPmRwU=
----------------------EOF-----------------------
 
Code: 
C:\Windows\system32>sfc /scannow

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.

You are the best ! 100% for sfc.
I'm going to run dism to try to repair
 
Code: 
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2686

[==========================100.0%==========================]
Error: 0x800f0954

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 
I'm using WSUS for this server. So I'm trying this command :
Code: 
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:c:\temp\install.wim:4 /LimitAccess
 
No success :(
Code: 
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:c:\temp\install.wim:4 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2686

[==========================100.0%==========================]
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
 
Here is : CBS-new2.zip
And : DISM.zip
Before your last message, I have launched :
Code: 
C:\Windows\system32>dism.exe /online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2686

[===========================99.0%========================= ]
[==========================100.0%==========================]
The operation completed successfully.
But I have deleted cbs.log, so cbs.log only contains the result of these commands :
Code: 
C:\Windows\system32>sfc /scannow

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.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2686

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

C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>sfc /scannow

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.
 
Your CBS log appears to be clear to me, what happens when you attempt to update?
 
Sorry for the delay.
Update run good.
But I'm a little annoyed by the result of sfc : "Windows Resource Protection found corrupt files but was unable to fix some of them."
Code: 
Microsoft Windows 10 [Version: 10.0.17763.2686]
Reset Windows Update Tool.

Scan your system files and to repair missing or corrupted system files (SFC.exe).


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.

The operation completed successfully.
Here is the last version of the CBS' directory : CBS-new3.zip
 
Rich (BB code): 
2022-04-25 10:25:41, Info                  CSI    000076e6 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-04-25 10:25:41, Info                  CSI    000076e7@2022/4/25:08:25:41.981 Primitive installers committed for repair
2022-04-25 10:25:41, Info                  CSI    000076e8 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
 Expected: {l:32 ml:4096 b:8bbe2742d4284d6a9578cada99243b282e6be6df9a6f796d19e6e72eafa1e382}.
 Actual: {l:32 b:6ddc7a8470d204334a9b520d436e6cf2196cde7687406bc020c06eac6385889a}.
2022-04-25 10:25:41, Info                  CSI    000076e9 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

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. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run SFC /scannow and if it reports no errors, then please attempt to update again.
 

Attachments

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