How Do I Stop CheckDisk?

Greetings,

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from spring 2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot the
laptop?
Thanks


W. K. Mahler
http://www.mahlers.com

On 10/24/2014 09:39 AM, W. K. Mahler, Mahlers.Com wrote:
Greetings,

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from spring 2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot
the laptop?
Thanks


W. K. Mahler
http://www.mahlers.com


If you let chkdsk run to completion , the next time you start, it should
not run unless the machine was shut down improperly.

Is it hibernating OK?


If all seems to be OK


I am going to cut and paste this:



You probably have a corrupt entry for Error Checking in the registry. A
System Restore point would probably fix that. If you want to look at the
entry doing it, it's at:

'autocheck' entry (value) at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\BootExecute


Mark L. Ferguson MS-MVP

philo wrote:
On 10/24/2014 09:39 AM, W. K. Mahler, Mahlers.Com wrote:
Greetings,

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from spring
2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot
the laptop?
Thanks


W. K. Mahler
http://www.mahlers.com


If you let chkdsk run to completion , the next time you start, it should
not run unless the machine was shut down improperly.

Is it hibernating OK?


If all seems to be OK


I am going to cut and paste this:



You probably have a corrupt entry for Error Checking in the registry. A
System Restore point would probably fix that. If you want to look at the
entry doing it, it's at:

'autocheck' entry (value) at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\BootExecute

I'm sure there are threads all over for this. Chkdsk sure is a
damn nuisance.

http://forum.sysinternals.com/unable...24_page12.html

The value of the BootExecute key, is "autocheck autochk *" by default,
without the double quotes. What that does is check the "dirty" bit
on each file system.

The BootExecute key can contain multiple lines of text. Either malware
or antivirus programs, could load something into the multiple
lines of text, perhaps pushing the "autocheck autochk *" command
further along.

An interesting idea, on that particular Sysinternals page, is that
malware can replace your copy of "autocheck" with their own code.
This would result in no checking being done, no dirty file system
being repaired. So is a potential failure mode. One suggestion
is to check that the autocheck file is digitally signed, as
an indication it isn't the real one.

*******

File system checks can be scheduled a couple of ways.

1) If you do properties on a partition, attempt to do CHKDSK,
the partition is busy and cannot be dismounted, the OS will add
instructions for the partition to be checked during the next bootup process.
So instead of "autocheck autochk *" you will see something that specifies
explicitly that the partition in question needs to be checked.

2) The other option, is each partition keeps track of its status with
the "dirty" bit. The dirty bit can be queried by a user. The dirty
bit can be set by a user (to trigger CHKDSK to run at startup). The
dirty bit cannot be cleared by a user. Only CHKDSK is supposed to
clear the dirty bit, as proof that CHKDSK has run and corrected
the problem. If CHKDSK crashes during a run, then it would not
have an opportunity to clear the dirty bit.

fsutil dirty query C:
fsutil dirty set C:

There is no "clear" option. If it gets set, you must run CHKDSK
to take care of it. For people who experiment with the dirty bit,
sometimes their reward, is to get stuck in a CHKDSK loop at each
startup.

CHKDSK runs in the form of "autochk" at startup. Checking a
partition at startup offers an opportunity to check the partition,
before any processes make the partition "busy". CHKDSK can
also be run from the installation CD, from the command
prompt there. Which is another potential way to clear the
dirty bit, by a CHKDSK run.

The options to CHKDSK, differ slightly depending where you run them.
The "/f" looks useful. CHKDSK should be run as administrator, and
in the recovery console, you are the administrator. If you attempt
the command from the command prompt window in a running OS, it's
possible you would not have permissions to run this. On some
of the latest OSes, you're a member of the administrator group,
so this would not be a problem.

http://en.wikipedia.org/wiki/Chkdsk

It's possible a CHKDSK problem is related to the version
of file system stamped on the partition. NTFS has several
version numbers. There are subtle differences between
them. Like perhaps the treatment of $UPPERCASE metadata.
Or some attributes thing. It could be that CHKDSK is
triggered, because of some trivial crap like that.
You would want to examine the CHKDSK log in any case,
to see what it's been up to. The winlogon entry in
Event Viewer, may have the CHKDSK log from the run that
happens at bootup. More examples here, on tracking down
the reclusive CHKDSK log...

http://www.sevenforums.com/tutorials...iewer-log.html

HTH,
Paul

On Fri, 24 Oct 2014 10:39:07 -0400, W. K. Mahler, Mahlers.Com wrote:

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from
spring 2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot the
laptop?


The obvious way is to let it finish once. There's some reason why it
was scheduled, no?

But if you really do want to cancel it, it's not hard. When I googled
"cancel a scheduled disk check" (without quotes), there were over
69,000 hits. The first one, at Microsoft, refuses to load without
Javascript, but here's the second, which has the answer:

https://answers.microsoft.com/en-us/...rum/windows_7-
windows_programs/how-to-disable-the-chkdsk-check-disk-on-start-
up/35f58c69-7a6c-4e1b-aec3-26d7131ec643

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Shikata ga nai...

On Fri, 24 Oct 2014 10:39:07 -0400, W. K. Mahler, Mahlers.Com wrote:

Greetings,

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from spring 2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot the
laptop?

Actually, this looks even easier:

http://grok.lsu.edu/Article.aspx?articleId=13107


What _I_ would like is a way, when I reboot and get the prompt, to
start the check right away, without waiting for the indicated number
of seconds.



