Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What does the "autocheck" in the default data of the registry value HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\bootexecute (Data is: autocheck autochk *) do? There's no autocheck.exe on a current (checked XP, Win7, Vista) standard Windows install, so it can't be launching an executable(?) I know what autochk does.

share|improve this question

migrated from Jul 22 '12 at 15:23

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted

It's an arbitrary name associated with the boot-time command autochk *.

The BootExecute value is a REG_MULTI_SZ, i.e., it can contain multiple separate strings. However, if you double-click it in the Registry Editor you will notice that the default value is not three separate strings, autocheck, autochk and * but rather a single string autocheck autochk *.

Each string in BootExecute contains an arbitrary descriptive name followed by the command to execute.

share|improve this answer
Thanks! That makes sense and it seems to work as explained in my tests too. :) – myname Jul 24 '12 at 14:47

From here. "autocheck" tells windows to run "autochk *" after previous illegal shutdown :)

By default, its value is "autocheck autochk *" - this tells Windows to run Autochk on any drive whose dirty bit is set

share|improve this answer

Autochk is standard Windows native application. AFAIK, is always present in fresh install of Windows XP.

Explain from Microsoft:

The Autochk (Autochk.exe) utility is a version of Chkdsk. For more information about Autochk, see the Windows XP Professional Resource Kit. To do this, visit the following Microsoft Web site: Troubleshooting Disks and File Systems

share|improve this answer
Yes, that's why I'm asking about autocheck, not autochk. ;) – myname Jul 22 '12 at 12:40

Imho, this runs some internal system checks. For example, when there is a folder C:\Program\, windows warn about it (because it interfere with C:\Program Files\).

share|improve this answer
Not sure I understand. I just tried to create a C:\program folder and didn't get a warning on my XP. Is this internal warnings for the OS, not the user? – myname Jul 22 '12 at 10:18
Was seen this warning (dialog box, suggesting to rename folder to Program1) in Windows 7. And this warning appears sometimes after booting. – Maximus Jul 22 '12 at 10:23
Thanks! I hadn't rebooted, I see what you mean now. :) This message still appears though, when you remove autocheck from the bootexecute value. – myname Jul 22 '12 at 10:28
Can you check, what process shows this warning? I was lazy to do that. May be "default value" is informational for user only, and OS runs checks everytime? :) – Maximus Jul 22 '12 at 10:34
The popup is from explorer.exe and a procmon log shows explorer first accessing C:\program and then testing if c:\program1 exists. explorer was launched by userinit. – myname Jul 22 '12 at 10:45

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .