Ok. I’m not sure what I did wrong, but I now have already moved everything out of Boxcryptor to Cryptomator. Is it possible to simply move the vault to a directory instead of a drive letter? If so, how?
Yes this is possible. You can change the way how your virtual filesystem is integrated any time.
To do it:
Go to app settings and make sure that you have selected “FUSE” (red frames)
open your vault settings (vault must be locked), and change the mount point to your folder where you want to have the unencrypted files to be shown. This folder must exist and has to be empty. (yellow frames)
More Info see documentation: Setup — Cryptomator 1.6.0 documentation
Please note that the android app work different than the desktop app.
You do not mount the vault, the vault is accessed via the android app. No integration in document provider on android so far, but its on the roadmap.
in settings, under Virtual Drive, Automatic is the default and selected, the other options are: WinFsp, WinFsp (Local Drive), WebDAV (Windows Explorer), and WebDAV (HTTP Address)
To pull back a bit this is what I am trying to do 1) I only want to encrypt the files from my computer that are synced with Dropbox. I run a program (SecondCopy) daily to move the files (unencrypted files on my desktop) that have changed to the “Virtual Folder” for encryption and synchronization via Dropbox. Essentially a daily backup to Dropbox with encrypted data. I just need to be able to refer to the virtual drive via a Drive Letter (in boxcrypter it was the X: drive) so I can tell SecondCopy where to place the changed data.
From all my research this seems do-able in cryptomator. I would think there are a number of people looking for this same solution. If there is a handy set of instructions / setting for this, I would assume several of us coming from boxcrypter could use it. I am trying to accomplish this without having to become an expert on cryptomator.
Let me know if my plan is reasonable.
I got this to work!
I decided to use brute force and was able to get SecondCopy to recognize the cryptomater virtual drive (d:). As I started playing with it, everything was off a level within the first structures. I simply went in and added a folder above my main folder call something like “Cryptomater File Level Holder” and it all works fine. The extra level does not bother me. I tested large amounts of data in complex files structures - No Issues! Thanks for your patience and I hope this might help others!