| "Eeyan" <
[email protected]>
| wrote in message | Hi, Anyone help? XP Pro. When booting up to perform a
| chkdsk it reports Cannot open volume for full access. It is a
| consistent problem. Any solutions?
If by writing "Cannot open volume for full access" you mean
"Cannot Open Volume for Direct Access", then:
Like the Microsoft Knowledge Base Article on the subject says:
"Microsoft is researching this problem and will post more
information in this article when the information becomes available."
For more information see the following Microsoft Knowledge Base
article:
KB823439 - "Cannot Open Volume for Direct Access" Error Message
When Chkdsk Runs at Startup
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;823439
And to quote Jerold Schulman - Windows: General MVP, from
his "JSI, INC_ - Tips & Tricks" web page on the subject:
"There is currently no fix for this problem. When a solution
becomes available, Microsoft will probably release a hotfix, or
provide a workaround. If a hotfix becomes available, Microsoft
will include the fix in a Windows XP service pack. NOTE: You may
have success if you schedule Chkdsk to run at startup and use the
/X switch, which will force a dismount."
For the entire article see the "JSI, INC_ - Tips & Tricks" web
page on the subject:
JSI Tip 7079_ You receive 'Cannot open volume for direct access'
when Chkdsk runs during Windows XP startup
http://www.jsiinc.com/SUBO/tip7000/rh7079.htm
And if forcing a dismount does not work you may want to try the
resolution given by the following Web Site:
Computer Technical Support Forums
All Forums | SOFTWARE SUPPORT | Operating Systems: Microsoft
MyTechSupport_ca - Cannot open volume for direct access
http://www.mytechsupport.ca/support/topic.asp?TOPIC_ID=3503
In my words:
Run msconfig. Select a Diagnostic Startup of Basic Devices and
Services Only. Use the method of your choice to schedule autochk
(the version of chkdsk that runs when you restart your computer).
And then reboot.
Note that the Computer Technical Support Forums Web Site implicates
3rd party kernel-mode drivers. Additionally, many on the Microsoft Public
Newsgroup Forums have implicated a Zone Alarm kernel-mode driver
as being the culprit. If that could be the cause you may want to do a
Google search such as the following one that uses relevant criteria, and
review those suggestions.
driver vsdatant chkdsk
http://www.google.com/search?&q=driver+vsdatant+OR+vsmon+chkdsk
For example, the above Google search leads to the following article that
you may be interested in.
Re Zone Alarm 5 upgrade stopping Win XP Check Disk
Windows and ZoneAlarm® Messages and Alerts
Zone Labs User Forum
http://forum.zonelabs.org/zonelabs/board/message?board.id=win_za_msgs&message.id=5933
Also see the following Microsoft Knowledge Base article on
the subject of deactivating kernel-mode drivers:
KB816071 - How to Temporarily Deactivate the
Kernel Mode Filter Driver
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;816071
For more information about the GUI error-checking tool search
Windows XP Professional Help and Support Center Full-text Search
Matches titled: "Detecting and repairing disk errors".
For more information about the command-prompt method "chkdsk"
(and the /x parameter) search the Windows XP Professional Help
and Support Center for the word in double-quotes and read the
Full-text Search by that title.
For more information about msconfig and the option: Diagnostic
Startup - load basic devices and services only, see the following
Microsoft Knowledge Base Article:
KB310560 - How to Troubleshoot By Using the Msconfig
Utility in Windows XP
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;310560
