Vista - Re: sfc cannot fix errors

To create relevant SFC-only information gleaned from the cbs.log, and put it
in a small file called sfcdetails.txt, open Command Prompt (using the
shortcut in Start Menu\Programs\Accessories). By default, the prompt starts
in C:\Users\(Your Name). Type:

cd desktop

Press Enter on your keyboard. Then Copy and Paste this at the prompt:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

Press Enter. Sfcdetails.txt should then appear on your Desktop.

Looking at entries for the latest date in that
text file , what files are noted as being problematic? From what you
posted, I only see tcpmon.ini and settings.ini, which seem to come up
regularly in cbs.logs that I've seen posted. Settings.ini is a text file
that tells Windows Sidebar what the default settings are for the Sidebar,
should you decide to set everything back to the default. It's not really a
show-stopping file. Tcpmon.ini is kind of a legacy file for older plug and
play printers, again probably not real important. If you wanted, you could
try coping them from another Vista computer, and replace the ones you have.

C:\Program Files\Windows Sidebar\settings.ini
C:\Windows\System32\tcpmon.ini

"arf7ea" <adamfedyk@gmail.com> wrote in message
news:arf7ea.2uvk42@no-mx.tabletquestions.com...
>
> I'm trying to run sfc on my dell pc with vista. I'm getting through sfc
> but at the end it tells me
>
> Verification 99% complete.Windows Resource Protection found corrupt
> files but was unable to fix some of them.
> Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
>
> At the end of the CBS log here's the errors:
>
> 1:53:59, Info CSI 00000288 [SR] Verify complete
> 2007-08-05 21:53:59, Info CSI 00000289 [SR]
> Repairing 2 components
> 2007-08-05 21:53:59, Info CSI 0000028a [SR]
> Beginning Verify and Repair transaction
> 2007-08-05 21:53:59, Info CSI 0000028b Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2007-08-05 21:53:59, Info CSI 0000028c [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2007-08-05 21:53:59, Info CSI 0000028d Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e9c129bd0a02\settings.ini
> do not match actual file [l:24{12}]"settings.ini" :
> Found: {l:32 b:zROVK9Mfp77kOMRFbV0UIrKe21a++Wg54PRgEPEEsMg=}
> Expected: {l:32 b:40ijQez8dnId2/xBxTWnf/gsCddJvRLR5cH9MDStaEu=}
> 2007-08-05 21:53:59, Info CSI 0000028e [SR] Cannot
> repair member file [l:24{12}]"settings.ini" of
> Microsoft-Windows-Sidebar, Version = 6.0.6000.16386, pA =
> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
> nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
> TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2007-08-05 21:53:59, Info CSI 0000028f Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
> do not match actual file [l:20{10}]"tcpmon.ini" :
> Found: {l:32 b:0cSv9zUxBdxIACUdN3TVidA8dd5qeWe9Ct2GEzhrLi5=}
> Expected: {l:32 b:Uu3AaPzr3p1NNnR6zY6aW6nbeOxBy6AP9XHSLyFUjD9=}
> 2007-08-05 21:53:59, Info CSI 00000290 [SR] Cannot
> repair member file [l:20{10}]"tcpmon.ini" of
> Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version =
> 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral,
> VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type
> neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2007-08-05 21:53:59, Info CSI 00000291 Hashes for
> file member
> \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e9c129bd0a02\settings.ini
> do not match actual file [l:24{12}]"settings.ini" :
> Found: {l:32 b:zROVK9Mfp77kOMRFbV0UIrKe21a++Wg54PRgEPEEsMg=}
> Expected: {l:32 b:40ijQez8dnId2/xBxTWnf/gsCddJvRLR5cH9MDStaEu=}
> 2007-08-05 21:53:59, Info CSI 00000292 [SR] Cannot
> repair member file [l:24{12}]"settings.ini" of
> Microsoft-Windows-Sidebar, Version = 6.0.6000.16386, pA =
> PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1
> nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral,
> TypeName neutral, PublicKey neutral in the store, hash mismatch
> 2007-08-05 21:53:59, Info CSI 00000293 Repair
> results created:
> POQ 115 starts:
>
> POQ 115 ends.
> 2007-08-05 21:53:59, Info CSI 00000294 [SR] Repair
> complete
> 2007-08-05 21:54:00, Info CSI 00000295 [SR]
> Committing transaction
> 2007-08-05 21:54:00, Info CSI 00000296 Creating NT
> transaction (seq 2), objectname [6]"(null)"
> 2007-08-05 21:54:00, Info CSI 00000297 Created NT
> transaction (seq 2) result 0x00000000, handle @0x11b8
> 2007-08-05 21:54:00, Info CSI
> 00000298@2007/8/6:02:54:00.09 CSI perf trace:
> CSIPERF:TXCOMMIT;3
> 2007-08-05 21:54:00, Info CSI 00000299 [SR] Verify
> and Repair Transaction completed. All files and registry keys listed in
> this transaction have been successfully repaired
>
>
> If someone tells me how I'll post the entire CBS log file. Thanks for
> any help you can give.
>
>
> --
> arf7ea

That's possibly quite a hefty file to copy ; )

Try this first. When you open Command Prompt, right-click on it and choose
Run as Administrator. Then follow the instructions in my previous post.

If that doesn't work, for you desktop cbs.log, type:

cd desktop

Press Enter, then Copy and Paste:

findstr /c:"[SR]" %userprofile%\desktop\cbs.log >sfcdetails.txt

Press Enter. Sfcdetails.txt should then appear on your desktop.



"arf7ea" <adamfedyk@gmail.com> wrote in message
news:arf7ea.2uxb2v@no-mx.tabletquestions.com...
>
> Thanks fellas. I haven't noticed any problems, I just run sfc from time
> to time as a general diagnostic tool. This was the first time I
> encountered any errors.
>
> As for your tip dean, I find myself having "access denied" to my CBS
> log file under the Windows folder. I had to copy the file to the
> desktop to be able to open it. Knowing that, what should I type at the
> command prompt to create sfcdetails.txt? Thanks.
>
>
> --
> arf7ea