asked on

CHKDSK Scheduled

I have a 2003 server that wants to run CHKDSK upon boot. There was a HD issue which has been corrected (RAID5, replaced drive). No, when the server restarts it wants to run CHKDSK. Normally this is not an issue. But this server has an extremly large vomune and would take to long to run. Is there a way to kill the CHKDSK so it won't run at startup?

Thanks

ASKER CERTIFIED SOLUTION

sunray_2003

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sunray_2003

http://windows.about.com/library/tips/bltip018.htm

mchristo63

ASKER

The Key reads:

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

Data: autocheck autochk*

I check another 2003 server and it has the same parameters. So, what does is the value when CHKDSK is scheduled to execute at boot because I am assuming this currect key is not set to execute (I think that only because the other server has the same key).

Thanks

sunray_2003

mchristo63,

Have you tried to remove the text in bootexecute ie autocheck autochk* and checked what happens ?

Make sure to backup your registry before doing the changes

mchristo63

ASKER

Nevermind. I figured it out. I forced a server to run CHKDSK and had it schedule itself to run at boot. Here is what the key value looks like:

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

Thanks for your help.

sunray_2003

mchristo63,

Thanks for the pts.
So you wanted to schedule chkdsk at bootup or wanted to disable that

mchristo63

ASKER

I wanted to disable. The key data listed above was from a server that was scheduled to run at boot, but the server in question didn't have those keys. I ask this because last time I rebooted the server wanted to run CHKDSK, but I canceled the process. So, I assumed upon next boot the server was going to run it again. After looking at the key, maybe when I canceled the CHKDSK it removed the key data and set it to a default value. Anyway, in short, the key data didn't have chkdsk parameters so I am assuming it won't run on next boot.