CBS & SFC total detected corruption count: 4

[fraXis]

Hello,

Can you please analyze my information and tell me if this is repairable or something that I do not need to worry about?

Thanks.



SFCFix version 2.0.2.1 by niemiro.
Start time: 2013-11-14 03:32:05.942
Not using a script file.








AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 4
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2013-11-14 03:32:33.486
----------------------EOF-----------------------

 

[NoelDP]

Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[fraXis]

Hi Noel. Here is my CheckSUR.log file.

Thanks.

Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[NoelDP]

CheckSUR managed to fix the only problem it found...

Checking Component Store
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\x86_microsoft-windows-i..odepage-57002-57011_31bf3856ad364e35_6.1.7601.17514_none_3b7302d236956600.manifest x86_microsoft-windows-i..odepage-57002-57011_31bf3856ad364e35_6.1.7601.17514_none_3b7302d236956600 
(fix) CSI Manifest Failed Catalog Check CSI File Replaced File: x86_microsoft-windows-i..odepage-57002-57011_31bf3856ad364e35_6.1.7601.17514_none_3b7302d236956600.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-neutralcab-v2.cab
Summary:
Seconds executed: 77
 Found 1 errors
 Fixed 1 errors
  CSI Manifest Failed Catalog Check Total count: 1
  Fixed: CSI Manifest Failed Catalog Check.  Total count: 1

This has repaired the fie that the SFC was complaining about, so now we need to check that it hasn't brought any more errors to light - run another SFC /SCANNOW and see what it reports now - with any luck it will say 'no errors found'. If not, post the new CBS.log file.