• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

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

B

briantrease

#1
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/co...eral&mid=66e782bd-647a-4567-b019-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 Computer

U

uvbogden

#2
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:

http://www.vistax64.com/tutorials/86959-access-vista-install-dvd-files.html

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/co...eral&mid=66e782bd-647a-4567-b019-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 Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)