New
#11
thanks for the tip. I usually run SFC at least twice if there are errors found. I will run it a few more.SFC with /SCANNOW switch needs often to be run several times. Three - four times is totally normal, sometimes even more. This is also clearly told in the tutorial. My rule is: after an SFC /SCANNOW run, if not all errors were fixed, reboot and repeat, although not every geek sees the reboot in between the SFC runs necessary.I use Virtual CloneDrive (Freeware).
(Near the bottom of that web page.)
If that does not install for you, then it might be time for this: SFC scan.
SFC found corrupt files but was unable to repair them, any suggestions? CBS.log attached
thanks
This quote from the SFC tutorial:
Note
- If 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.
- If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
- If still not, then try using OPTION ONE above to run the sfc /scannow command at boot.
- If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
- If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix if there are not to many fix.
- If there are to many files to manually fix, or you prefer not to use OPTION THREE below, then you could do a repair install without losing anything.
- If you would like to get help with your SFC issue, then be sure to upload and attach your sfcdetails.txt file from OPTION THREE below in your post.
I assume the method for running an SFC scan at boot would be from within Windows Recovery Environment command prompt?