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" wrote in message
...
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" wrote in message
...
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.

"HMT" wrote in message
...
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" wrote in message
...
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" wrote in message
...
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.


Are you using Windows Vista Home Premium 64-bit?

Directory of C:\Windows\System32
04/11/2009 12:22 PM 734,720 autochk.exe (717KB)

Directory of C:\Windows\SysWOW64
04/11/2009 12:23 PM 643,072 autochk.exe (628KB)

"HMT" wrote in message
...
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" wrote in message
...
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" wrote in message
...
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.


Are you using Windows Vista Home Premium 64-bit?

Directory of C:\Windows\System32
04/11/2009 12:22 PM 734,720 autochk.exe (717KB)

Directory of C:\Windows\SysWOW64
04/11/2009 12:23 PM 643,072 autochk.exe (628KB)

I discovered the different sizes yesterday. The copy I got was from Vista
Ultimate 64-bit and larger than the one I need for Vista Premium 32-bit. I'll
ty and find someone with Vista Premium 32-bit and copy their autochk.exe.

"Tae Song" wrote:


"HMT" wrote in message
...
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" wrote in message
...
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" wrote in message
...
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.


Are you using Windows Vista Home Premium 64-bit?

Directory of C:\Windows\System32
04/11/2009 12:22 PM 734,720 autochk.exe (717KB)

Directory of C:\Windows\SysWOW64
04/11/2009 12:23 PM 643,072 autochk.exe (628KB)

I discovered the different sizes yesterday. The copy I got was from Vista
Ultimate 64-bit and larger than the one I need for Vista Premium 32-bit. I'll
ty and find someone with Vista Premium 32-bit and copy their autochk.exe.

"Tae Song" wrote:


"HMT" wrote in message
...
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" wrote in message
...
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" wrote in message
...
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.


Are you using Windows Vista Home Premium 64-bit?

Directory of C:\Windows\System32
04/11/2009 12:22 PM 734,720 autochk.exe (717KB)

Directory of C:\Windows\SysWOW64
04/11/2009 12:23 PM 643,072 autochk.exe (628KB)