Yes, I did get it to work. Here is what I did:
Upgraded to 1.7.3
Used Volume Type WinFsp
Used default mount flags
At this point, when I unlock my vault I have drive letters assigned to each of my vaults
When I am using windows on a day-to-day basis I just navigate inside my drive letters to find the files that I am looking for. However, for Syncback, I needed to use the UNC that windows shows. For example: \cryptomator-vault\job_data
@scadav5 Thanks so much for the time you put into your reply. The detail is much appreciated.
The good news is that what you’ve written has confirmed I followed instructions correctly. The bad news is that something is failing for me on step 6. When I try to use the UNC path, I’m prompted for a username and password and nothing I’ve tried has worked. I’ll have to dig into that step a little more I guess…
@infeo Thanks for the heads up about what’s coming.
What I’ve found with WinFSP Local is that I can get the mapping to a folder to be visible via Syncback Pro (i.e. I can see the folder listing when setting up the profile), but when I actually go to start the synchronization, Syncback Pro reports “Attempting to prepare…” and then eventual reports “The drive :\ does not exist!”
I can see the mapped folder from Explorer. I was able to copy a file as well.
BTW … this is why I started this thread in the first place. I’m not a very strong IT guy, I just played around with configurations to get it to work. I don’t really understand the difference between WinFSP vs WinFSP (Local Drive). In layman terms, I’d love to understand what the “Local Drive” part means.