I am running Windows 7 Home Premium x64 with Intel Core 2 Duo processors. A week ago I upgraded my Dell XPSm1710 laptop from 100 GB to 500 GB HD, from 2 to 4 GB RAM. I did a clean install of Windows. Over the past 48 hours, my system has slowed considerably, and downloads are timed-out before completing. I ran the usual maintenance programs, including chkdsk (no problems found), and then a sfc. SFC found corrupt files some of which could not be repaired. I found the report in CBS.log, and it said the following in two locations in the text:
2010-11-06 01:50:31, Info CSI 0000002c Hashes for file member: SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7600.16385_none_3de8def0db722996\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
Found: {l:32 b:elI/RKVtKUeIfJ+74cDOqymXmfmQsooYFfwkVYni6rw=} Expected: {l:32 b:O9osH5IuxnI1PLLylnIPx189Vzpvz4ebIg63k2Ec+C4=} 2010-11-06 01:50:31, Info CSI 0000002d [SR]
Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
Using 7-Zip, I accessed files on my Win 7 HP DVD. The first part says that the autochk.exe file described in Winsxs above, has a hash mismatch with “actual file {1:22{11}] “autochk.exe””. I take it that the “actual file” refers to the locations of this file in System32 and SysWOW64 folders.
The second part of the CBS report clearly tells me that a hash mismatch file of pA AMD64, [1:22{11}] “autochk.exe”, path/location unspecified, has become corrupted and could not be repaired by sfc.
In the Windows 7 Home Premium install DVD, the following files are found:
- In Windows\Winsxs\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7600.16385_none_3de8def0db722996\autochk.exe. This autochk file has a date of 7/13/2009 at 7:38 PM, size 760 KB.
- The Windows\System32\autocheck.exe has a date of 7/13/2009 at 7:38 PM, size 760 KB.
- The Windows\Winsxs\x86_microsoft-windows-autochk_31bf3856ad364e35_6.1.7600.16385_none_e1ca436d2314b860\autochk.exe has a date of 7/13/2009 at 7:14 PM and a size of 653 KB.
- The Windows\SysWOW64\autochk.exe has a date of 7/13/2009 at 7:14 PM and a size of 653 KB.
When the CBS report says that the actual autochk.exe file doesn’t match the autochk.exe file in Windows\winsxs\amd64…, which of the files above found on the install DVD would be considered the “actual” file referred to that needs to be replaced? Intuitively, it would seem to me that a file in System32 would be backed up in (and match) the winsxs\x86_..file. Likewise, the SysWOW64 file would be the same as the winsxs\amd64_...file. But this is not the case in the install DVD, where the SysWOW64 file size is 653 KB and the winsxs\amd64 file is 760 KB.
This is confusing. Can you help me determine which of the 4 autochk.exe files on the install DVD I should use to replace whatever it means by the “actual” autochk.exe file?