--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Shikata ga nai...

Stan Brown wrote:
On Fri, 24 Oct 2014 10:39:07 -0400, W. K. Mahler, Mahlers.Com wrote:
Greetings,

Windows 7 Home Premium w/SP1 here on a Toshiba Satellite from spring 2011.

Whenever I start this laptop, checkdisk starts. Unless I press any key,
checkdisk takes forever to well, check the hard drive. The harddrive is
fine so how do I prevent checkdisc from starting up everytime I reboot the
laptop?

Actually, this looks even easier:

http://grok.lsu.edu/Article.aspx?articleId=13107


What _I_ would like is a way, when I reboot and get the prompt, to
start the check right away, without waiting for the indicated number
of seconds.




What the grok.lsu.edu article would be doing,
is editing the BootExecute registry key.
Which can also be done with Regedit.

And it doesn't solve the case of a partition
that has the dirty bit set. You still have to
run CHKDSK in that case.

Paul

On Sat, 25 Oct 2014 09:37:11 -0400, Paul wrote:

Stan Brown wrote:
Actually, this looks even easier:

http://grok.lsu.edu/Article.aspx?articleId=13107


What the grok.lsu.edu article would be doing,
is editing the BootExecute registry key.

Did you even look at Step 3?

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Shikata ga nai...

Stan Brown wrote:
On Sat, 25 Oct 2014 09:37:11 -0400, Paul wrote:
Stan Brown wrote:
Actually, this looks even easier:

http://grok.lsu.edu/Article.aspx?articleId=13107

What the grok.lsu.edu article would be doing,
is editing the BootExecute registry key.

Did you even look at Step 3?


Step 3 would be the step that edits the Registry for you.
To "un-schedule" a CHKDSK, you change the contents
of BootExecute. For example, restoring the default
"autocheck autochk *" just checks for dirty bits
and does not force a CHKDSK. If you schedule C: to be
checked on the next reboot, the contents of the
BootExecute key will be different than that
(explicitly spells out that C: must be checked).

If you haven't been messing with this stuff, go
check your BootExecute key now, and see what is there.

Paul

On Sat, 25 Oct 2014 21:41:06 -0400, Paul wrote:

Stan Brown wrote:
[quoted text muted]
is editing the BootExecute registry key.

Did you even look at Step 3?


Step 3 would be the step that edits the Registry for you.


We're not looking at the same article.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Shikata ga nai...

On Mon, 27 Oct 2014 20:52:32 -0400, Stan Brown
wrote in
:

On Sat, 25 Oct 2014 21:41:06 -0400, Paul wrote:

Stan Brown wrote:
[quoted text muted]
is editing the BootExecute registry key.

Did you even look at Step 3?


Step 3 would be the step that edits the Registry for you.


We're not looking at the same article.

I don't see what would make you think that.

WHAT CHKNTFS DOES

Chkntfs /D sets BootExecute to "autocheck autochk *"
[normal behavior, run chkdsk on a drive if the dirty bit is set.]

chkntfs /x c: sets BootExecute to "autocheck autochk /k:C *"
[Don't check drive C even if the dirty bit is set]

chkntfs /c c: sets BootExecute to
"autocheck autochk /m \??\C: autocheck autochk *"
[schedule a drive to be checked; run chkdsk if dirty bit is set]
(I don't see how this is any different from chkntfs /D)

If you type chkdsk /f c: (and drive c: is in use) you will be asked if
you want to run chkdsk on the next reboot. If you say "Y", BootExecute
is set to "autocheck autochk /p \??\C: autocheck autochk *"

This is a "planned chkdsk" and is run regardless of the state of the
dirty bit.

If you accidentally schedule a drive for a chkdsk, i.e., respond "Y"
to

"Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N),

you can undo that choice before restarting by running

chkntfs /D

THE DIRTY BIT

The dirty bit is SET when the file system is accessed (more accurately
written to, I suppose). It is CLEARED when the system is shut down
properly and the file system is internally consistent. 'Nuff said.

If you want to find you if the dirty bit is the reason chkdsk keeps
running on startup, type

fsutil dirty query c: [where c: is the drive of interest]

If you really want to prevent chkdsk from running with a dirty bit
set, type

chkntfs /x c: (remember fix the problem and clear this -- it could be
a ticking time bomb...)

If you want to see how your system responds to the dirty bit being
set, type

fsutil dirty set c:

NOTE: There is no fsutil dirty clear ! Once you set the dirty bit, you
are committed to running chkdsk on that drive (volume).

OTHER THOUGHTS

1. To easily view the contents of BootExecute without opening the
registry editor, use AutoRuns from www.sysinternals.com. It is a
program that can show all "startup entries including BootExecute. Be
sure to look under Options-Filter Options and uncheck "Hide Microsoft
entries" and "Hide Windows entries". Then select the BootExecute Tab.

2. The following may help you determine the "cause" of a chkdsk:

A chkdsk that is run because the dirty bit was found set will say:

"One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue."

A chkdsk that is requested by the user (chkdsk /f command) will say:

"A disk check has been scheduled."

3. Finally, If you want to change to the countdown value the appears
before a chkdsk begins, type:

chkntfs /T:n [where n is the number of seconds you want]

You might find the following articles helpful. They say they are for
older systems but these programs haven't changed that much.

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

http://support.microsoft.com/kb/160963/EN-US
--
Jim

I'll believe a corporation is just like a person when the State of Texas executes one.