How To'sWindows

Fix: Corrupt Files Reported by SFC Using SFCFix

The corruption of system files that are necessary for the optimum functioning of their computers is one of the largest and most common problems that users of the Windows Operating System are often met with. Thankfully for Windows users, all versions of the Windows OS come with a highly effective utility capable of repairing corrupted system files – the System File Checker (SFC) scan.

By opening an elevated Command Prompt, typing in sfc /scannow and pressing Enter, you can initiate an SFC scan. The scan analyzes all of your computer’s system files, sets all corrupted/missing system files aside and then attempts to fix the issue by replacing them with uncorrupted cached copies. The SFC scan is, in every sense of the word, ingenious. However, there are some instances where the SFC scan simply isn’t enough to resolve the issue. For example, if the cached copies of the system files that have become corrupt are also, for some reason, corrupt, the SFC scan will not be able to fix them and will display a message along the lines of “Windows Resource Protection found corrupt files but was unable to fix some of them.”

Because such instances are extremely rare, most people wouldn’t know what they should do next when running an SFC scan does not entirely fix the problem. Enter SFCFix – a completely free piece of software that can be downloaded here and is designed specifically to tackle problems that an SFC scan failed to fix. SFCFix is extremely easy to use, portable and compatible with all recent versions of the Windows OS.

The way SFCFix works is pretty impressive to say the least. When you initiate an SFC scan, the scan creates a CBS.log file that contains information on every single corrupt or missing system file that the scan encounters, including those that the scan failed to repair or replace. What SFCFix does is that it parses and reads this CBS.log file, finds out what corrupt or missing system files the SFC scan couldn’t deal with and it needs to tend to, and then uses file hashes and advanced algorithmic searches to repair or replace any and all corrupt/missing system files.

Listed below are all of the steps you need to perform in order to resolve all of the problems that an SFC scan couldn’t fix for you. It should be noted that since SFCFix needs the CBS.log file that an SFC scan creates when it is initiated to do its thing, you will have to first run an SFC scan before you can launch SFCFix.

Open the Start Menu. Search for cmd. Right-click on Command Prompt in the search results. Click on Run as administrator in the contextual menu.

cmd-run-as-administrator

Type sfc /scannow into the elevated Command Prompt and press Enter.

2016-01-20_045557

Allow the SFC scan to run its course, and as soon as it has, launch SFCFix. Press Enter on the prompts you get to continue.

Allow SFCFix to do its thing. SFCFix will scan your computer and then attempt to repair or replace the missing/corrupt system files that the SFC scan failed to deal with. The whole process can take anywhere between 15 and 30 minutes (depending on various factors), but SFCFix will inform you if the estimated time of completion for the process is longer than 15 minutes so that you know just how long you need to wait.

2016-01-20_050009

Once SFCFix has gone about its business successfully, it will open a Notepad document that will list the full path of every corrupt/missing system file that SFCFix found and whether or not it was successfully repaired or replaced by the program.

13 Comments

  1. I have error code 0xc000021a and I have tried all the methods you’ve mentioned, except for downloading SFCFix tool as my computer won’t start in order to get it online… What else can I do?

  2. I have run the scan after 100%of verification I got the message that Window Resource Protection did not find any integrity violation. What is my next step?

  3. I ran sfc /scannow and got the following message: Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log.

    I then downloaded and ran SFCFix and it said Due to the nature of your corruptions, scan times have been extended by approximately 15-20 minutes.” Then it ran DISM and gave err msg 0x800f081f The Source files could not be found. Use the “Source” option to specify the location of the files that are required to restore the feature. I remember running DISM some weeks back in an attempt to fix my corrupt files, but I always got the same error message re not finding the source files. Any advice?

Leave a Reply

Your email address will not be published.

Expert Tip

Fix: Corrupt Files Reported by SFC Using SFCFix

If the issue is with your Computer or a Laptop you should try using Reimage Plus which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Reimage by clicking the Download button below.

Download Now

I'm not interested

Close