|
Re: Can't Replace Corrupt autochk.exe
"HMT" <HMT@discussions.microsoft.com> wrote in message
news:EAF0721F-B62C-41CE-BE7F-0D9332AEC9CA@microsoft.com...
> SFC could not repair it. How do I take ownership and give myself
> permission?
>
> "." wrote:
>
>> Only Trusted Installer can write to that file. You could take ownership
>> and
>> give yourself permission.
>> Didn't SFC repair it?
>> --
>> ..
>> --
>> "HMT" <HMT@discussions.microsoft.com> wrote in message
>> news:441F8355-7753-49AB-9366-908DEBC20D3C@microsoft.com...
>> > My Vista Premium will not run autochk.exe. I ran sfc/ scannow and the
>> > cbs
>> > log
>> > file found autochk.exe corrupt. I tried to copy autochk.exe from
>> > another
>> > Vista PC to the c:\windows\system 32 folder and it will not let me. I'm
>> > running as administrator and click continue when user account control
>> > pops
>> > up, but it won't copy. Any suggestions?
>>
>>
There might not be a problem with AUTOCHK.EXE.
If SFC says it can't repair something, it usually means the file-hash for
file is corrupt in the registry.
The way SFC detects corrupt files is by comparing the file-hash stored in
the registry against the hash generated from the file. If they don't match,
SFC copies a new copy from storage. Everything should be good then. But if
the file-hash in the registry is corrupt or out of sync, the hash from the
good copy still isn't going to match, so SFC will report it couldn't repair
the problem.
You don't need to worry about it too much unless it starts interfering with
Windows operations. Usually, this means Windows Update which uses the
file-hash in the registry to check what files you have installed. If you
get error like 0x80073712 ERROR_SXS_COMPONENT_STORE_CORRUPT, you would have
to go in and surgically remove the file-hash data in the registry to fix the
problem. The problem being Window Update not being able to do updates on
the files affected.
The problem is not uncommon.
|
Linear Mode
