Nixx
asked on
Cannot Open Volume For Direct Access in Sched CHKDSK
Since I can't chkdsk while windows is running, it automatically schedules the chkdsk to be ran when the computer is restarted. Then the chkdsk screen pops up when i reboot and says "cannot open volume for direct access" and says "chkdsk complete" or something like that. I read somewhere that either cypkey or some sort of third party device is running while the computer is booting, therefore not enabling the chkdsk to run. I also checked microsoft's webpage and they had a fix to the problem, but only for windows NT. then i found some mention on the internet about "RC2" that fixed this error, but it said it was only released to a limited list of beta testers. Is there anyway I can get past this error and get chkdsk to run?
thanks.
thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am not the original poster, but I have the same inssue... for some reason I cannot get into SafeMode ... it just sits there. However, I can boot into complete XP Pro and use the machine as if nothing is wrong. yet ...
---------- as sent to a Forum ------
I asked WinXP to run a chkdsk with fix and it told me it would have to be next boot and now everytime it boots it runs chkdsk and reports:
Checking file system
The type of file systems is NTFS
Cannot open volume for direct access
Windows has finished checking the disk
…..
If I open a 'cmd' box and run chkdsk with no switches it states there are errors.
Things I have tried are:
msconfig - selective startup
disabled all services except Microsoft services
disabled all startup entries
then reboot as the machine should be booting Windows alone (which on completion is proven to be the case)
Conclusion: No application has control of C: despite chkdsk thinking this is the case!!
Partition Magic 8.0 - check for errors on C: after booting with rescue disks
it found no errors
Conclusion: booting an application that understands NTFS from floppy should 'free' C: - not sure how good the PM error check is
The install is a fresh install of WinXP, Office2K and it does have Norton Internet Security 2004. When I ran the Windowsupdate after installing the drivers, etc I did see MS KB836972 (the fix worked), so right now I do not feel too good about the correctness of the install. However, it boots, behaves itself but there is an error (according to chkdsk (no switches)) on the C: that seems incurable.
Looking at MS KB highlights KB823439 which does not hold out much hope … as it was posted in August 2003.
So, how do I stop chkdsk from running everytime I boot and how do I get to be able to actually run a chkdsk /f on my C: … my present feeling is that I should run format c: and start again, but I cannot be sure I will not end up back when I am now, seeing that it’s a fresh install and I am not sure what I could do different during the install to get to the right place. This is not my first every WinXP install, the others have been fine ..
---------- as sent to a Forum ------
I asked WinXP to run a chkdsk with fix and it told me it would have to be next boot and now everytime it boots it runs chkdsk and reports:
Checking file system
The type of file systems is NTFS
Cannot open volume for direct access
Windows has finished checking the disk
…..
If I open a 'cmd' box and run chkdsk with no switches it states there are errors.
Things I have tried are:
msconfig - selective startup
disabled all services except Microsoft services
disabled all startup entries
then reboot as the machine should be booting Windows alone (which on completion is proven to be the case)
Conclusion: No application has control of C: despite chkdsk thinking this is the case!!
Partition Magic 8.0 - check for errors on C: after booting with rescue disks
it found no errors
Conclusion: booting an application that understands NTFS from floppy should 'free' C: - not sure how good the PM error check is
The install is a fresh install of WinXP, Office2K and it does have Norton Internet Security 2004. When I ran the Windowsupdate after installing the drivers, etc I did see MS KB836972 (the fix worked), so right now I do not feel too good about the correctness of the install. However, it boots, behaves itself but there is an error (according to chkdsk (no switches)) on the C: that seems incurable.
Looking at MS KB highlights KB823439 which does not hold out much hope … as it was posted in August 2003.
So, how do I stop chkdsk from running everytime I boot and how do I get to be able to actually run a chkdsk /f on my C: … my present feeling is that I should run format c: and start again, but I cannot be sure I will not end up back when I am now, seeing that it’s a fresh install and I am not sure what I could do different during the install to get to the right place. This is not my first every WinXP install, the others have been fine ..
I'm getting this issue in 2003 Server. I looks like this issue, along with others started to happen when the disk got full corrupting certain files.
What other solution could there be so that I can get the chkdsk running at boot time???
What other solution could there be so that I can get the chkdsk running at boot time???
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.