Windows Vista Forums

3 corrupt system files that sfc /scannow cannot fix, including aut

  1. #1


    briantrease Guest

    3 corrupt system files that sfc /scannow cannot fix, including aut

    Hello,

    After realizing that my autochk.exe is corrupt, I've tried running sfc
    /scannow to fix it. From the resulting cbs.log file, I see that the file is
    corrupt and cannot be fixed. There are two other files in the log with the
    same problem (tcpmon.ini and settings.ini).

    How do I replace these files, and from where should I attain the new
    versions? Or, is there some recommended repair utility?

    (Below is the relevant section of CBS.log for autochk.exe)

    Thanks!
    Brian

    *note, refer to this previous post of mine where one problem was solved, but
    this new problem was discovered:
    http://windowshelp.microsoft.com/com...9-9f6daa4861f4

    ---
    2007-07-17 18:40:35, Info CSI 0000001c Hashes for file
    member
    \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2b4dc4d6121b\autochk.exe
    do not match actual file [l:22{11}]"autochk.exe" :
    Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
    {l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
    2007-07-17 18:40:35, Info CSI 0000001d [SR] Cannot
    repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
    Version = 6.0.6000.16386, 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
    2007-07-17 18:40:36, Info CSI 0000001e Hashes for file
    member
    \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2b4dc4d6121b\autochk.exe
    do not match actual file [l:22{11}]"autochk.exe" :
    Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
    {l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
    2007-07-17 18:40:36, Info CSI 0000001f [SR] Cannot
    repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
    Version = 6.0.6000.16386, 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
    2007-07-17 18:40:37, Info CSI 00000020 Repair results
    created:


      My System SpecsSystem Spec

  2. #2


    uvbogden Guest

    RE: 3 corrupt system files that sfc /scannow cannot fix, including aut

    My computer was unable to do error checking (chkdsk) and errors began to
    accumulate. System restore did not go back far enough to restore this
    function. System File Check identified a corrupt system file "autochk.exe"
    that sfc was unable to repair. Instead of doing a clean install, I was able
    to do an Upgrade Install that preserved my programs, devices, settings, etc.
    (see John Barnett Windows MVP).

    I wanted to replace my corrupt system file with a good one from the Vista
    Install DVD without having to do a complete install, but was unable to do
    this until now. From multiple sources including contributors on Vista
    Communities, Windows IT Pro, How-To Geek, and Vistax64 Forum, I have put
    together a tutorial on how to access files from your Vista Install DVD that
    you can use to replace corrupt files in your OS. See the link below:

    Access Vista Install DVD Files

    System File Check will identify corrupt system files that it can't repair
    (see CBS.log). You can replace your corrupt files with good copies from the
    Vista Install DVD. Many thanks to those who contributed to this solution.


    "briantrease" wrote:

    > Hello,
    >
    > After realizing that my autochk.exe is corrupt, I've tried running sfc
    > /scannow to fix it. From the resulting cbs.log file, I see that the file is
    > corrupt and cannot be fixed. There are two other files in the log with the
    > same problem (tcpmon.ini and settings.ini).
    >
    > How do I replace these files, and from where should I attain the new
    > versions? Or, is there some recommended repair utility?
    >
    > (Below is the relevant section of CBS.log for autochk.exe)
    >
    > Thanks!
    > Brian
    >
    > *note, refer to this previous post of mine where one problem was solved, but
    > this new problem was discovered:
    > http://windowshelp.microsoft.com/com...9-9f6daa4861f4
    >
    > ---
    > 2007-07-17 18:40:35, Info CSI 0000001c Hashes for file
    > member
    > \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2b4dc4d6121b\autochk.exe
    > do not match actual file [l:22{11}]"autochk.exe" :
    > Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
    > {l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
    > 2007-07-17 18:40:35, Info CSI 0000001d [SR] Cannot
    > repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
    > Version = 6.0.6000.16386, 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
    > 2007-07-17 18:40:36, Info CSI 0000001e Hashes for file
    > member
    > \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.0.6000.16386_none_dfbd2b4dc4d6121b\autochk.exe
    > do not match actual file [l:22{11}]"autochk.exe" :
    > Found: {l:32 b:tZN+W/XkksJHvDvnrLN0OmikXDWw+uH0l1SsXGI9vdg=} Expected:
    > {l:32 b:wSKkBQ/YXr4909/sTSrtOCsbCRFN0hw8v/ecE99qI6V=}
    > 2007-07-17 18:40:36, Info CSI 0000001f [SR] Cannot
    > repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk,
    > Version = 6.0.6000.16386, 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
    > 2007-07-17 18:40:37, Info CSI 00000020 Repair results
    > created:
    >


      My System SpecsSystem Spec

3 corrupt system files that sfc /scannow cannot fix, including aut

Similar Threads
Thread Forum
sfc /scannow found corrupt files but was unable to fix some of them
I run sfc /scannow as Administrator and got the message: Beginning system scan. This process will take some time. Beginning verification phase...
General Discussion
sfc scannow reveals corrupt files
My question is, after doing a restore to original condition and then running sfc scannow is it normal for a New HP pavilion dv4-1125 Entertainment...
General Discussion
results of my sfc /scannow scan saying can't fix corrupt files. Help!
Hello My latop has been turned itself off about 8 times today so I did a bit of reading on the forums and one of the things that was suggested...
General Discussion
repair corrupt system files after scannow cmd couldn't repair
I ran the scannow command, but the corrupted files were unable to be repaired. I'm told I need to insert the CD in order to repair them, but my...
Vista General
How to fix corrupt system files?
Hi folks, Few days back vista crashed (Dell Inspiron 1525, Vista 32bit Home Premium). It then damaged some DLL files and device drivers. Most of...
General Discussion
found corrupt files with sfc /scannow
okay found corrupt files when I ran6215 sfc /scannow Also found the same thing when i went to use vista glazz to patch up6216 and I cant provide...
General Discussion
sfc /scannow found corrupt files but was unable to fix some of the
I ran the sfc /scannow command because I was having some problems getting programs to run and got this message.. verification 100% complete Windows...
Vista General