Obviously Googling, using search terms like "disable chkdsk registry",
should turn up a number of helpful registry settings, that you could compare
with your own.
I tried that (google web and google groups), with dubious results...
-
http://www.dataclinic.co.uk/disable-scandisk-chkdsk.htm claims that by
changing "the BootExecute entry to: 'autocheck autochk *'" I can disable
chkdsk at boot time.
-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q160963 claims
that "Chkdsk /f schedules itself to run at the next reboot by setting the
dirty bit on the drive." In my experience, chkdsk /f schedules a boot time
check by adding the line "autocheck autochk /p \??\C:" to the BootExecute
value in the registry. chkdsk /f does not seem to set the dirty bit:
--------------------------------------------------------
e:\>fsutil dirty query d:
Volume - d: is NOT Dirty
e:\>chkntfs d:
The type of the file system is NTFS.
D: is not dirty.
e:\>chkdsk /f d:
The type of the file system is NTFS.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) n
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y
This volume will be checked the next time the system restarts.
e:\>fsutil dirty query d:
Volume - d: is NOT Dirty
e:\>chkntfs d:
The type of the file system is NTFS.
Chkdsk has been scheduled manually to run on next reboot
on volume D:.
e:\>
--------------------------------------------------------
Running chkdsk, instead of marking the drive as dirty, creates an
additional line in BootExecute, which on my system is now (after the
above):
autocheck autochk /p \??\D:
autocheck autochk /p \??\C:
autocheck autochk *
(Which results in D: being checked, but not C: ...)
The rest of the hits was either about how the standard settings should be
(which are not any different on my system) or about how to disable the
autocheck, using the BootExecute value or chkntfs.
Nothing that would add anything to what I already checked, with your (and
others') help.
For example, perhaps run through all the "BootExecute" keys in the
registry
eg at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\Session Manager
Check that they are ALL set to autocheck autochk *
Because I already tried to schedule a manual boot time check, all these
keys are set to:
autocheck autochk /p \??\C:
autocheck autochk *
(Or were, before I ran the sequence above that scheduled the D: drive.)
I already tried to delete the first line and set it back to the default
value. The result is that chkdsk does not run on boot (because the drive is
not dirty). When I run chkdsk /f after the boot, it adds that first line
(as expected), but it still doesn't run on boot.
Another key to look at would be the WinLogon key at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
I have pasted the current values of my entries
Thanks a lot, that was new to me. Nothing odd there, except...
Also saw that Kelly had a check disk enable / disable on her site
(number 82 in this page)
http://www.kellys-korner-xp.com/xp_tweaks.htm
She says that SfcScan in Winlogon should be 1; it's 0 in your system, it's
been missing in mine, but adding it didn't change anything.
I found a mention of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Diagnostics\RunDiagnosticLoggingGlobal, which I set to 1
during the last boot. But no additional error messages showed up in the
event log. Only the one normal Winlogon event with the results of checking
the D: drive.
**********************************************************************
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon] "AllowMultipleTSSessions"=dword:00000001
is 0, can't see a problem with this
"LogonType"=dword:00000001
is 0, shouldn't be a problem
"ShowLogonOptions"=dword:00000000
is 1, shouldn't be a problem
The following are missing, but I can't see how they would change the chkdsk
behavior.
"KeepRasConnections"="1"
"DisableCAD"=dword:00000001
"LeakTrack"=dword:00000000
"SfcScan"=dword:00000000
adding this with a data of 1 didn't change anything
"AutoAdminLogon"="1"
"Background"="0 0 0"
**********************************************************************
Thanks... I'm pretty much lost with this. If only it were possible to get
some diagnostic output from autocheck or autochk... Can I run these
manually from the recovery console? I haven't found anything about
additional diagnostic output from these tools.
Gerhard
