Windows 10: SFC not repairing file. Given CBS Error in Details

Hey, I have been having problems updating my computer for awhile pushing them off thinking nothing of it but just recently I was trying to install apps on MC Store and it would not download as well as my Windows Updates, giving me the error 0x800703f1. I did some research and saw that my files might be corrupt so I ran a SFC and indeed they were. System File checker told me they found corrupted files and were unable to repair them so I am trying to repair them manually.Any tips on where to start?

:)

 

Understanding the CBS log & repairing corrupt files

I've been getting some event errors lately, in particular 2 errors.

Date: 10/21/2019 8:54:17 AM
Type: ErrorEvent: 1020Source: Microsoft-Windows-Perflib

The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 34008 and the required size was 45368.

Date: 10/21/2019 2:07:45 PM
Type: WarningEvent: 1008Source: Microsoft-Windows-Perflib

The Open procedure for service ".NETFramework" in DLL "C:\WINDOWS\system32\mscoree.dll" failed with error code The system cannot find the file specified.. Performance data for this service will not be available.

So I went to https://support.microsoft.com/en-us/...rrupted-system and ran

sfc /scannow

I got the message:
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.

I tried to follow the rest of the steps listed on the support page, but got lost in the details.

1. When I used an elevated Powershell & ran the suggested command, I got:

PS C:\> findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

out-file : Could not find a part of the path 'C:\%userprofile%\Desktop\sfcdetails.txt'.At line:1 char:1+ findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\s ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: ) [Out-File], DirectoryNotFoundException + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

2. I manually went to C:\Windows\Logs\CBS & opened CBS.log.There was so much detail that I couldn't follow what was corrupt. I've attached the log.

I would appreciate anyone telling me what files are corrupt & how to replace them. Thank you in advance!

 

SFC reports corrupt files that cannot be repaired

Hi Jay,

For to better assist you with the SFC reports issue, we'd like to know the following:

• Have you installed any Windows updates prior to this issue?
  
• Please provide us a CBS logs for us to determine what is the file that cannot be repaired.
  

To get the logs, please follow the steps below:

• Open a Command Prompt (Admin).
  
• Copy and paste findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfclogs.txt”, then hit
  Enter. (This will create a sfclogs.txt file on your desktop).
  
• Open the sfclogs.txt and check the result of SFC scan.
  

Note: SFC cannot always fix corrupted files.

We're looking forward to your reply.

 

sfc /scannow error

That's why Im asking the question. Am I correct in thinking that its perfectly normal that after the second running of sfc /scannow in your list you would get :-

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired 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.

Then after that..its the third sfc /scannow that you list that comes up clean .
Ivghandi was saying that he presumed that the second sfc /scannow you list showing "Windows Resource Protection found corrupt files and successfully repaired them" meant that he still had a problem.

The way I understand that DISM works is that it repairs the Component Store. Then when you run SFC /scannow again it can then repair the file corruptions it detected originally. Have I got that correct?