CHKDSK fails

[Guest]

One night I tried to Defrag my computer, an error message poped up saying a
CHKDSK was schedueled to run and could not Defrag. So I restart my computer
and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[neil]

Boot from the XP CD and enter the recovery console, then run chkdsk at the
command prompt. What happens this time.??

You can also use a chkntfs at the command prompt in windows to turn off the
"dirty" check if you want to.

"Displays or modifies the checking of disk at boot time.

CHKNTFS volume [...]
CHKNTFS /D
CHKNTFS /T[:time]
CHKNTFS /X volume [...]
CHKNTFS /C volume [...]

volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
/D Restores the machine to the default behavior; all drives
are
checked at boot time and chkdsk is run on those that are
dirty.
/T:time Changes the AUTOCHK initiation countdown time to the
specified amount of time in seconds. If time is not
specified, displays the current setting.
/X Excludes a drive from the default boot-time check.
Excluded
drives are not accumulated between command invocations.
/C Schedules a drive to be checked at boot time; chkdsk will
run
if the drive is dirty.

If no switches are specified, CHKNTFS will display if the specified drive is
dirty or scheduled to be checked on next reboot."

Neil

 

[Wesley Vogel]

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

 

[Guest]

Thank you for the reply. Yes I had recently installed Spyware Doctor, and had
no idea this program would do that. I deleted the [ ikhlayer.sys ] file and
now everything works perfectly. Thank you very much!

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up saying
a CHKDSK was schedueled to run and could not Defrag. So I restart my
computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Wesley Vogel]

Keep having fun. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thank you for the reply. Yes I had recently installed Spyware Doctor, and
had no idea this program would do that. I deleted the [ ikhlayer.sys ]
file and now everything works perfectly. Thank you very much!

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up
saying a CHKDSK was schedueled to run and could not Defrag. So I
restart my computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Guest]

Thanks Wesley Vogel, Spyware Doctor was the problem. I did exactly as you
directed, rebooted and chkdsk ran. Thanks mate from Sydney OZ.
--
Money is POWER!
Knowledge is a fringe benefit.

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up saying
a CHKDSK was schedueled to run and could not Defrag. So I restart my
computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Wesley Vogel]

Glad to hear it. Keep having fun.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks Wesley Vogel, Spyware Doctor was the problem. I did exactly as you
directed, rebooted and chkdsk ran. Thanks mate from Sydney OZ.
--
Money is POWER!
Knowledge is a fringe benefit.

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up
saying a CHKDSK was schedueled to run and could not Defrag. So I
restart my computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Mike Gasson]

Glad to hear it. Keep having fun.

I've also discovered that Bit Defender Internet Security 9 does the same
thing. They tell me it is a known fault and they are working on it.
Have you come across a fix?

 

[Wesley Vogel]

That sounds like Plan 9 from Outer Space to me. ;-)

Thanks for the tip, Mike, I'll add it to my list.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log displayed
regarding chkdsk. What indication is there that the action was actually
carried out?

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up saying
a CHKDSK was schedueled to run and could not Defrag. So I restart my
computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Wesley Vogel]

Look in the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log displayed
regarding chkdsk. What indication is there that the action was actually
carried out?

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up
saying a CHKDSK was schedueled to run and could not Defrag. So I
restart my computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Guest]

Thanks for the reply.
Naturally your answer provoked more questions.
I looked at the log, and found one from several weeks ago, which showed
there were no bad sectors. However, I have tried to run chkdsk since that
time (at the behest of Symantec Support), and found no log for that attempt.
Is there some reason that it would not run?
Second, I did find an event of type 1001 Winlogon at a later date which
would correspond to the second attempt, but it was tagged as an error with
the following description : Fault Bucket 271613656. Does that shine any
light on my case?

Thanks.

Look in the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log displayed
regarding chkdsk. What indication is there that the action was actually
carried out?

 

[Wesley Vogel]

It means that you probably got an Event ID: 1001 Event Source: Application
Error

Explanation
A fault bucket identification number is a number assigned by the system to
identify specific types of errors. This number is used by Microsoft to
identify a particular program error when you send an error report.

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

Tip from:
Doug Knox

Or you can use:

CHKDSK C: /X > C:\CHKDISKLOG.TXT

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for the reply.
Naturally your answer provoked more questions.
I looked at the log, and found one from several weeks ago, which showed
there were no bad sectors. However, I have tried to run chkdsk since that
time (at the behest of Symantec Support), and found no log for that
attempt. Is there some reason that it would not run?
Second, I did find an event of type 1001 Winlogon at a later date which
would correspond to the second attempt, but it was tagged as an error with
the following description : Fault Bucket 271613656. Does that shine any
light on my case?

