Disk Check Cancelled

[DerbyBorn]

Has anyone had the problem of Disk Checking always cancelling and found a
solution?

 

[philo]

Has anyone had the problem of Disk Checking always cancelling and found a
solution?

Please post the *exact* error message.

 

[Paul]

Has anyone had the problem of Disk Checking always cancelling and found a
solution?

Using Regedit, look in...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\BootExecute

http://support.microsoft.com/kb/158675

The key value of BootExecute, is supposed to be this by default:

autocheck autochk *

If, on the other hand, you did this

http://www.microsoft.com/resources/...all/proddocs/en-us/fsutil_dirty.mspx?mfr=true

fsutil dirty set C:

AFAIK, that's what the autocheck is looking for.
Once the dirty bit is set on a partition, it can't be cleared
unless there is a successful chkdsk run. That would be an
alternative to "scheduling" a run.

If you think about it, that registry key "BootExecute",
is pretty special. Things like malware, like the idea.
Whatever command is in BootExecute, runs very early in
the boot process. Say I write a utility, and I want it to
access C: early. I arrange to put the name of my utility in BootExecute.
I make the disk busy, while doing my thing perhaps. CHKDSK comes
along as the next thing to run (maybe I set up things so
autocheck runs next), CHKDSK notices my utility has made
C: busy, and then CHKDSK will refuse to check C:. CHKDSK
will cancel its run, because the assumption that C: is
not busy, has been violated.

So checking the value of BootExecute in this case, is critical.

Paul

 

[John Williamson]

Has anyone had the problem of Disk Checking always cancelling and found a
solution?

Not since Windows 98, and that was due to not having enough memory to
run chkdsk on C: without swapping. D: was fine, as the swapfile was on C:

 

[DerbyBorn]

http://www.microsoft.com/resources/documentation/windows/xp/all/proddoc
s/en-us/fsutil_dirty.mspx?mfr=true

The Volume was not dirty.

The Boot Execute is set to autocheck autochk (space) *

It had up until a few days ago been:

autocheck autochk * /r\DosDevice\C


The exact messsage is:

A disk check has been scheduled
Disk checking has been cancelled

Oddly - It worked onece last night - but not since.

 

[Paul]

The Volume was not dirty.

The Boot Execute is set to autocheck autochk (space) *

It had up until a few days ago been:

autocheck autochk * /r\DosDevice\C


The exact messsage is:

A disk check has been scheduled
Disk checking has been cancelled

Oddly - It worked onece last night - but not since.

Doesn't a disk check create a log somewhere.

I thought one way to access it, was Event viewer.
I think I tried to look at the log file once, and
it was "binary" inside.

If you're lucky, the canceled job would create a log for itself.

*******

There are some ideas here. Apparently, one user feels the job
is getting canceled at boot, because the computer "presses
a key for itself", causing the cancellation. The people then
try tricks, such as "chkntfs /t:0", to bypass that as a potential cause.
Setting the timer to zero, prevents the computer from pressing
the key for itself.

http://social.technet.microsoft.com...f/thread/d78e4aaf-e506-43d1-bb01-89216bfba24b

And running from a Recovery Console, is another way to do it.
Virtually every installer CD/DVD, has an option to run an
MSDOS-like recovery console, and CHKDSK runs from there.
The command line options for CHKDSK, when run there, aren't
quite the same, but you'll figure it out.

Paul

 

[DerbyBorn]

Doesn't a disk check create a log somewhere.

I thought one way to access it, was Event viewer.
I think I tried to look at the log file once, and
it was "binary" inside.

If you're lucky, the canceled job would create a log for itself.

*******

There are some ideas here. Apparently, one user feels the job
is getting canceled at boot, because the computer "presses
a key for itself", causing the cancellation. The people then
try tricks, such as "chkntfs /t:0", to bypass that as a potential
cause. Setting the timer to zero, prevents the computer from pressing
the key for itself.

http://social.technet.microsoft.com/Forums/en- US/w7itproperf/thread/d78
e4aaf-e506-43d1-bb01-89216bfba24b

And running from a Recovery Console, is another way to do it.
Virtually every installer CD/DVD, has an option to run an
MSDOS-like recovery console, and CHKDSK runs from there.
The command line options for CHKDSK, when run there, aren't
quite the same, but you'll figure it out.

Paul

Doing FS Util dirty set c: caused CHKDSK to run.
I initially got the message that it was cancelled - then it ran.