sfc /scannow very slow

sfc /scannow brings up the "Windows File Protection" window and goes through unattended with no errors.

The question is: How long does it take for others? Mine takes 1.5 hours. I opened task manager and the majority of cpu time was being taken by "winlogon.exe ". It was allowing "system.exe" to have the cpu for very limited time.

Is this normal behavior?

Would it be faster in Safe Mode?

 

BMoore1129--

Try it.
SFC is not a quick process, but 1.5 hours seems a bit long. However, there could be legitimate reasons. Have you run SFC faster before?

 

No Jim, I haven't tried it in Safe Mode yet.

I have no base of comparison because just yesterday I finally got it to work unattended for the first time. I had to change my setup entries in the registry per a long post from here about sfc and video cards.

I was going to "end process" on the winlogon.exe but was warned off by a pop up that says something about a system file and threatened world wide destruction if I stopped it.

I will give it a try in Safe Mode and report back....

 

BMoore1129--Sounds like you got the annoying Retry messages many times when you were using the WindowsXP CD as the source of replacement OS files.
Presume you now have copied your system files over to your C:\I386 file, reset your Source Path, and at least are no longer bothered with the messages to Retry.
http://www.helpwithwindows.com/WindowsXP/howto-24.html
I also changed HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath to C:\ .

 

Jim...Not only that. I got the annoying as an ex wife popups for my XP Pro CD and for my XP Pro SP2 CD.

I just tried sfc in safe mode. It doesn't work.

In Run it flashes what looks like a command window and sits there looking dumb.

If I open a cmd window and enter sfc /scannow I get an error message saying the RPC server is not available.

I go to the services msc and try to start the RPC Locator and get a message that it doesn't work in safe mode.

Also went to task manager and see that winlogon.exe is loaded and waiting to interfere anyway..Oh well.....

 

It is just "system ", PeteC. I misspoke with the exe.

I started it again and the winlogon is jumping around from 36-92% and the system is jumping around from 1-30% with system idle kicking in to take to remainder at any given time,

I have AMD2000 (1667) with 1 Gig SDRAM and 7200rpm WD 40 gig drives. I would assume yours would finish in half my time.