SFC/scannow

Thanks Paws for all your input, much appreciated. Tom, are we still using OTLPE ?????

Thanks Paws for all your input, much appreciated.

Tom, are we still using OTLPE ?????

No… I guess not. I forgot.

I sent OT a PM both here and at BC and asked him what he thought

From OT Hey ken545. Because it's failing on the kernel32.dll module my guess would be that that is where the issue is. It would be interesting to get the details on that file (date/time, size, version, MD5). The tools load a copy of kernel32.dll when they start up and use a number of its internal function calls. If you really want to run OTL then I would use OTLPE until you can get the machine to a stable running state. Cheers. OT

From OT Hey ken545. That appears to be a valid version of kernel32.dll so there is something else amiss with that user's system but I don't know exactly what that might be. They are either missing some system component or some component has been compromised. Cheers. OT

Sounds like your back to… "How do we make SFC run?"

This is what i would do: 1. Back-up 2. Nuke and Pave

When you run windows updates does it not add the new updates to the I386 folder as well, if it does and the sourcepath is correct why is it asking her for the Windows Pro XP 3 disk ?

Ken, that's a good question. I never had much luck getting sfc to work with the C:\I386 folder after SP3 was installed. It worked okay before then using the registry hacks, but not after. I suspect SP3 does not update the \i386 folder. I wonder if you copied c:\Windows\ServicePackFiles\i386 to \i386 and let it replace any existing files, if that would then bring the \i386 folder up to the SP3 level.

Good question, have you seen that done before ?

why is it asking her for the Windows Pro XP 3 disk ?

I think it is a recognized (except perhaps by MS) bug.

Ken, I remember reading about it once or twice but I can't find the posts now. May not make any difference. Bill may be right about this being a MS bug. Shame they never fixed it.