New Year chkdsk starts, never stops

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This started this morning, on my first use in 2005:

I have a triple boot machine with Win 98, NT, and XP, but almost always boot
into XP (the default). Today, when XP started, it started running chkdsk on
drive D:, my rarely-touched Win NT partition.

First of all, I don't know what triggered this. More importantly, it finds a
seemingly ENDLESS series of errors of the type "Recovering orphaned file
xxxxx into directory file #####"

Several times, I've reset the computer and hit a key to prevent the chkdsk
operation on the new boot. Booting into either the NT partition (drive D:)
or the XP partition, I seem to have OK operation.

Any idea what's going on here? Is it just coincidence that this started with
the new year?
 
How to Cancel CHKDSK After It Has Been Scheduled

To stop the execution of CHKDSK /F /R, you must edit the registry using
Registry Editor.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct them.
Microsoft cannot guarantee that any problems resulting from the use of
Registry Editor can be solved. Use this tool at your own risk.

To stop the execution of CHKDSK /F /R, take the following steps:
1. Run the Registry Editor(Regedt32.exe).
2. Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:
\SYSTEM\CurrentControlSet\Control\Session Manager
3. Change the BootExecute entry from:

autocheck autochk * /r\DosDevice\C:

To:

autocheck autochk *
If you have scheduled CHKDSK for multiple volumes, there will be an
autocheck entry for each volume. Delete the string from the BootExecute
registry value for each volume you do not want checked.

This procedure will reset the default string, and CHKDSK /F /R will not run
 
Thanks, Nicoliani:

Actually, at the end of yesterday's work, I simply let chkdsk "do its thing"
after I left. When I came in this morning, my monitor screen was black.
Forgetting how I'd left it yesterday, I flipped the power off, then on. The
reboot was normal (without chkdsk). Consulting that registry entry, I found
it to be

autocheck autochk *

So I guess everything's OK. Still, I'd like to know what got that check set
up to begin with and why it found so many "orphaned" files on a volume I
haven't used recently.
 
It can go on if a computer shoutdown was inpropebly done. That on older
systems as NT and 2000.

chkntfs /x c: This disables chkdsk from running on drive C:
 
Back
Top