Thanks.

Look in the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled
it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked. The
Winlogon service then moves the contents of each Bootex.log file to the
Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log displayed
regarding chkdsk. What indication is there that the action was actually
carried out?

 

[Guest]

Hi!

Thank you very much Wes for your advice.

It was Spyware Doctor/ikhlayer.sys causing me the problem, autochk chkdsk
not proceeded at boot-up. I didn't even have the Spyware Doctor active, so,
I just simply deleted the ikhlayer.sys file from Win\Sys32\Drivers and
everything began to work normally.


Best regards,

Pete V.

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

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) 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

In

One night I tried to Defrag my computer, an error message poped up saying
a CHKDSK was schedueled to run and could not Defrag. So I restart my
computer and this happens when it tried to run CHKDSK:

Cannot open volume for direct access.
The type of the file system is NTFS.
Windows has finished checking the disk.

I have done everything I possibly could to fix this. Checked if drive is
dirty (it is).
Went to CMD: CHKDSK C: /f /r (same error message as above)
Even tried to repair Windows with my Windows XP SP2 disc.
Can some one please help me? I do not know what else to do.

 

[Guest]

Wes,

I attempted to run chkdsk c: /f > chkdisklog.txt from the command prompt,
but after letting it go for a couple of hours, I suspected something was
wrong and terminated it. There is no file named chkdisklog.
Is it possible that it could take longer than a couple of hours to do this
op on a 155 gig drive? If so, how long would you recommend I let it work?
Can you think of anything else which would interfere with disk checking?

Thanks,

Bill

It means that you probably got an Event ID: 1001 Event Source: Application
Error

Explanation
A fault bucket identification number is a number assigned by the system to
identify specific types of errors. This number is used by Microsoft to
identify a particular program error when you send an error report.

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

Tip from:
Doug Knox

Or you can use:

CHKDSK C: /X > C:\CHKDISKLOG.TXT

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for the reply.
Naturally your answer provoked more questions.
I looked at the log, and found one from several weeks ago, which showed
there were no bad sectors. However, I have tried to run chkdsk since that
time (at the behest of Symantec Support), and found no log for that
attempt. Is there some reason that it would not run?
Second, I did find an event of type 1001 Winlogon at a later date which
would correspond to the second attempt, but it was tagged as an error with
the following description : Fault Bucket 271613656. Does that shine any
light on my case?

Thanks.

Look in the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled
it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked. The
Winlogon service then moves the contents of each Bootex.log file to the
Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Bill S <Bill (e-mail address removed)> hunted and pecked:
Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log displayed
regarding chkdsk. What indication is there that the action was actually
carried out?

 

[Wesley Vogel]

Bill,

I apologize.

CHKDSK C: /F > C:\CHKDISKLOG.TXT doesn't work quite right. It creates a
log right away...

C:\CHKDISKLOG.TXT

[[The type of the file system is NTFS.
Cannot lock current drive.

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) ]]

and then it just hangs.

Normally if you run CHKDSK C: /F from a command prompt, you get that
same message *in* the command prompt and you have to type Y to schedule it
for the next boot.

If chkdsk actually runs, you see something similar to this on a black
screen...

----------
CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...

Security descriptor verification completed.
----------

Here is the GUI way to run chkdsk (Error Checking).

1. In My Computer or Windows Explorer, right-click the drive you want to
check and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

* Automatically fix file system errors
* Scan for and attempt recovery of bad sectors

A message will popup.

[[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?]]

Click YES.

Then reboot.

You should then see the black screen with...

CHKDSK is verifying files (stage 1 of 3)...

wait for it to finish, it should take ~10 minutes.

Then it will boot into Windows.

If you get one of these messages, then there is a problem...

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Wes,

I attempted to run chkdsk c: /f > chkdisklog.txt from the command prompt,
but after letting it go for a couple of hours, I suspected something was
wrong and terminated it. There is no file named chkdisklog.
Is it possible that it could take longer than a couple of hours to do this
op on a 155 gig drive? If so, how long would you recommend I let it work?
Can you think of anything else which would interfere with disk checking?

Thanks,

Bill

It means that you probably got an Event ID: 1001 Event Source:
Application Error

Explanation
A fault bucket identification number is a number assigned by the system
to identify specific types of errors. This number is used by Microsoft to
identify a particular program error when you send an error report.

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

Tip from:
Doug Knox

Or you can use:

