Menu

TrueCrypt to VeraCrypt - Cannot open volume for direct access.

2017-08-07
2017-08-07
  • Jens Petersen

    Jens Petersen - 2017-08-07

    Have just converted 2 partitions from TC v7.1a to VC v1.21. Am on Win7x64 and everything seemed fine. However a bat file failed, saying it could not find the D drive. I then tried a Filecheck and got:
    Checking the file system on the VeraCrypt volume mounted as D:...
    Cannot open volume for direct access.
    Press any key to continue . . .

    Not sure what's going on, though needless to say there were no problems doing this in TrueCrypt.

     
  • Enigma2Illusion

    Enigma2Illusion - 2017-08-07

    VeraCrypt has stricter command line structure than TrueCrypt to prevent incorrect action taken since in TrueCrypt it was possible to combine certain command switches which resulted in different results than intended expected behavior.

    Review the documentation and adjust your command switches according to the VeraCrypt documentation.

    https://www.veracrypt.fr/en/Command%20Line%20Usage.html

     
  • Jens Petersen

    Jens Petersen - 2017-08-07

    Actually I tried the filecheck through the VeraCrypt GUI.
    As far as the bat file goes, I was trying to access a drive via the letter in Windows - not rocket science; and I fail to see why command switches would be needed for that.

     
  • Enigma2Illusion

    Enigma2Illusion - 2017-08-07

    What does the bat file perform?

    This could be a registry issue that happens to some users when they migrated existing TC to VC that has drive letter conflicts.

    Try unmounting all TC and VC volumes and run as administrator in command window:

    mountvol.exe /r

    Reboot PC.

     
  • Jens Petersen

    Jens Petersen - 2017-08-07

    I went to Edit the security permissions for the drive in question via Properties-Security-Edit, and could not - got an error message (attachment).

     
  • Jens Petersen

    Jens Petersen - 2017-08-07

    What does the bat file perform?

    This could be a registry issue that happens to some users when they migrated existing TC to VC that >has drive letter conflicts.

    Try unmounting all TC and VC volumes and run as administrator in command window:

    mountvol.exe /r

    Reboot PC.

    Thanks Enigma2Illusion - will try.

     

    Last edit: Jens Petersen 2017-08-07
  • Jens Petersen

    Jens Petersen - 2017-08-07

    Unfortunately the problem is still there.

     
  • Jens Petersen

    Jens Petersen - 2017-08-07

    Update - Well, the D drive with the original problem, still has it. But Windows has now 'mirrored' it, so it also appears as K. The K drive can be filechecked etc. So registry problems might still be the culprit I suppose. Don't like it - neither drive reports the correct size from the Computer explorer view, but does give the correct size in Disk-Properties.

     
  • Jens Petersen

    Jens Petersen - 2017-08-07

    Fixed by deleting the
    HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
    key. VeraCrypt seems to be working fine, the mount times are maybe 10s which is great - much more important anyway, is what happens once they are mounted. I really like the randomness status bar - better than the old TrueCrypt way of shaking the mouse around for some time, without any feedback:-)

     
  • Enigma2Illusion

    Enigma2Illusion - 2017-08-08

    For benefit of other users, you can perform the following using a modified version of Idrassi's instructions:

    With the all volumes dismounted, perform the following.

    Check the registry key "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices" using regedit. Scroll down and you'll find entries starting with "\DosDevices\" which indicate the drive letters that are taken by the system. Before mounting any volume, double click on each one and remove the ones contains the name "VeraCrypt" or "TrueCrypt".

    Also, there are other entries whose name start with "#{" and "\??\Volume{": double click on each one of them and remove the ones whose data value contains the name "VeraCrypt" or "TrueCrypt".

    Reboot PC.

    If the above does not resolve the issue. See below.


    If you are willing to use the DriveCleanup utility below to remove all currently non present USB Storage Devices, Disks, CDROMs, Floppies, Storage Volumes and WPD devices from the device tree. Furthermore it removes orphaned registry items related to these device types.

    I request you use version 0.9.0 since I have not tested 1.4.0 version that was recently released.

    Create a directory and unzip the software files into the directory.
    Start a command line prompt as Administrator.
    In the command window, change into the directory where you unzipped the files. If you are using 64-bit Windows OS, change into x64 subdirectory.
    Dismount all VeraCrypt/TrueCrypt volumes.

    Use the following command to view what the DriveCleanup utility will remove from the registry:

    drivecleanup -T

    To remove items the registry:

    drivecleanup

    Reboot PC after running utility.

    Any USB that was not currently connected to your PC will be install again by Windows and you may have to manually reassign the drive letters in Windows Disk Management if you had certain drive letters for an external hard drive or thumbdrives.

    http://www.uwe-sieber.de/drivetools_e.html

    http://www.uwe-sieber.de/files/drivecleanup090.zip

    I have performed this numerous times on my Win 7 Pro 64-bit Windows system to remove all registry entries including valid devices due to tests with file containers.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.