Sfc scannow - cannot repair file

SFc scannow is reporting that the system cannot repair some corrupt files.
From reading the CBS log I found this entry:

CSI 0000001d [SR] Cannot verify component files for
3c52bd14fb076de75da14b4b67a96f83, Version = 6.0.6000.16720, pA =
PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS,
PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral,
PublicKey neutral, manifest may be damaged (TRUE)

Any idea what's causing this and how this can be fixed?? thanks.

Hi,

Looks like a temp file couldn't be repaired, nothing that should be of
concern. The long string of characters is usually the result of a temp setup
file for a service pack update, normally these are deleted at the end of the
install process but in some systems they remain behind.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
Vote for my shoe: http://rick-mvp.blogspot.com

"Carm" <> wrote in message
news:0CF22106-0F32-47BB-AED5-...
> SFc scannow is reporting that the system cannot repair some corrupt files.
> From reading the CBS log I found this entry:
>
> CSI 0000001d [SR] Cannot verify component files for
> 3c52bd14fb076de75da14b4b67a96f83, Version = 6.0.6000.16720, pA =
> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
> nonSxS,
> PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral,
> PublicKey neutral, manifest may be damaged (TRUE)
>
> Any idea what's causing this and how this can be fixed?? thanks.

Thanks for your reply - is there any way this temp file can be deleted??

"Rick Rogers" wrote:

> Hi,
>
> Looks like a temp file couldn't be repaired, nothing that should be of
> concern. The long string of characters is usually the result of a temp setup
> file for a service pack update, normally these are deleted at the end of the
> install process but in some systems they remain behind.
>

Hi,

If you can locate it, the whole temp folder from the setup can be deleted.
Usually it's on the root of the drive, but you may also be under the windows
or software distribution directories. You will likely need to change
permissions on the folder to remove it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
Vote for my shoe: http://rick-mvp.blogspot.com

"Carm" <> wrote in message
news:8DFCA6A7-636D-45FB-A236-...
> Thanks for your reply - is there any way this temp file can be deleted??
>
> "Rick Rogers" wrote:
>
>> Hi,
>>
>> Looks like a temp file couldn't be repaired, nothing that should be of
>> concern. The long string of characters is usually the result of a temp
>> setup
>> file for a service pack update, normally these are deleted at the end of
>> the
>> install process but in some systems they remain behind.
>>
>

Carm wrote:
> SFc scannow is reporting that the system cannot repair some corrupt files.
> From reading the CBS log I found this entry:
>
> CSI 0000001d [SR] Cannot verify component files for
> 3c52bd14fb076de75da14b4b67a96f83, Version = 6.0.6000.16720, pA =
> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS,
> PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral,
> PublicKey neutral, manifest may be damaged (TRUE)
>
> Any idea what's causing this and how this can be fixed?? thanks.


Before running SFc scannow, delete your old CBS.log (and
CBS.persist.log) files.

You will get a clean bill of health. No false positives about not being
able to repair "corrupt" files. A new CBS.log will be generated.

If the new scan shows errors, those would be real problems to track down
in the log.

NetLink_Blue