sfc found corrupt files but "was unable to fix". Now what?

Anonymous
2010-01-13T18:49:07+00:00

My laptop, which I recently upgraded to Windows 7 from Vista, has been periodically locking up on me.  I ran sfc /scannow, and received the following error:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example

C:\Windows\Logs\CBS\CBS.log

I checked CBS.log and found this line which seemed relevant:

2010-01-13 13:14:13, Info                  CSI    000001aa [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

OK.  Now what do I do?  I found a "How to analyze the log file entries that the Microsoft Windows Resource Checker program generates", but it doesn't give a clue as to what to do about a "cannot repair" entry.

Any help?

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-01-14T17:45:31+00:00

Hello Mikey Chairs,

a)    Have you made any recent changes on the computer?

Method 1: In order to fix this issue, I would suggest you to refer the article given below and follow the steps from the link and check if it helps.

Note: This is also applies for windows 7:

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

http://support.microsoft.com/kb/928228

**Method 2:**Try to perform clean boot and check if any of the third party applications are causing the issue.

To find out which startup application is causing the issue. Please follow the steps below:

Clean Boot will help you start your computer by using a minimal set of drivers and startup programs so that you can determine whether a background program or any of the third party service is interfering with your program.

 Steps to perform a Clean Boot:

  1. Click Start on your Desktop
  2. Type msconfig in the Start Search box and then press ENTER.

If you are prompted for an administrator password or for a confirmation, type the password, or click   Continue.

  1. On the General tab, click Selective Startup.
  2. Under Selective Startup, click to clear the Load Startup Items check box.
  3. Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
  4. Click OK.
  5. When you are prompted, click Restart.

If the computer boots fine after clean boot, then there are some non Microsoft applications causing the problem. To find out which application causing the problem refer from step 2 to step 6 in the article this is mentioned in the clean boot article.

http://support.microsoft.com/kb/331796

Once you find out the application which is causing the issue, i would suggest you to uninstall and reinstall the application.

To return your computer back to normal boot:

  1. Click Start on your Desktop
  2. Type msconfig in the Start Search box and then press ENTER.

If you are prompted for an administrator password or for a confirmation, type the password, or click   Continue.

  1. Click the General tab.
  2. Click Normal Startup - load all device drivers and services, and then click OK.
  3. When you are prompted, click Restart to restart the computer.

For information on using “Clean Boot”, see the following Microsoft Article:

http://support.microsoft.com/kb/331796

Method 3: Try to perform disk cleanup to remove temporary files from the computer. To do so, please follow the steps below:

The following procedure cleans up files associated with your user account. You can also use Disk Cleanup to clean up all the files on your computer.

1.    Open Disk Cleanup by clicking the Start button. In the search box, type Disk Cleanup, and then, in the list of results, click Disk Cleanup.

2.    In the Drives list, click the hard disk drive that you want to clean up, and then click OK.

3.    In the Disk Cleanup dialog box, on the Disk Cleanup tab, select the check boxes for the file types that you want to delete, and then click OK.

4.    In the message that appears, click Delete files.

For more information, please refer the link mentioned below:

http://windows.microsoft.com/en-us/windows7/Delete-files-using-Disk-Cleanup

I hope this information helps. Please get back to us if you have any more questions about this issue.

Thanks and Regards

Mir - Microsoft Support ****Visit our http://social.answers.microsoft.com/Forums/en-US/answersfeedback/threads

Was this answer helpful?

40+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2015-05-24T18:34:12+00:00

Hi - The 'solution' I found to this may just work for your HP notebook (although I realize the issues with this particular update aren't the same for everybody) - Have a look at my post on 20th May in the thread below...there seems to be some link between this update and KB3035583 which was first offered in March/April, but revised and re-offered this month. I uninstalled the original...installed the new version and 3022345 immediately became shown as an 'optional' update.

 http://answers.microsoft.com/en-us/windows/forum/windows_7-system/sfc-cannot-fix-corrupted-files-in-windows-7/f798f377-126c-47ff-bb16-ef5e0dddb5be?page=5

Was this answer helpful?

10+ people found this answer helpful.
0 comments

91 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-12-18T19:32:04+00:00

    Hi Mir A,

    As a Microsoft professional I find that you've taken an easy way out to the solution your are proposing here. I hate it when Support Personnels dump standard text on issues. The first part of your solution is OK, but the second part (Method 2) on using MSConfig is total bull. It doesn't address the issue.

    Please read, the user has "Corrupted" System files. The files are already corrupted, how do you think setting boot-time applications will restore the corrupt files. Your solution is below par, and should be removed, especially when you profess to be a support professional. If you don't know the solution, you are forgiven, but don't insult our integrity by dumping standard support text on an issue.

    The question here is, how do we get to know which files are corrupted so we can restore them from Install Cabs without having to do a clean install of the system. Do you have a tool with which we can restore these files automatically, etc. Those are the solutions we are seeking.

    In my case, I have an IDE drive going belly up, lots of relocated sectors via CHKDSK /F /R. It got so bad to a stage that I am getting Genuine Windows Validation promp, while the System Properties was showing that the system has been activated. Of course I know files are corrupted because of the bad sectors. So now that I have fetched a new IDE drive, and moved Windows 7 over (Partition restor via ImageX), I want to fix those corrupted files. Fired up SFC /Scannow only to end up with the same error as the original user. SFS sees corrupted files but can't fix them, how do fix my system without the rigors of fully system install? Go Microsoft!

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2013-02-22T00:10:18+00:00

    My laptop, which I recently upgraded to Windows 7 from Vista, has been periodically locking up on me.  I ran sfc /scannow, and received the following error:

    Windows Resource Protection found corrupt files but was unable to fix some of them.

    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example

    C:\Windows\Logs\CBS\CBS.log

    I checked CBS.log and found this line which seemed relevant:

    2010-01-13 13:14:13, Info                  CSI    000001aa [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

    OK.  Now what do I do?  I found a "How to analyze the log file entries that the Microsoft Windows Resource Checker program generates", but it doesn't give a clue as to what to do about a "cannot repair" entry.

    Any help? 

    Regarding to the original problem. This might work for you:

    1. Make sure your computer is connected to the internet.
    2. Open command prompt and run this command:

    dism /online /cleanup-image /restorehealth

    The command will download and repair corrupted files.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  3. Anonymous
    2014-03-24T21:15:58+00:00

    This thread is what seriously p***s me off with the windows forums.  This is a Windows 7 forum. SEVEN!  The OP put in his thread WINDOWS 7.  He specifically quoted an output from sfc /scannow which identified a problem with autochk.exe. 

    The first "official" reply clearly hadn't read the OP.  It does NOT answer the question, and yet is marked as "ANSWER".

    Many of the other posts refer to Windows 8, and then many responses saying thanks that fixed it - when the command quoted does not even work in windows 7.

    THERE IS NO ANSWER TO HOW TO FIX A CORRUPTED AUTOCHK.EXE IN WINDOWS 7

    I've got Windows 7 Home Premium, and I have this same problem. I cannot restore because there is a problem with the disk, so I should run chkdsk.  It cannot run now because the disk is in use, so I have to reboot; on reboot NOTHING HAPPENS.  I search, and find that I should run sfc /scannow in a command prompt which I do.  It identifies that autochk.exe is corrupt and that "source file in store is also corrupted"/ so cannot repair it.

     (I've found a KB article which was suggested in another thread, that should replace the file, though the problem it solves is slightly different.  Unsurprisingly, it tells me that the hotfix when run is not appropriate to my computer.)

    The suggestion of a full reinstall is laughable. There has to be a way of replacing this file.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments