I have used a batch command to mount a volume in Truecrypt and then Veracrypt for several years without any problem in the format:
"...veracrypt" /volume "C:\VCV\vcv07" /letter v /auto /password XXX /quit /silent
Recently the effect has been: Vercrypt sees the mounted volume as drive V (I have an image 01 but cannot see how to attach it), but Windows 10 sees it as drive H (image 02). My later Windows commands referencing V now do not work.
One of my other commands to mount a volume as drive S (run at the same time as this) has no such problems.
I do not know if it is relevant, but in the last year I have been plagued by the "two drive letters" issue and tried some of the suggestions in relevant threads, but mostly to no avail - but I can live with that.
I have tried using the drivecleanup utility, and doing a clean boot, as suggested in another thread, but the problem remains. I am using Veracrypt 1.22 64 bit and Windows 10. Any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can't explain why your command has worked successfully for years, but now fails in certain situations, but there is something odd about it, which it might be sensible to deal with, to see if that has a bearing on the case.
You do not need to specify '/auto', if you use '/v' and '/q' (it will be implicit). So, I suggest removing '/auto' from your command, in case its (in effect, duplicate) presence is complicatiing matters (bearing in mind that specifying '/auto' in the absence of '/l' mounts to the next available drive letter).
Also, have you tried using the command without '/s', to see what error messages, if any, appear?
Last edit: Adrian Kentleton 2018-06-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the replies. I will try these out. However my original problem has gone away.
To explain: I had to recover from a Windows update issue, which involved various rebootings. I also had a different problem with Veracrypt, in that I had (recently after an earlier windows update issue) reinstalled it as an admin user, so had to keep antering the admin password when I ran it as a norrmal user. I therefore uninstalled Veracrypt and reinstalled it as a non-admin user (having of course to give the admin password just once).
Now, after all these changes and for whatever reason, I find that my volume is installed as drive V as well as drive H, so I can now use my commands that refer drive V. Later I will try to get rid of the drive H issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have used a batch command to mount a volume in Truecrypt and then Veracrypt for several years without any problem in the format:
"...veracrypt" /volume "C:\VCV\vcv07" /letter v /auto /password XXX /quit /silent
Recently the effect has been: Vercrypt sees the mounted volume as drive V (I have an image 01 but cannot see how to attach it), but Windows 10 sees it as drive H (image 02). My later Windows commands referencing V now do not work.
One of my other commands to mount a volume as drive S (run at the same time as this) has no such problems.
I do not know if it is relevant, but in the last year I have been plagued by the "two drive letters" issue and tried some of the suggestions in relevant threads, but mostly to no avail - but I can live with that.
I have tried using the drivecleanup utility, and doing a clean boot, as suggested in another thread, but the problem remains. I am using Veracrypt 1.22 64 bit and Windows 10. Any suggestions?
I can see how to add the two attachments to this comment.
Are you running the drivecleanup utility by starting a command prompt as "Run as administrator"?
Your default directory when you first the command prompt as "Run as administrator" should be:
C:\WINDOWS\system32>Be sure that Fast Startup is disabled.
http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html
Reboot PC.
Then run the drive cleanup utility and reboot PC.
Last edit: Enigma2Illusion 2018-06-06
I can't explain why your command has worked successfully for years, but now fails in certain situations, but there is something odd about it, which it might be sensible to deal with, to see if that has a bearing on the case.
You do not need to specify '/auto', if you use '/v' and '/q' (it will be implicit). So, I suggest removing '/auto' from your command, in case its (in effect, duplicate) presence is complicatiing matters (bearing in mind that specifying '/auto' in the absence of '/l' mounts to the next available drive letter).
Also, have you tried using the command without '/s', to see what error messages, if any, appear?
Last edit: Adrian Kentleton 2018-06-06
Thanks for the replies. I will try these out. However my original problem has gone away.
To explain: I had to recover from a Windows update issue, which involved various rebootings. I also had a different problem with Veracrypt, in that I had (recently after an earlier windows update issue) reinstalled it as an admin user, so had to keep antering the admin password when I ran it as a norrmal user. I therefore uninstalled Veracrypt and reinstalled it as a non-admin user (having of course to give the admin password just once).
Now, after all these changes and for whatever reason, I find that my volume is installed as drive V as well as drive H, so I can now use my commands that refer drive V. Later I will try to get rid of the drive H issue.