Hard Disk Error Checking Utility

[Guest]

When I ran the Windows XP SP2 Hard Disk Error Checking Utility with the
"Automatically fix file system errors" box checked, I get an error message
that reads as follows:

"Checking Disk Local Disk (C"

"The disk check could not be performed because the disk check utility needs
exclusive access to some Windows files on the disk. These files can be
accessed only by restarting Windows. Do you want to schedule this disk check
to occur the next time you restart the computer?"

When I rebooted and ran the utility again with nothing else running I got
the same error message. Then I used the Windows MSCONFIG utility and
disabled ALL startup programs. I then ran the utility and I got the same
error message.

When I ran the Windows XP SP2 Hard Disk Error Checking Utility with
"Automatically fix file system errors" box unchecked, the utility reported no
problems.

What is going on here? Any suggestions?

 

[Woody]

Run utility again and answer yes to the question "Do you want to schedule
this disk check to occur the next time you restart the computer?". Reboot;
the utility should run before loading windows.

Woody

to occur the next time you restart the computer

 

[Lanwench [MVP - Exchange]]

When I ran the Windows XP SP2 Hard Disk Error Checking Utility with
the "Automatically fix file system errors" box checked, I get an
error message that reads as follows:

"Checking Disk Local Disk (C"

"The disk check could not be performed because the disk check utility
needs exclusive access to some Windows files on the disk. These
files can be accessed only by restarting Windows. Do you want to
schedule this disk check to occur the next time you restart the
computer?"

When I rebooted and ran the utility again with nothing else running I
got the same error message. Then I used the Windows MSCONFIG utility
and disabled ALL startup programs. I then ran the utility and I got
the same error message.

When I ran the Windows XP SP2 Hard Disk Error Checking Utility with
"Automatically fix file system errors" box unchecked, the utility
reported no problems.

What is going on here? Any suggestions?

This is normal when you're running chkdsk on your system volume. You have to
say "yes" when prompted to let it run on next startup, then restart the
computer.

 

[Guest]

This is normal when you're running chkdsk on your system volume. You have to
say "yes" when prompted to let it run on next startup, then restart the
computer.

Mr. Lanwench,

I tried your suggestion and CHKDSK now does run upon booting. Thank you
very much.

Several comments though.

1. After CHKDSK runs a report is generated on the screen. However, the
report disappears from the screen very quickly and I am unable to read all of
it. So I don't know if there are problems or not. (Some flakey things are
happening which caused me to want run this disk diagnostic utility in the
first place.) Would the report stick around longer if there were a problem?
May I conclude then that there are no problems?

2. I have Norton Disk Doctor (a part of Norton SystemWorks 2005). I've run
it with the "Fix errors" checkbox unchecked. In the report that is
generated, in the section labeled "Indexes Status", it says "Corrective
actions indicated below were not written to disk" because the "Fix errors"
checkbox was not checked. Then it goes on to list numerous entries of the
sort "Deleting index entry XXXX (where this character string varies) in index
$130 of file 47005." I then checked the "Fix errors" checkbox, which also
seems to force the running of the CHKDSK utility. My comment #1 above
applies in this situation as well. When I later run Norton Disk Doctor it
then still reports errors of the sort mentioned above, i.e., "Deleting index
entry XXXX (where this character string varies) in index $130 of file YYYY
(where this may vary)"

Any further comments, please?

Thank you.

Kal B

 

[Guest]

Woody,

I tried your suggestion and CHKDSK now does run upon booting. Thank you
very much.

Several comments though.

1. After CHKDSK runs a report is generated on the screen. However, the
report disappears from the screen very quickly and I am unable to read all of
it. So I don't know if there are problems or not. (Some flakey things are
happening which caused me to want run this disk diagnostic utility in the
first place.) Would the report stick around longer if there were a problem?
May I conclude then that there are no problems?

2. I have Norton Disk Doctor (a part of Norton SystemWorks 2005). I've run
it with the "Fix errors" checkbox unchecked. In the report that is
generated, in the section labeled "Indexes Status", it says "Corrective
actions indicated below were not written to disk" because the "Fix errors"
checkbox was not checked. Then it goes on to list numerous entries of the
sort "Deleting index entry XXXX (where this character string varies) in index
$130 of file 47005." I then checked the "Fix errors" checkbox, which also
seems to force the running of the CHKDSK utility. My comment #1 above
applies in this situation as well. When I later run Norton Disk Doctor it
then still reports errors of the sort mentioned above, i.e., "Deleting index
entry XXXX (where this character string varies) in index $130 of file YYYY
(where this may vary)"

Any further comments, please?

Thank you.

Kal B

 

[Lanwench [MVP - Exchange]]

Mr. Lanwench,

Ms. Lanwench, please

I tried your suggestion and CHKDSK now does run upon booting. Thank
you very much.

No prob.

Several comments though.

1. After CHKDSK runs a report is generated on the screen. However,
the report disappears from the screen very quickly and I am unable to
read all of it. So I don't know if there are problems or not. (Some
flakey things are happening which caused me to want run this disk
diagnostic utility in the first place.) Would the report stick
around longer if there were a problem? May I conclude then that there
are no problems?

Check your system event logs....

