SFCFix comes to the rescue when SFC /Scannow cannot repair Windows file corruption - gHacks Tech News

SFCFix comes to the rescue when SFC /Scannow cannot repair Windows file corruption

One elegant option to deal with file corruption on a Windows system is to run the SFC /scannow command on the machine running the operating system.

SFC, which stands for System File Checker, scans all protected system files for corruption and attempts to repair it by copying a cached copy of each corrupted file from the system32\dllcache folder.

This works sometimes but not all of the time. For instance, if the cached copy is corrupted as well, then it won't succeed.

A message like "Windows Resource Protection found corrupt files but was unable to fix some of them" highlights the issue.

sfc scannow

That's where the free program SFCFix comes into play. It parses the CBS.log file that the sfc /scannow command creates for corrupt files to repair them. The application itself is portable and compatible with all recent versions of Windows.

The website of the program does not reveal much about how the program achieves that and how it differs, only that it "uses advanced algorithmic searches to find and replace corrupt/missing system files". On another web page, it is revealed that it is using file hashes.

Update: The program website is no longer available. We have uploaded the latest working version of SFCFix to our server. You can download it with a click on the following link: SFCFix Please note that we don't support the program in any way.

The program is easy to use, but you may want to be cautious about it nevertheless. First of all, you need to be sure that there is no malware on the system if the source of the corruption was a malware attack.

Second, you may want to create a system backup just in case so that you can restore the current version of Windows in case something goes wrong along the way.

Before you run SFCFix, run sfc /scannow as it uses the information of the log that the process creates.

  1. Tap on the Windows-key, type cmd.exe, right-click on the result and select "run as administrator" to open an elevated command prompt.
  2. Type sfc /scannow and hit enter.
  3. The process checks all protected system files for corruption and attempts to repair any files that are corrupted.

Once the process has run its course, run SFCFix on the system.

sfc fix

A full scan may take anywhere from 15 minutes to 30 minutes depending on several factors. The program informs you if the scan will take longer than the projected 15 minutes so that you know how long you have to wait approximately.

The program opens a notepad document after the scan listing the results of the scan. It reveals the full path of each corrupt file and whether it was fixed or repaired successfully by SFCFix.

Closing Words

Considering that it is not clear how it repairs corrupt files, it is suggested to take precautions before running it on a machine running Windows. The program may help you resolve file corruption errors that Windows itself cannot repair.

