After you schedule chkdsk and reboot, if you get one of these messages:
Cannot lock volume for direct access
or
Cannot open volume for direct access
<quote>
This problem occurs because the Chkdsk.exe utility or the Autochk.exe
utility could not lock the partition. This problem can occur if another
utility or service, such as a virus checker program or a disk monitoring
program, locks the partition before you try to run the Chkdsk.exe utility or
the Autochk.exe utility.
<quote>
There are several things that can cause the problem.
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/SUPPOR...6e22005026f1/52d79c84c363973488256ea600542b5a
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.
[[Ok BitDefender live support told me yesterday that they are working on it
and sending people analyse tools but she didn't send me one.....]]
from...
(e-mail address removed) 21 May 2006
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.
-----
Roxio Drive Letter Access can also cause the problem.
<quote>
Resolution (if anyone cares)
I removed the Sonic 'DLA' (drive letter access) CD burning software, (a
whole bunch of drivers loaded from \system32\dla\*.sys) which I actually
no longer needed, and disabled the (dubiously misnamed!, and hidden)
'networkX' device (ckldrv.sys loader, part of the Cryptkey software
protection, aka PC destruction, package) and now, suddenly, disk
checking works right. I am not about to put them back to see which one
was the culprit.
<quote>
from...
GSV Three Minds in a Can
It's Roxio Drive Letter Access now.
http://www.roxio.com/enu/products/dla/overview.html
--------
You can also try this.
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
[[Message 1
Cannot lock volume for direct access
Message 2
Cannot open volume for direct access ]]
You receive an error message when you run the Autochk.exe utility on a
partition after you restart the computer or when you schedule the Chkdsk.exe
utility to run on a partition on a Windows 2000-based computer or a Windows
NT-based computer
http://support.microsoft.com/kb/160654
This can sometimes work.
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
