"Access Denied Error" Source: volTransformThreadFunction:2757
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I am receiving this error message when I try to utilize Veracrypt to make a 64 GB encrypted USB key. Any insight would be greatly appreciated. I am using the portable version.
Last edit: m1dori 2020-04-22
You are not alone; I have the same issue. After years of problem-free use of Truecrypt (since 3.1) and Veracrypt, I am starting to find it impossible with my new PC to:
a. format file containers when creating them, and have to resort to a workaround whereby one doesn't set a file system on creation, but does so on first mount. (Other users are having this problem.)
b. encrypt an entire USB key.
I recently bought 4 SanDisk Ultra Flair 32GB USB 3.0 sticks. Can't encrypt them on my W10 Pro v1909 64-bit system (8GB RAM, Pentium 1.5GHz) running VC 1.24-Update6 64-bit, getting the same error message as you.
Fortunately, I can encrypt them on my old W7 Pro SP1 32-bit system (3GB RAM, Intel Core i3 2.53GHz) running VC 1.23 32-bit.
I'm experimenting with creating file containers using the old setup, more anon.
I suspect W10 personally, it's another classic MS omnishambles, but it's rather frustrating!
Curiouser and curiouser ...
I have three other W10 PCs:
a. one is identical to my main PC, except it's running v1809: encrypting USB key works fine!
b. one is W10 Home v1909, 64-bit, with VC 1.23 (x64): encrypting USB key works fine!
c. one is W10 Pro v1809, 32-bit, with VC 1.23 (x32): encrypting USB key works fine!
Will update VC on b. & c., and see what happens. More anon.
I appreciate your updates! I can confirm that VC 1.23 (x64) portable is working on my W10 Home v1909 64-bit PC. The problem only appeared with VC 1.24 (x64).
Thank you again for the reply!
Had time yesterday to update VC to 1.24-Update6 on c. above ie W10 Pro v1809 32-bit; was able to encrypt a USB key. Will have a go at b. today.
I've updated b. above ie W10 Home v1909 64-bit to VC 1.24-Update6 64-bit, and have been able to encrypt a USB key.
So, there appears to be some compatability issue between my W10 Pro v1909 64-bit PC, and VC 1.24 Update-6 64-bit. But not with my W10 Home v1909 64-bit PC running VC 1.24 Update-6 64-bit (which was the original poster's issue).
Can the developers please shed some possible light on this? What sort of issue does the error message in the original post point to?
I have 'reset' my errant W10 Pro v1909 64-bit main PC, and the problems I have been experiencing with VC (unable to encrypt USB drive, unable to format file container when creating it) have disappeared.
I reset my PC because I was starting to experiencing all sorts of bizarre and random issues, for which the most likely common factor was NTFS permissions issues (despite the fact that whenever security settings were investigated, all appeared in order).
So, some registry corruption, probably, but all attempts to diagnose the root cause drew a blank. Resetting appeared to be only option, a bit of a pain, but worth the effort; the other problems appear to have been resolved as well.
Disable "Controlled folder access" under "Ransomware protection" in Windows 10 and Veracrypt can again encrypt USB drives for me.
After too much research to reach such a basic piece of info I learned that in order to create NTFS volumes you need to run as administrator..But Veracrypt warns against that I might not be able to have write access after im done.. I am not sure what to do next, Ill just do it and hope for the best..
Last edit: hosa 2023-12-29