The easiest way to access/read the cbs.log file is to simply copy/paste it
into another folder like My Documents. The copy will have no restrictions to
open. You may have to click the Continue button to provide administrator
permission to copy after the Paste command. Works great, but be prepared to
see several entries not covered by the Microsoft KB articles on how to
interpret it.

HMT

"ghrad" wrote:

Kristan -

I received almost the same message . . . albeit my message reads as follows:
"Verification is 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. For example C:\Windows\Logs|CBS\CBS.log" As was the
case with other individuals, I was prevented from reading the log.

Doesn't seem to affect anything, but has MS been able to resolve this issue?

Geoffrey

"Kristan M. Kenney [MVP]" wrote:

Just a heads up, I've noticed on a lot of systems (both 32-bit and 64-bit
Windows Vista, multiple SKU's) that KB941600 causes SFC.EXE /SCANNOW to
report the following:

"Windows Resource Protection found corrupt files but was unable to fix some
of them."

I've reviewed the CBS.log file in accordance to KB928228 and KB929833, and
CBS.log reports that there are no corrupted files. I have also spoken with a
Microsoft Technical Support Professional in regards to this issue for about 6
hours and the only solution is to not install this hotfix (which provides a
baseline quality level for the USB Core Components in Windows Vista).

My question is this- why does this hotfix cause Windows system state
corruption, and is there any other known workarounds for this issue? Also,
has anyone else noticed this behavior after installing KB941600?

Thanks for your time and have a great day,

--
Regards,
Kristan M. Kenney
Microsoft MVP [Windows - Shell/User]

This posting is provided "AS IS" with no warranties, and confers no rights.