CHKDSK C: /X > C:\CHKDISKLOG.TXT

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thanks for the reply.
Naturally your answer provoked more questions.
I looked at the log, and found one from several weeks ago, which showed
there were no bad sectors. However, I have tried to run chkdsk since
that time (at the behest of Symantec Support), and found no log for that
attempt. Is there some reason that it would not run?
Second, I did find an event of type 1001 Winlogon at a later date which
would correspond to the second attempt, but it was tagged as an error
with the following description : Fault Bucket 271613656. Does that
shine any light on my case?

Thanks.

:

Look in the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID,
and volume name or serial number to help determine what volume Chkdsk
ran against. Also included is whether Chkdsk ran because a user
scheduled it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked.
The Winlogon service then moves the contents of each Bootex.log file
to the Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In Bill S <Bill (e-mail address removed)> hunted and pecked:
Forgive me for jumping in here.

I ran the chkdsk C: /x at the cmd prompt, and rebotted as advised.
The boot looked just like every other one, quick, and no log
displayed regarding chkdsk. What indication is there that the action
was actually carried out?

 

[Guest]

Bill,

I apologize.

CHKDSK C: /F > C:\CHKDISKLOG.TXT doesn't work quite right. It creates a
log right away...

C:\CHKDISKLOG.TXT

[[The type of the file system is NTFS.
Cannot lock current drive.

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) ]]

and then it just hangs.

Normally if you run CHKDSK C: /F from a command prompt, you get that
same message *in* the command prompt and you have to type Y to schedule it
for the next boot.

If chkdsk actually runs, you see something similar to this on a black
screen...

----------
CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...

Security descriptor verification completed.
----------

Here is the GUI way to run chkdsk (Error Checking).

1. In My Computer or Windows Explorer, right-click the drive you want to
check and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

* Automatically fix file system errors
* Scan for and attempt recovery of bad sectors

A message will popup.

[[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?]]

Click YES.

Then reboot.

You should then see the black screen with...

CHKDSK is verifying files (stage 1 of 3)...

wait for it to finish, it should take ~10 minutes.

Then it will boot into Windows.

If you get one of these messages, then there is a problem...

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

 

[Guest]

Wes,

Well, chkdsk is apparently not running on this computer. I dusted off my
laptop and ran it, and it did exactly as you indicated it should in your
previous post. The question now is, "why ain't that sucker running?". I see
that others in this thread have had trouble with other software interfering.
If that is the case, must I stop other programs from starting up on reboot?
What about running chkdsk in safemode?

Bill

 

[Wesley Vogel]

Good idea, Bill. It's worth a shot.

Schedule chkdsk and reboot in Safe Mode.

The way to do that in this instance is to use the msconfig method.

Start | Run | Type: msconfig | Click OK |
BOOT.INI tab | Under Boot Options select: /SAFEBOOT

The /SAFEBOOT switch causes Windows to start in Safe Mode.

After making those boot.ini changes using msconfig, you need to click Apply
and Close.

Then click on: Restart.

See if chkdsk runs correctly.

Then before you shutdown or reboot again, open msconfig...

UNSelect: /SAFEBOOT under the boot.ini tab | Click Apply |
Under the General tab Select: Normal Startup - load all device drivers and
services | Click Apply and Close

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Wes,

Well, chkdsk is apparently not running on this computer. I dusted off my
laptop and ran it, and it did exactly as you indicated it should in your
previous post. The question now is, "why ain't that sucker running?". I
see that others in this thread have had trouble with other software
interfering. If that is the case, must I stop other programs from
starting up on reboot? What about running chkdsk in safemode?

Bill

Bill,

I apologize.

CHKDSK C: /F > C:\CHKDISKLOG.TXT doesn't work quite right. It
creates a log right away...

C:\CHKDISKLOG.TXT

[[The type of the file system is NTFS.
Cannot lock current drive.

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) ]]

and then it just hangs.

Normally if you run CHKDSK C: /F from a command prompt, you get that
same message *in* the command prompt and you have to type Y to schedule
it for the next boot.

If chkdsk actually runs, you see something similar to this on a black
screen...

----------
CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Index verification completed.

CHKDSK is verifying security descriptors (stage 3 of 3)...

Security descriptor verification completed.
----------

Here is the GUI way to run chkdsk (Error Checking).

1. In My Computer or Windows Explorer, right-click the drive you want to
check and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

* Automatically fix file system errors
* Scan for and attempt recovery of bad sectors

A message will popup.

[[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?]]

Click YES.

Then reboot.

You should then see the black screen with...

CHKDSK is verifying files (stage 1 of 3)...

wait for it to finish, it should take ~10 minutes.

Then it will boot into Windows.

If you get one of these messages, then there is a problem...

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

 

[Guest]

Well, that worked.
What do you suppose is the reason for this?

Thanks

Bill