New
#11
Very strange.
1. SFC hung at 94% saying it can't complete.
2. Corrupt files that can't be fixed...rebooted.
3.SFC comes up clean.
Should I run the SFCFIX tool?
Just run SFC again to be sure.
SFC Corrupt files
-
-
New #12
My understanding the reason for running sfc /scannow 3 time or more is.
1. You need to reboot for some repairs to complete the repairs.
2. sfc /scannow can only make (X) amount of repairs with one attempt whether the needed files are their or not.
The problem with #2 is I can't prove that it is true.
It comes from this Tutorial.
SFC /SCANNOW Command - System File Checker
and this one
SFC /SCANNOW : Run in Command Prompt at Boot
-
New #13
If SFC is coming back clean, then I think this has magically repaired itself It might have pended the replacement over a reboot on the first run, then on the second run (before rebooting) it detected the corrupt files, but saw they were already pended for replacement and didn't report them in the CBS log because they were about to be fixed. I think it's safe to say that's a long shot
I'm not sure if SFC even makes this check, but it would explain a few, but not all, things if it did.
The first point you mentioned is definitely correct, and is the reasoning behind why I said that on very few occasions, a second SFC run will actually help, but as far as I know, your second point isn't. I may well be wrong, and would love to be because then I learn something new, but I don't see why SFC would limit the number of repairs it could make in one run because surely it would want to fix as much as possible in one, and get the system stable immediately. Maybe when I've got a little more time, I'll corrupt 100 or so system files and see what SFC thinks of it.
Another thing, running SFC at boot isn't advantageous to running it normally, unless the system can't boot because of a corrupt file. I know you didn't say this was the case, it's just something I wanted to mention whilst we're on the topic :)
As for this (in the SFC tutorial), I'm going to ask Shawn what made him write this :)
I'm 99% sure it's wrong, but it's the remaining 1% that makes me curiousIf SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
Will report back gents!
Tom
-
New #14
Like I said #2 I can't prove. I think we all agree that doing the scan 3 times can't hurt anything.
I can say in my case when sfc /scannow found a problems on my computers the second time it came up clean. I don't know if that would be the case for everybody and their computers.
I run sfc /scannow at least once a month just to check how things are working and seldom found a problem.
From my post #12
The problem with #2 is I can't prove that it is true.
-
-
New #16
Yep, completely agree! It's overkill but doesn't stand a chance of causing any damage :)
It'll make the repairs on the first run, or pend them to be done over a reboot if the file is in use, then the second run will come back clean because the first run has fixed the problem :) Much like an AV detecting malware somewhere: scanning the first time detects the problem and it is then fixed, running it again won't detect anything.
No problemo, any time, Gary :)
Quote
Related Discussions