2. I have Norton Disk Doctor (a part of Norton SystemWorks 2005).
I've run it with the "Fix errors" checkbox unchecked. In the report
that is generated, in the section labeled "Indexes Status", it says
"Corrective actions indicated below were not written to disk" because
the "Fix errors" checkbox was not checked. Then it goes on to list
numerous entries of the sort "Deleting index entry XXXX (where this
character string varies) in index $130 of file 47005." I then
checked the "Fix errors" checkbox, which also seems to force the
running of the CHKDSK utility. My comment #1 above applies in this
situation as well. When I later run Norton Disk Doctor it then still
reports errors of the sort mentioned above, i.e., "Deleting index
entry XXXX (where this character string varies) in index $130 of file
YYYY (where this may vary)"

I haven't used Norton Disk Doctor - can't say. Have you checked in help?

 

[Quaoar]

Woody,

I tried your suggestion and CHKDSK now does run upon booting. Thank
you very much.

Several comments though.

1. After CHKDSK runs a report is generated on the screen. However,
the report disappears from the screen very quickly and I am unable to
read all of it. So I don't know if there are problems or not. (Some
flakey things are happening which caused me to want run this disk
diagnostic utility in the first place.) Would the report stick
around longer if there were a problem? May I conclude then that there
are no problems?

2. I have Norton Disk Doctor (a part of Norton SystemWorks 2005).
I've run it with the "Fix errors" checkbox unchecked. In the report
that is generated, in the section labeled "Indexes Status", it says
"Corrective actions indicated below were not written to disk" because
the "Fix errors" checkbox was not checked. Then it goes on to list
numerous entries of the sort "Deleting index entry XXXX (where this
character string varies) in index $130 of file 47005." I then
checked the "Fix errors" checkbox, which also seems to force the
running of the CHKDSK utility. My comment #1 above applies in this
situation as well. When I later run Norton Disk Doctor it then still
reports errors of the sort mentioned above, i.e., "Deleting index
entry XXXX (where this character string varies) in index $130 of file
YYYY (where this may vary)"

Any further comments, please?

Thank you.

Kal B

Event Viewer will show logged information about the chkdsk operation.
In the applications section, look at the winlogon items.

Q

 

[Guest]

Very useful information. Thank you.

Kal B

Event Viewer will show logged information about the chkdsk operation.
In the applications section, look at the winlogon items.

Q

 

[Guest]

I have the same problem and I tried that and the utility never comes up It
just reboots back into Windows. Any other suggestions

Debbie

 

[Guest]

When I reboot chkdsk doesn't come up so I can't even use Defrag either
because it says that chkdsk is suppose to run during reboot

Debbie

 

[Loren Pechtel]

I have the same problem and I tried that and the utility never comes up It
just reboots back into Windows. Any other suggestions

Malware, perhaps?

 

[Guest]

When I run chkdsk /f/r it comes up during reboot but it says chkdsk cannot
open volumne for direct access. Windows has finished checking disk. Does
anyone have a helpful hint on this one.

Debbie

 

[Bob I]

Some software will cause this problem.

The following is a quote from a posting by Wesley Vogel


If you are getting one of these messages:

Cannot lock volume for direct access
or
Cannot open volume for direct access


Symantec AntiVirus Corporate Edition 9.0 can cause the problem.


Chkdsk.exe or ScanDisk fails to run on Windows XP or Windows 2003 after
installing Symantec AntiVirus Corporate Edition 9.0
http://service1.symantec.com/SUPPORT/ent-security.nsf/529c2f9adcf33a1...


A program called Hitman Pro can cause the problem.


A really old version of ZoneAlarm (a version from 2004) can cause the
problem.


BitDefender Internet Security 9 can cause the problem.


Spyware Doctor can also cause the problem.


The /x switch doesn't work if Spyware Doctor is installed. Spyware Doctor
needs to be uninstalled or you can do this...


Quoted from *PCTools*, *Spyware* *Doctor*...
1. Exit from Spyware Doctor (to exit from Spyware
Doctor please right click on the Spyware Doctor icon in
the notification area (next to the clock on the Windows
taskbar) and select Exit from the menu that appears)


2. Delete the file
ikhlayer.sys from %windir%\system32\drivers\
or
from c:\windows\system32\drivers\


3. Restart Spyware Doctor


Chkdsk, defrag and error-checking should now work.
-----


[[There is currently no fix for this problem.]]
[[NOTE: You may have success if you schedule Chkdsk to run at startup and
use the /X switch, which will force a dismount. ]]
from...
JSI Tip 7079. You receive 'Cannot open volume for direct access' when
Chkdsk
runs during Windows XP startup
http://www.jsifaq.com/subO/tip7000/rh7079.htm


To run chkdsk from a command prompt.


Start | Run | Type: cmd | Click OK |
In the command prompt, type:


chkdsk C: /x


Hit your Enter key.


The following error message appears:
Chkdsk cannot run because the volume is in use by another process. Would
you
like to schedule this volume to be checked the next time the system
restarts? (Y/N)


Type Y, hit Enter and close the command prompt.


Reboot.


The /x switch: Use with NTFS only. Forces the volume to dismount first, if
necessary. All open handles to the drive are invalidated. /x also includes
the functionality of /f. The /F switch fixes errors on the disk.


Unable to run CHKDSK
http://support.microsoft.com/kb/555484


--
Hope this helps. Let us know.


Wes
MS-MVP Windows Shell/User

 

[frodo]

boot into the Recovery Console and run chkdsk /p from there.

to do this you'll need 1) RC already installed on your HD as a boot
option, or 2) a CD w/ the RC on it; if running SP2 you'll need an SP2 CD
(slipstreamed works); the SP1 version of RC will not run on a SP2 system.