As far as I know the mount failure only happens during system restart. If I lock/unlock the vault manually after this failure, the vault is successfully unlocked and mounted to drive (D:) is once again mounted and is accessible. Cryptomator logs seem to indicate a mount timeout. Reveal drives fails, as does any other access to drive (D:, my mount point).Įvent logs show a dokany mount followed shortly after by an unmount. Cryptomator says the vault is unlocked, but there is no drive mapping. Suddenly, it seems the mount fails at startup.
This has been working flawlessly for months. I have a Cryptomator volume which is unlocked automatically when my system starts. I can’t say if this behavior is new with this version.
#CRYPTOMATOR MOUNTING FAILED WINDOWS#
Windows 10, running Cryptomator 1.58 exe 174 (new release) I can access my data without any problems after manually locking/unlocking the vault. Manually locking and unlocking the vault helps every time. When I click reveal vault, I get an error message in Windows Explorer.
I get the windows saying “Unlocked XYZ successfully! Your fault is now accessible”. “Unlock vault when starting computer” is enabled.Ĭryptomator starts automatically but fails to mount the drives at least every second time. I use Cryptomator 1.5.6 (Dokany) on Windows 10, Version 1909.
0 kommentar(er)
