Still hoping for an answer regarding chkdsk problem

  • Thread starter Thread starter W C Hull
  • Start date Start date
W

W C Hull

I'm still hoping that someone will have an answer as to why I can no longer
setup chkdsk to run on the next startup.

Last week I wrote that after installing and then removing some software from
my system I can no longer get chkdsk to setup and run on the next restart of
my system when I try and set the program up from the command window. I can
run chkdsk if I run it from the Windows recovery console if I boot from my
original Windows XP CD. I can also trick my system into running chkdsk by
using the FSUTIL program to set the dirty bit prior to restarting my system.
What I cannot do is go to an command window and enter chkdsk C: /F or chkdsk
C: /R from the prompt and get chkdsk to run on the next reboot. When I run
chkdsk from the command prompt it asks if I want chkdsk to run on the next
reboot and I always say yes but when my system restarts chkdsk never starts
and I boot to the logon screen.

It is my belief that chkdsk probably needs to set something somewhere and
cannot. My problem is that I don't know what needs to be set to determine
what might be wrong or missing. If anyone has info on this chkdsk failure,
please help.

Thanks,
 
once you say "Yes", do yuo get conformation that indeed "Volume will be
checked next time it reboots?
 
Okay here you are!!!

Change in registry should occur!
Some related KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;831426

It shows that there are entries in Session Manger regarding CHKDSK and
Autocheck.
My registry entries are same as KB article UNTIL, I invoke chkdsk/r command.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
Manager\BootExecute

By the way I entered chkdsk /f /r So yuors might look slightly different
maybe the /f added the \??\
the original value was: autocheck autochk*
the new value was: autocheck autochk /r \??\ C:autocheck autochk *
or real close. I used cut/paste to post.

I actually have a ControlSet001, ControlSet002, ControlSet0003, and
CurrentControlSet.

Alll these had same value before command entered.
Once I entered, command ONLY ControlSet001 and CurrentControlSet chnaged to
new value.

So if yuor command isn't updating Registry , then this is above me for sure!!!

You are using Admin or Admin privileges account to do this right???
You have to be Admin or Admin privileges.


That's all I can do for you.
 
Thanks for the reply.

I believe that this was a fairly good clue but now I'm more confused.

After reading the reply I checked my system before and my system showed the
BootExecute value as being Autocheck autochk *. After running chkdsk c: /F
from the command window I rechecked and the value was changed to:

autocheck autochk /p \??\C:
autocheck autochk *

I swear that I have checked this value prior to restarting my system on
prior attempts at running chkdsk and I also swear that it contained the same
values as shown above and chkdsk never started. Today, however chkdsk ran
on restart so, I don't know if other factors were (are) still at work or
whether I am simply mistaken on what I swear I saw.

Anyway I did find another article
http://support.microsoft.com/default.aspx?scid=kb;en-us;218461 that may or
may not help someone else who may experience this problem. Although the
article (KB218461) says it pertains to Windows 2000 I suspect that it it
also true for Windows XP as well.

I also found the following article on another program called CHKNTFS
http://support.microsoft.com/default.aspx?scid=kb;en-us;160963 that
indicates that chkntfs can be use to reset the BootExecute value. There is
one line in this article that I found intereresting. The line reads as
follow:

"Chkdsk /f schedules itself to run at the next reboot by setting the dirty
bit on the drive. Chkdsk /x disables the checking for this bit. Chkdsk /f
can never run on volumes that are excluded from dirty bit checking by
chkntfs."

Since the program I installed and removed was a System Management program,
I'm wondering if in running that utility it somehow invoked a chkdsk /x or
chkntfs /x command

Anyway, thanks for the lead, it really helped!!!!!!
 
Back
Top