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?

Only Trusted Installer can write to that file. You could take ownership and
give yourself permission.
Didn't SFC repair it?
--
..
--
"HMT" <(E-Mail Removed)> wrote in message
news:441F8355-7753-49AB-9366-(E-Mail Removed)...
> 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?

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" <(E-Mail Removed)> wrote in message
> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
> > 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?
>
>

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

--
..
--
"HMT" <(E-Mail Removed)> wrote in message
news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
>> > 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?
>>
>>

This is for Windows XP. I have Vista Premium. Will it work?

"." wrote:

> http://support.microsoft.com/kb/308421
>
> --
> ..
> --
> "HMT" <(E-Mail Removed)> wrote in message
> news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
> >> > 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?
> >>
> >>
>
>

Yes.

--
..
--
"HMT" <(E-Mail Removed)> wrote in message
news:C56CD02E-CC7E-4BCE-B001-(E-Mail Removed)...
> This is for Windows XP. I have Vista Premium. Will it work?
>
> "." wrote:
>
>> http://support.microsoft.com/kb/308421
>>
>> --
>> ..
>> --
>> "HMT" <(E-Mail Removed)> wrote in message
>> news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
>> > 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" <(E-Mail Removed)> wrote in message
>> >> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
>> >> > 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?
>> >>
>> >>
>>
>>

Thanks. I'll give it a try and report back the next day or so.

"." wrote:

> Yes.
>
> --
> ..
> --
> "HMT" <(E-Mail Removed)> wrote in message
> news:C56CD02E-CC7E-4BCE-B001-(E-Mail Removed)...
> > This is for Windows XP. I have Vista Premium. Will it work?
> >
> > "." wrote:
> >
> >> http://support.microsoft.com/kb/308421
> >>
> >> --
> >> ..
> >> --
> >> "HMT" <(E-Mail Removed)> wrote in message
> >> news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
> >> > 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" <(E-Mail Removed)> wrote in message
> >> >> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
> >> >> > 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?
> >> >>
> >> >>
> >>
> >>
>
>

I right-clicked the command prompt and selected Run as Administrator. I
assume that's what you mean by elevated command prompt?

"lemur" wrote:

>
> Did you run sfc /scannow with "elevated" command prompt?
>
>
> --
> lemur
>
> ::If *ANYONE* in this forum helps you, please click on
> their *REP* icon. Thanks! (the middle scale icon in the upper right
> corner)::
>

"HMT" <(E-Mail Removed)> wrote in message
news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
>> > 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.

The size of the corrupt autochk.exe file is about 100kb less than the correct
size for autochk.exe which is about 717kb.

"Tae Song" wrote:

>
> "HMT" <(E-Mail Removed)> wrote in message
> news:EAF0721F-B62C-41CE-BE7F-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:441F8355-7753-49AB-9366-(E-Mail Removed)...
> >> > 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.
>
>
>
>