autocheck utility -- yay/nay

[jim]

does anyone else have --
"autocheck autochk *Auto Check Utility Microsoft Corporation
c:\windows\system32\autochk.exe "

run as "boot execute" (autoruns (tm) description)?

and, if so, do you give it a yay or a nay and does this run in a
svchost.exe?

jim

 

[Paul]

does anyone else have --
"autocheck autochk *Auto Check Utility Microsoft Corporation
c:\windows\system32\autochk.exe "

run as "boot execute" (autoruns (tm) description)?

and, if so, do you give it a yay or a nay and does this run in a
svchost.exe?

jim

That's part of "chkdsk" when the system starts up.

It allows checking for partitions damaged by a dirty shutdown.

Opportunistic programs also try to hijack the registry entry,
when they want to do things very early in system startup. The
registry entry in question can hold multiple commands, so an
application can sandwich its command in front of the normal
system one.

My BootExecute key (as seen in Regedit) right now says:

autocheck autochk *

and that is a normal setting.

If you look in the registry key and you see

blah blah
autocheck autochk *

then some program (like a defragmenter or something)
is trying to do a "blah" command, before the OS has
a chance to do CHKDSK.

If none of the partitions are dirty, then the autocheck
would finish in the blink of an eye.

Paul

 

[jim]

On Sun, 22 Sep 2013 14:37:44 -0400, in

That's part of "chkdsk" when the system starts up.

It allows checking for partitions damaged by a dirty shutdown.

Opportunistic programs also try to hijack the registry entry,
when they want to do things very early in system startup. The
registry entry in question can hold multiple commands, so an
application can sandwich its command in front of the normal
system one.

My BootExecute key (as seen in Regedit) right now says:

autocheck autochk *

and that is a normal setting.

If you look in the registry key and you see

blah blah
autocheck autochk *

then some program (like a defragmenter or something)
is trying to do a "blah" command, before the OS has
a chance to do CHKDSK.

If none of the partitions are dirty, then the autocheck
would finish in the blink of an eye.

Paul

thanks! great info!

jim

 

[Andy]

That's part of "chkdsk" when the system starts up.



It allows checking for partitions damaged by a dirty shutdown.



Opportunistic programs also try to hijack the registry entry,

when they want to do things very early in system startup. The

registry entry in question can hold multiple commands, so an

application can sandwich its command in front of the normal

system one.



My BootExecute key (as seen in Regedit) right now says:



autocheck autochk *



and that is a normal setting.



If you look in the registry key and you see



blah blah

autocheck autochk *



then some program (like a defragmenter or something)

is trying to do a "blah" command, before the OS has

a chance to do CHKDSK.



If none of the partitions are dirty, then the autocheck

would finish in the blink of an eye.



Paul

Thanks for the interesting info.

Andy