View Single Post
  #9 (permalink)  
Old March 28th 08, 01:41 PM posted to microsoft.public.windows.vista.performance_maintenance
Mark@Peterborough
external usenet poster
 
Posts: 1
Default KB941600 causes sfc.exe /scannow

I am getting the same message but don't know if it is valid. Can anyone tell
me how to verify the CBS.log file contains no real errors? There are many
sections stating POQ Start: and POQ Ends with summary information at the end
of each such as:
POQ 73 ends.
2008-03-28 08:00:44, Info CSI 000001d6 [SR] Verify
complete
2008-03-28 08:00:44, Info CSI 000001d7 [SR] Verifying
100 (0x0000000000000064) components
2008-03-28 08:00:44, Info CSI 000001d8 [SR] Beginning
Verify and Repair transaction
2008-03-28 08:00:51, Info CSI 000001d9 Repair results
created:

Thanks Mark.

"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.