Summary
SFCFix comes to the rescue when SFC /Scannow cannot repair Windows file corruption
Article Name
SFCFix comes to the rescue when SFC /Scannow cannot repair Windows file corruption
Description
SFC Fix is a free program for all supported versions of Windows that attempts to repair file corruptions that the SFC scan of Windows can't fix.
Author
Publisher
Ghacks Technology News
Logo




  • We need your help

    Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

    We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.

    If you like our content, and would like to help, please consider making a contribution:

    Comments

    1. Flux said on November 6, 2015 at 7:42 pm
      Reply

      It uses dism to repair the system. Very nearly the same results can be achieved by running dism /online /cleanup-image /restorehealth
      Although SFCfix does a bit more with dism. It uses the most appropriate method of repair based on the Cbs log, not just one command every time.

    2. George said on November 7, 2015 at 11:41 am
      Reply

      Thanks, I’m sure this will come in handy at some point. On Windows 10, seems to me the sfc /scannow command has a higher success rate than previous Windows versions.

    3. Declan said on November 7, 2015 at 7:35 pm
      Reply

      A couple of weeks ago I was trying to manually handle the mess of Windows updates that MS has tossed at us. I got the good ones installed and the bad ones off. Every thing was working fine. Then I decided that while I was in the mood, I would go through my monthly routine of cleaning & defragging in preparation for my monthly clone. I decided to check for updates one last time, and BAM, it couldn’t connect and check for updates. I checked everything from network connection to malware to system restore. I spent almost a whole day researching the web for other’s comments on the same issue (gosh there were a lot) and solutions that didn’t work. I tried them all, including sfc/scannow….nothing.

      Then on some website run by a kid in Ontario I saw the comment on SFCFix.exe. What the heck, so I tried it also. BINGO. It worked. I don’t know what it did, or how it did it, but it worked. So, I uninstalled all the updates I added the day before and started over, now with a clean, working system. One by one I added and then checked each of the updates. I found the culprit … kb3083710. It updates the WindowsUpdate client and replaces files for several other updates. Somehow that update, which is not necessary, BTW, corrupted the update client and I needed to return it to a working state before I could continue connecting and downloading new updates. It was kb3083710 that was preventing that connection.

      Well, there’s a lot more to the story, and I’d be happy to share it with anyone who needs help if they’re having a similar problem, but I simply wanted to let the readers know that SFCFix.exe worked when nothing else would. I have absolutely nothing to do with that little gem, I wanted to say that so it was clear I wasn’t pushing something for my benefit. I just wanted to tell a story. Indeed, this is a little known tool that worked wonders for me and it might help solve other people’s problems that MS has caused with it’s forced updates. Thanks, Martin, your mention of it should help a lot of people fix file corruption issues.

      1. Tom said on November 14, 2015 at 8:38 pm
        Reply

        Excellent article, Martin. I ran SFC today and it reported problems it could not fix. I will give SFCFix a whirl tomorrow.

        Thanks to Declan for a well written response delineating his update problems ( why can’t MS get it right 1st time !!) and the SFCFix solution.

        Just remembered why MS screws up Windows. Because the new CEO fired a couple of thousand programmers and software testing engineers !

    4. psc said on November 29, 2015 at 10:43 pm
      Reply

      It is also not clear the where to download this sfcfix program. The link given seem to point to a highjacked website.

    5. PhoneyVirus said on December 11, 2015 at 7:59 pm
      Reply

      Just put the Windows 10 disc into the optical bay drive and boot from it click Repair, system don`t start after that, nuke it from orbit and start doing some heavy writing to the drive, BSOD the drive is failing and that means NO strip bar for this weekend enjoy.

      1. Dave Johnson said on November 6, 2017 at 7:15 am
        Reply

        Old as hell article ;but this guys reply is beyond short bus rider status.
        BSOD is 99.9% not your hard drive failing, SMART if enabled and in most cases is by default
        will keep you informed if your HDD is failing (if you’re still using mechanical HDD for your OS or at all really as SSD drives and hybrids are super cheap these days then you deserve HDD failure IMO).
        BSOD in most cases is either a memory leak or failing RAM or ram slot or Pagefile too small issue.
        If you’re getting fault in non-paged area or similar it is for sure either memory as in ram memory leak,ram or pagefile issue.
        First try:
        Increase your pagefile ,right click computer on Pre-windows 8/10 or ThisPC on Win 8/10
        Properties
        Advanced system settings
        Performance options
        Advanced
        Virtual Memory
        See what the recommended size is
        select custom size and increase it it 1000MB over the recommended size put the min at 10 mb over recommended size click set then ok and reboot.
        If you get BSOD again then it’s a ram error and you can remove sticks one at a time and switch out the last one left if you still get it with the other sticks removed.
        Then add sticks until your stable leaving out the stick that was in the first slot.
        If all else fails give your computer away and get an Android box

    6. Dwight Stegall said on March 10, 2016 at 9:59 am
      Reply

      This thing is really great. I ran sfc /scannow and it didn’t fix my files. SFCFIX fixed everyone of them.

    7. Parean said on March 16, 2016 at 11:33 am
      Reply

      If windows can’t boot, you can run SFC from Windows Recovery Console:

      sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

      Extracted from: http://www.sysadmit.com/2016/03/windows-reparar-archivos-del-sistema.html

    8. EdT said on August 27, 2016 at 3:29 am
      Reply

      Running sfc in safe mode, lets it work.

    9. Shua Li said on December 15, 2016 at 12:24 am
      Reply

      Just so you know, SFCFix and the website it was originally hosted on are both alive and well. It is currently on version 3.0.0.0, newer than the version you have archived here.

      Original download file:
      https://www.sysnative.com/niemiro/apps/SFCFix.exe

      1. Martin Brinkmann said on December 15, 2016 at 8:04 pm
        Reply

        Thanks. Do you have by chance a link to the page where it is hosted on, and maybe updated?

        1. AJ North said on December 16, 2016 at 3:38 am
          Reply

          Hello Martin,

          The link above is at https://www.sysnative.com/blogs/ (if not also at additional pages of their site).

          MajorGeeks also list SFCFix (and presumably maintain the most current version): http://www.majorgeeks.com/files/details/sfcfix.html .

          Best wishes for a safe & happy holiday — and new year!

          Cheers,

          AJ

        2. Shua Li said on December 21, 2016 at 12:36 pm
          Reply

          Yes, it’s located in a locked thread by niemiro in the Windows Update forum on sysnative.com:

          https://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html

          The thread is 4 years old now, but the download link always points to the most recent version.

    10. Anonymous said on January 28, 2018 at 1:16 pm
      Reply

      The program and the forum are still live and kicking
      Sysnative. com the tool can be found in the Sticky for Windows Updates

      And yes it runs on W10

    11. 13 said on April 13, 2018 at 11:48 pm
      Reply

      It was worth a shot. It could not repair some 50+ files that got corrupted because of a bad windows update freeze up during a large 150+ “important” files update. I swear they do that shit on purpose to make you get Win10. Not.Going.To.Happen. I’m going to restage this bitch and get it running even if it kills me and then cutting off windows update.

    Leave a Reply