Windows 10, running Cryptomator 1.58 exe 174 (new release)
I can’t say if this behavior is new with this version.
I have a Cryptomator volume which is unlocked automatically when my system starts. This has been working flawlessly for months.
Suddenly, it seems the mount fails at startup. Cryptomator says the vault is unlocked, but there is no drive mapping. Reveal drives fails, as does any other access to drive (D:, my mount point).
Event logs show a dokany mount followed shortly after by an unmount. Cryptomator logs seem to indicate a mount timeout. See logs at bottom of this post.
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. As far as I know the mount failure only happens during system restart.
Perhaps the dokany mount is just taking a bit too long? If so is there a way to increase the timeout? Any other suggestions?
Thanks.
Logs
15:23:42.512 [main] INFO org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Windows 10 10.0 (amd64)
15:23:54.087 [JavaFX Application Thread] INFO o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
15:23:54.120 [JavaFX Application Thread] INFO org.cryptomator.jni.FunctionsLoader - loaded WinFunctions.dll
15:23:55.768 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany version: 140
15:23:55.768 [App Background Thread 003] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
15:24:03.780 [App Background Thread 003] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
15:24:03.781 [App Background Thread 003] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of 'Cryptomator' succeeded.
15:25:34.926 [JavaFX Application Thread] WARN o.c.keychain.KeychainManager - LOAD
15:25:36.810 [App Background Thread 006] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: D:\
15:25:38.440 [JavaFX Application Thread] INFO o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
15:25:41.811 [App Background Thread 006] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver will be canceled now...
15:25:41.811 [App Background Thread 006] WARN o.cryptomator.frontend.dokany.Mount - Dokany driver for drive D:\: canceled.
15:25:41.814 [JavaFX Application Thread] INFO o.cryptomator.ui.common.VaultService - Locked Cryptomator
15:25:44.585 [App Scheduled Executor 01] INFO o.c.common.settings.SettingsProvider - Settings saved to C:\Users\LARRY\AppData\Roaming\Cryptomator\settings.json
15:25:46.415 [App Scheduled Executor 02] INFO o.c.common.settings.SettingsProvider - Settings saved to C:\Users\LARRY\AppData\Roaming\Cryptomator\settings.json
15:26:12.366 [App Background Thread 006] INFO com.dokany.java.DokanyDriver - Dokany version: 140
15:26:12.366 [App Background Thread 006] INFO com.dokany.java.DokanyDriver - Dokany driver version: 400
15:26:20.368 [App Background Thread 006] WARN o.c.frontend.dokany.MountFactory - Mounting timed out.
15:26:20.368 [App Background Thread 006] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of 'Cryptomator' succeeded.
15:26:22.621 [App Background Thread 006] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: D:\
15:27:00.062 [JavaFX Application Thread] INFO o.cryptomator.ui.quit.QuitController - Locked
15:27:00.081 [main] INFO org.cryptomator.launcher.Cryptomator - UI shut down
15:27:00.089 [Thread-174] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: D:\
15:27:00.090 [Thread-8] INFO com.dokany.java.DokanyDriver - Unmount and shutdown: D:\