KB941600 causes sfc.exe /scannow

"nyred" wrote:

> Hi:
> Thanks for IDing the problem. However, what is the solution? If Windows
> Resource Protection found corrupt files but is unable to fix them--where do I
> go from here. Not a developer...just a regular user. XP never gave me
> problems. Vista and IE 8--nightmare. Tried other fixes for "webpage cannot be
> displayed,"Message: Unexpected call to method or property access.
> Line: 264
> Char: 5
> Code: 0
> URI: res://ieframe.dll/httpErrorPagesScripts.js" What does that mean in
> lay terms? How can it be fixed?
>
> Thanks.
>
>
> "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.

Have you tried chkdsk /r /x ? I had the same problem and ran chkdsk and it
seemed to get rid of any SFC.exe error message. It seems to be helpful to
run SFC.exe /scannow in a Safe Mode command prompt window. When that's done,
if you see an error message: "Windows Resource Protection found corrupt files
but was unable to fix some of them," then run CHKDSK /r /x from right there
at the command prompt and answer "Y" to the question about running at boot
time. After that, run SFC again and hopefully you will see no error message
as happend for me.

Best of luck,
Mike