I recently upgraded from 1.2 to 18.104.22.168 and have run into a problem under which I receive the following error message in a balloon from the BoxCryptor system-tray icon:
The source directory does not exist anymore!
My usage model is, perhaps, non-standard, as I use the program to provide a Windows-friendly means of accessing several remotely hosted EncFS volumes. These can be large, >50GB at times, and while on a Windows platform, I've been using SMB/CIFS to access the shares. Obviously this is not the standard DropBox <2GB usage model, but earlier versions have worked OK.
The error generally occurs several minutes after launching the BoxCryptor program (in this case on a Win7-64 machine). After it occurs, I unmount the affected volume and check the underlying CIFS network share, which does indeed appear to be inaccessible from this client. This CIFS share remains accessible from other clients on the network, and other CIFS shares on the same remote machine remain accessible throughout from all clients. After some amount of time (say 30 minutes, perhaps less), the underlying affected CIFS network share becomes accessible again from the affected client. If multiple BoxCryptor volumes are mounted, only the first/top mounted volume appears to be affected.
Given the above behavior, it is unclear to me whether the issue resides in BoxCryptor itself or in how the program interacts with the OS and Windows networking. I will post a support ticket with a couple of BoxCryptor.log files shortly.