Windows 10: SFC /SCANNOW says it found problems and couldn't fix them....NOW WHAT?

This is a question I have seen asked more than once. The answer, of course, is to run DISM. And THEN to run SFC /SCANNOW again.

This is my session from last evening which is what reminded me that I keep seeing this question.




Now, as you can see, I did exactly what I SAID should be done until all the problems were repaired. Then I stopped and went back to enjoying my computer.



Had it been necessary I might have also run CHDSK/F ("F" does not, in this case, indicate the drive. It means "Fix" "C"---my main hard drive---is the one it is fixing) and then run SCANNOW THIRD time.


If none of that works it may be time to look for hardware problems which may lead to buying a new computer.


Oh...I should probably mention why I ran this in the first place. Cortana had stopped responding to verbal input and there was some other behavior from my computer that was a bit "off" so I looked into why. Good practice, always.

I know we get frustrated at times like that and just go ahead with what we were doing (or try to---and I COULD have) instead of taking the time to fix the issues but that's not really the best way to handle this.

The BEST way is to TAKE the to fix problems WHEN they occur...otherwise things just get worse.

It isn't time WASTED at all. It is time well spent

:)

 

SFC scannow not working but verify only is working

there is no problem in chkdsk I've checked When I select command prompt and sfc scannow from f8 and repair.. it shows that a reboot is required for pending repair and pending renames folder in winsxs is full of files.. what should I do??

 

sfc /scannow says this.


Well, I think we don¡t need the log, hahaha. The sfc report says everything is good now:





I guess the DISM thing solved it? It's a mistery to me.

Anyway, with this tool I'm a little bit psyched. It's good to run the scf on a kind of routine, or only if we see that something is messed up? I ask this because I wasn't experiencing anything bad, but did it and found those lines.

 

sfc /scannow error

That's why Im asking the question. Am I correct in thinking that its perfectly normal that after the second running of sfc /scannow in your list you would get :-

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Then after that..its the third sfc /scannow that you list that comes up clean .
Ivghandi was saying that he presumed that the second sfc /scannow you list showing "Windows Resource Protection found corrupt files and successfully repaired them" meant that he still had a problem.

The way I understand that DISM works is that it repairs the Component Store. Then when you run SFC /scannow again it can then repair the file corruptions it detected originally. Have I got that correct?