Windows 10: 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!

:)

 

Corrupted file RAR

If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:

• Open WinRAR application in your system.
• Now click on File tab > Open or simply press Ctrl+O.
• A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
• Now click Open button.
• Click Tools tab > Repair archive or simply press Alt+R.
• Again a small window "Repairing File name.rar" will pop up.
• Now click Browse to select a location to save the repaired archive.
• Check the box "Treat the corrupt archive as RAR" and click OK.
• WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.

I hope the above steps will help you repair the corrupted RAR archive.

Thanks.

 

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 Corrupt Files

Nope, ran sfc /scannow and it stopped at 72%. The log file is attached.