HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
\Session Manager \AutoChkTimeOut
If the subkey does not exist, the default countdown of 10 seconds is used. If the subkey exists, and it is set to 0 seconds, there is no countdown. If it is set to more than three days (259,200 seconds), the default value is used.
If Autochk runs against a volume during the start-up process, it records its output to a file called Bootex.log in the root of the volume being checked. The Winlogon service then moves the contents of each Bootex.log file to the Application event log.
One event log message for each volume that is checked is recorded as follows:
Event-ID: 1001
Source: Winlogon
Description: This includes file system type; drive letter or GUID, and volume name or serial number to help determine what volume Chkdsk ran against. Also included is whether Chkdsk ran because a user scheduled it or because the dirty bit was set.
Note Volumes that are shared between server cluster nodes that run the Cluster service do not allow Autochk access to the volume during the start-up process. When the volumes are brought online, the Cluster service performs a function that is similar to running Chkntfs to see whether the dirty bit is set and to see whether the volume is dirty. If it is, the chkdsk /f command runs against the volume before being brought online. This does not check the BootExecute registry value, so it does not take these values into account.
|
