Windows 10: Help SFC /Scannow Found Corrupt Files CBS Log Attached

I will list all my system details below that are relevant unless more are requested. I keep getting an error when shutting my system down I use the Power > Shutdown method. I ran sfc /scannow to find the issue and found that there are corrupt files in my system. To counteract those I ran the DISM commands DISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanup-Image /RestoreHealthBoth 'successfully' completed the process of repairing the corrupted files but upon running sfc /scannow again, more corrupted files were found. Attached is my sfc /scannow command line and the CBS logMy sy

:)

 

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!

 

Ran sfc /scannow. Found corrupt files.

Hi,

I ran sfc /scannow on my Windows 10 desktop and got the response below:

Microsoft Windows [Version 10.0.17134.523]

(c) 2018 Microsoft Corporation. All rights reserved.

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.

Did not find any "log" from the directions above.

Please help,

Thanks,

Joe

 

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?